Shaun Santa Cruz shaunsantacruz

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"

description

tools

4.1 Beast Mode

changes

codebase

editFiles

extensions

fetch

findTestFiles

githubRepo

new

openSimpleBrowser

problems

readCellOutput

runCommands

runNotebooks

runTasks

runTests

search

searchResults

terminalLastCommand

terminalSelection

testFailure

updateUserPreferences

usages

vscodeAPI

Beast Mode v3 is out now: 👉 https://gist.github.com/burkeholland/88af0249c4b6aff3820bf37898c8bacf

You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.

Using an Access Token for the first time

Follow the instructions on Github to Create an Access Token in Github

Configure Git to use the osxkeychain

By default, git credentials are not cached so you need to tell Git if you want to avoid having to provide them each time Github requires you to authenticate. On Mac, Git comes with an “osxkeychain” mode, which caches credentials in the secure keychain that’s attached to your system account.

You can tell Git you want to store credentials in the osxkeychain by running the following:-

How to Change Open Files Limit on OS X and macOS

This text is the section about OS X Yosemite (which also works for macOS Sierra) from https://docs.basho.com/riak/kv/2.1.4/using/performance/open-files-limit/#mac-os-x

The last time i visited this link it was dead (403), so I cloned it here from the latest snapshot in Archive.org's Wayback Machine https://web.archive.org/web/20170523131633/https://docs.basho.com/riak/kv/2.1.4/using/performance/open-files-limit/

Mac OS X

To check the current limits on your Mac OS X system, run:

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

Include Weather Icons in your app: https://github.com/erikflowers/weather-icons
Include the below JSON in your application, for example purposes, lets assume it's a global named weatherIcons.
Make a request to OpenWeatherMap:

req = $.getJSON('http://api.openweathermap.org/data/2.5/weather?q=London,uk&callback=?');

	<!-- wp:paragraph {"align":"center","customTextColor":"#000000","backgroundColor":"very-light-gray","fontSize":"small"} -->
	<p style="color:#000000;text-align:center" class="has-background has-small-font-size has-very-light-gray-background-color">Gutenberg Sample Content.<br/>Put together with ❤️ by <a href="https://artisanthemes.io/">Artisan Themes</a>.</p>
	<!-- /wp:paragraph -->

	<!-- wp:heading {"level":1} -->
	<h1>This is a heading (H1)</h1>
	<!-- /wp:heading -->

	<!-- wp:heading -->
	<h2>This is a heading (H2)</h2>

	/*
	* This file contains JS modules for a React app using react-router and redux.
	* Each module should be in its own separate file, but for the purposes of
	* this gist, I've inlined them all.
	*/

	/* app/index.js */

	import React from 'react'
	import { Router, browserHistory } from 'react-router'

	<?php

	add_action('admin_init', function () {
	// Redirect any user trying to access comments page
	global $pagenow;

	if ($pagenow === 'edit-comments.php') {
	wp_redirect(admin_url());
	exit;
	}

	<?php

	/**
	* Duplicates a post & its meta and returns the new duplicated Post ID.
	*
	* @param int $post_id The Post ID you want to clone.
	* @return int The duplicated Post ID.
	*/
	function duplicate_post(int $post_id): int
	{