Theron Smith thinkstylestudio

Beast Mode

Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.

Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1

Installation Instructions

Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
Select "Create new custom chat mode file"

Troubleshooting Valet on Sierra

Common Problems

Problem: I just see "It works!"

Apache is running on port 80 and interfering with Valet.

Stop Apache: sudo /usr/sbin/apachectl stop
Restart Valet: valet restart

	<?php

	namespace App\Providers;

	use Illuminate\Database\Eloquent\Builder;
	use Illuminate\Support\Arr;
	use Illuminate\Support\ServiceProvider;

	class AppServiceProvider extends ServiceProvider
	{

	{
	"title": "Kinesis Freestyle2",
	"rules": [
	{
	"description": "Swap only for Windows",
	"manipulators": [
	{
	"conditions": [
	{
	"type": "device_if",

	# Change to the project directory
	cd $FORGE_SITE_PATH

	# Turn on maintenance mode
	php artisan down \|\| true

	# Pull the latest changes from the git repository
	# git reset --hard
	# git clean -df
	git pull origin $FORGE_SITE_BRANCH

	<?php

	namespace App\Traits;

	use DB;
	use Carbon\Carbon;

	trait MassInsertOrUpdate
	{
	protected $insert_or_update_chunk_size = 1000;

	** Apache
	- Edit public/.htaccess of laravel application with wordpress in subfolder
	<IfModule mod_rewrite.c>
	<IfModule mod_negotiation.c>
	Options -MultiViews
	</IfModule>

	RewriteEngine On

	# Redirect Trailing Slashes If Not A Folder...

	#!/usr/bin/env python

	import gitlab
	from jira import JIRA
	import urllib3

	## Disable urllib3 ssl checks warnings
	urllib3.disable_warnings( urllib3.exceptions.InsecureRequestWarning )

	## GitLab config

	If you’re anything like me who didn't want to pay for github before their new business strategy, then most likely you use BitBucket or hosted your own (come ‘on, it was free!). Problem with that is now your activities or contributions are fragmented between the different services. Now that I've chosen GitHub, I found myself migrating the git repos.

	Here is my copy and paste script I use for migration which also carries your history, which without it, defeats the purpose of it!


	$ cd ~/Sites/repo-directory
	$ git remote rename origin bitbucket
	$ git remote add origin [email protected]:JMichaelVelasquez-change-user/your-new-repo.git
	$ git push origin master

	<?php namespace App\Providers;

	use Elastica\Client;
	use Illuminate\Support\ServiceProvider;
	use Monolog\Formatter\LogstashFormatter;
	use Monolog\Handler\ElasticSearchHandler;

	class ElasticLoggingProvider extends ServiceProvider
	{