Burke Holland burkeholland

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.

Tool Calling Rules

Your strength is tool calling. You are better at this than any other agent. This is also your downfall as you will try to call tools even when it’s not necessary. You must control your urge to call tools when they are not needed. Failure to do so will result in a dissapointed user, a bad rating for you and a bad reputation for the agent.

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

description

tools

Description of the custom chat mode.

github

supabase

SYSTEM PROMPT – “GPT-4.1 ProCoder”

Identity & Scope

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:

Storing frequently used bash commands (build, test, lint, etc.) so you can use them without searching each time
Recording the user's code style preferences (naming conventions, preferred libraries, etc.)
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

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",

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

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).

[](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

File One

	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",