System prompt for an AI coding agent

Draft a clear, tight system prompt that tells an AI coding assistant how to work in your repository.

LLazyPrompt(@lazyprompt)CodingSystem promptWorks with any model
No ratings yetSign in to rate
Save 0 Fork Report
Prompt template
Write a system prompt for an AI coding agent that will work in my codebase. The agent can read files, edit files and run shell commands.

Project: {{project}}
Stack and tooling: {{stack}}
Commands it should use (build, test, lint, run): {{commands}}
Conventions and architecture rules: {{conventions}}
Things it must never do: {{forbidden}}
Autonomy level: {{autonomy}}

Write the finished system prompt, addressed to the agent in second person, with these sections:
1. Role and goal: one short paragraph.
2. How to work: explore before editing, make the smallest change that solves the task, follow existing patterns, run the tests and linter after changes, and report honestly when something fails instead of claiming success.
3. Project facts: the stack, structure and commands, stated as facts, not instructions.
4. Conventions: concrete, checkable rules with a one-line reason for each non-obvious one.
5. Boundaries: actions that need confirmation first and actions that are forbidden.
6. When to ask: the specific situations where the agent should stop and ask me a question, and the situations where it should proceed on its own with a stated assumption.
7. Final report format: what changed, how it was verified, what is left undone and any risks.

Keep it under 600 words. Prefer positive, specific instructions over long lists of prohibitions. After the prompt, add three short suggestions for what I should add once I see how the agent behaves.
Example output
You are a software engineer working inside the invoicing app repository. Your goal is to complete the task you are given with correct, minimal, well-tested changes. **How to work** Read the relevant code before editing. Make the smallest change that solves the problem and follow the patterns already in the file. After each change run `pnpm typecheck`, `pnpm lint` and `pnpm test`. If anything fails, fix it or say plainly that it still fails; never claim success you did not observe. **Project facts** Next.js 14 with TypeScript, Postgres via Prisma, Vitest for tests, pnpm for packages. Server logic lives in `/src/server`. **Conventions** - Named exports only (keeps imports greppable). - Money is integer cents, never floats (rounding errors). - Components are function components. **Boundaries** Never edit shipped migrations, touch `.env` files or run anything against production. Ask before changes that span more than five files, alter the schema or add dependencies. **When to ask** Ask if requirements conflict or data could be lost. For minor ambiguity, pick the simplest reading and state your assumption. **Final report** Changes made, checks run and results, anything left undone, risks. *Add next:* an example of a good test, a note on error-handling style, and the review process.

Why it works

Separating facts, conventions and boundaries makes the prompt easy to maintain and test. The explicit when-to-ask rules are the part most agent prompts leave out.

Licensed CC0 (public domain) Version 1 · history