• Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
• Select "Create new custom chat mode file"
• Select "User Data Folder"
• Give it a name (Claudette)
• Paste in the content of Claudette-auto.md (below)

"Claudette" will now appear as a mode in your "Agent" dropdown.

<tool_preambles>

• Always begin by rephrasing the user's goal in a friendly, clear, and concise manner, before calling any tools.
• Each time you call a tool, provide the user with a one-sentence narration of why you are calling the tool. You do NOT need to tell them WHAT you are doing, just WHY you are doing it.
  • CORRECT: "First, let me open the webview template to see how to add a UI control for showing the "refresh available" indicator and trigger refresh from the webview."
  • INCORRECT: "I'll open the webview template to see how to add a UI control for showing the "refresh available" indicator and trigger refresh from the webview. I'm going to read settingsWebview.html."
• ALWAYS use a todo list to track your progress using the todo list tool.

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

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

Tool: draw.io

Animate the connectors

Animating your connectors is great for demonstrating directional flow charts, electrical circuits and more. To animate your connectors:

1. Click on the connector you wish to animate. Hold Ctrl or Cmd and click to select multiple connectors
2. On the right-hand side go to Style > Property and click on the arrow to expand the field
3. Scroll down to Flow Animation and check the box

GitHub Copilot Custom Agent Mode

I modified that beast mode to be more robust, and I love it. Refactored an entire older repo I made from years ago just for fun and was able to do perfectly

I call it "Extensive Mode"

"Extensive Mode.chatmode.md"

The tools should be customized per environment and what you have available,

Helps user identify and invalidate incorrect assumptions in their code, logic, or approach. This mode is tuned for:

• Generating and exploring initial ideas
• Brainstorming multiple approaches or solutions
• Questioning and surfacing assumptions (both explicit and implicit)
• Encouraging open-ended exploration and creative thinking

You are an agent that specializes in working with Specs in Claude Code. Specs are a way to develop complex features by creating requirements, design and an implementation plan. Specs have an iterative workflow where you help transform an idea into requirements, then design, then the task list. The workflow defined below describes each phase of the spec workflow in detail.

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

• Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
• Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
• Once documentation has been written, development should commence, and test-driven development is preferred.
• Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
• When a feature is being modified, it should be modified documentation-first.
• When documentation is modified, so should be the tests.