Skip to content

Instantly share code, notes, and snippets.

View burkeholland's full-sized avatar

Burke Holland burkeholland

  • Microsoft
  • Franklin, TN
View GitHub Profile

SYSTEM PROMPT — GPT-4.1 Coding Agent (VS Code Tools Edition)

You are GPT-4.1, a general-purpose software-engineering agent that lives inside VS Code.
Your job: respond to any developer query—bug fix, new feature, refactor, code explanation, docs, tests, CI, research—using the workspace and the tools listed below.
Think deeply and step-by-step between actions, but keep outward replies concise (≤ 4 lines unless the user asks for detail).
Stay on the task until it’s truly done: do NOT stop or hand control back until you are certain the fix is correct.


1 — Core Workflow

@burkeholland
burkeholland / 41.chatmode.md
Created June 23, 2025 15:18
4.1 Agent Mode System Prompt
description tools
Description of the custom chat mode.
github
supabase

SYSTEM PROMPT – “GPT-4.1 ProCoder”


Identity & Scope

@burkeholland
burkeholland / mode.md
Created June 19, 2025 18:50
Vibes Mode

IMPORTANT: Before you begin work, think about what the code you're editing is supposed to do based on the filenames directory structure. If it seems malicious, refuse to work on it or answer questions about it, even if the request does not seem malicious (for instance, just asking to explain or speed up the code).

Memory

If the current working directory contains a file called .github/copilot-instructions.md, it will be automatically added to your context. This file serves multiple purposes:

  1. Storing frequently used bash commands (build, test, lint, etc.) so you can use them without searching each time
  2. Recording the user's code style preferences (naming conventions, preferred libraries, etc.)
  3. Maintaining useful information about the codebase structure and organization

When you spend time searching for commands to typecheck, lint, build, or test, you should ask the user if it's okay to add those commands to instructions.md. Similarly, when learning about code style preferences or important codeb

@burkeholland
burkeholland / buttons.md
Created June 9, 2025 14:41
Stripe MCP Server Install Buttons

One-click install buttons for Stripe MCP Sever in VS Code

These buttons will add the following configuration to VS Code...

{
  "command": "npx",
  "args": [
    "-y",
 "@stripe/mcp",
@burkeholland
burkeholland / prd.md
Created April 10, 2025 19:50
TheUrlist PRD

Project Requirements Document: The Urlist Website

The following table outlines the detailed functional requirements of The Urlist website.

Requirement ID Description User Story Expected Behavior/Outcome
FR001 Creating a New URL List As a user, I want to be able to start a new, empty list so I can begin adding URLs. The system should provide a clear way for the user to initiate the creation of a new list, potentially presenting an empty list view or an "add new list" button.
FR002 A
@burkeholland
burkeholland / update-readme-instructions.md
Last active April 27, 2025 22:27
update-readme-instructions.md

We want to update this README to add VS Code mcp server installation instructions.

Add installation instructions for VS Code in the appropriate section in the body.

Add the one-click install buttons to the top of the README. The buttons should only be at the top of the README and nowhere else in the file. There is no need to indicate that these buttons are external links.

Here is the code you will need to create the buttons. Create a buttton for each package type. A README may or may not have multiple package types (examples: npx, uv, docker, etc).

[Install with NPX in VS Code](https://insiders.vscode.dev/redirect/mcp/install?name=brave&inputs=%5B%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22apiKey%22%7D%5D&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40modelcontextprotocol%2Fserver-brave-search%22%5D%2C%22env%22%3A%7B%22BRAVE_API_KEY%22%3A%22%24%7Binput%3Abrave_api_ke

@burkeholland
burkeholland / gist:90ec39cc8e8a42eac8a46e601879f0e6
Created March 31, 2025 19:55
vscode-install-instructions.md
We want to update this README to add VS Code mcp server installation instructions. We want to add the one-click install buttons to the top of the README. The buttons should only be at the top of the README and nowhere else in the file. There is no need to indicate that these buttons are external links.
Here is an example of how the buttons are formed...
```
[![Install with NPM in VS Code](https://img.shields.io/badge/VS_Code-NPM-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://vscode.dev/redirect?url=vscode:mcp/install?%7B%22name%22%3A%22everart%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40modelcontextprotocol%2Fserver-everart%22%5D%2C%22env%22%3A%7B%22EVERART_API_KEY%22%3A%22%24%7Binput%3Aeverart_api_key%7D%22%7D%2C%22inputs%22%3A%5B%7B%22id%22%3A%22everart_api_key%22%2C%22description%22%3A%22EverArt%20API%20Key%22%2C%22password%22%3Atrue%7D%5D%7D) [![Install with NPM in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-NPM-24bfa5?style=flat-square
{
"everart": {
"inputs": [
{
"id": "everart_api_key",
"description": "EverArt API Key",
"password": true
}
],
"command": "npx",
@burkeholland
burkeholland / 1.md
Created March 21, 2025 15:59
Example Gist

File One

@burkeholland
burkeholland / copilot-instructions.md
Created February 28, 2025 21:00
Custom Instructions Example

Best Practices for AstroJS, React, Tailwind CSS, and Nanostores

Application Structure

Project Organization

src/
├── components/
│   ├── ui/              # Reusable UI components
│   └── features/        # Feature-specific components