In this gist, you can find all the VS Code chat modes I am using in my projects for the Persona based approach technique I created.
You will find an article about on my dev.to blog (dev.to/kasuken)
In this gist, you can find all the VS Code chat modes I am using in my projects for the Persona based approach technique I created.
You will find an article about on my dev.to blog (dev.to/kasuken)
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
| FROM python:3.10.12-slim-buster as python-base | |
| # python | |
| ENV PYTHONUNBUFFERED=1 \ | |
| # prevents python creating .pyc files | |
| PYTHONDONTWRITEBYTECODE=1 \ | |
| # poetry | |
| # make poetry install to this location | |
| POETRY_HOME="/opt/poetry" \ | |
| # make poetry create the virtual environment in the project's root |
| # syntax=docker/dockerfile:1 | |
| # Keep this syntax directive! It's used to enable Docker BuildKit | |
| # Based on https://github.com/python-poetry/poetry/discussions/1879?sort=top#discussioncomment-216865 | |
| # but I try to keep it updated (see history) | |
| ################################ | |
| # PYTHON-BASE | |
| # Sets up all our shared environment variables | |
| ################################ |
| module.exports = { | |
| "parser": "@babel/eslint-parser", | |
| "env": { | |
| "browser": true, | |
| "es2021": true | |
| }, | |
| "extends": "plugin:react/recommended", | |
| "parserOptions": { | |
| "requireConfigFile": false, | |
| "ecmaFeatures": { |
| ------------------------------- MODULE Clock ------------------------------- | |
| EXTENDS Naturals | |
| VARIABLES hour, minute, second | |
| Init == | |
| /\ hour = 0 | |
| /\ minute = 0 | |
| /\ second = 0 |
| ---------------------------- MODULE TwoCounters ---------------------------- | |
| EXTENDS Integers | |
| CONSTANT C, Limit | |
| VARIABLES counter | |
| Init == | |
| counter = [c \in C |-> 0] | |
| Next == |
| <?xml version="1.0" encoding="UTF-16"?> | |
| <Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task"> | |
| <RegistrationInfo> | |
| <Date>2021-09-26T17:04:07.1303814</Date> | |
| <Author>jbrinkma</Author> | |
| <URI>\Daily Timesheet</URI> | |
| </RegistrationInfo> | |
| <Triggers> | |
| <CalendarTrigger> | |
| <StartBoundary>2021-09-26T16:45:00</StartBoundary> |
OOP Design (object-oriented programming) is a good exercise to show how to split up our system into different components. You can think of React Components but instead, we are separating our system into different objects/classes. The important factor of this problem and problems like these are that they are opened ended and force you to think abstractly and creatively. The main goal of this exercise is to be able to draw out diagrams to communicate abstract ideas before they begin to be implemented with code.
These problems are language agnostic (meaning language-neutral, or cross-language)
Unless otherwise noted (either in this file or in a file's copyright section) the contents of this gist are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.
If you more tips and advice like these, you can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! This gist is all about Homebrew, so if you like it you can support it by donating to them or becoming one of their Github Sponsors.