Coding agents operate differently from chat-based LLMs — they read and write real files, execute terminal commands, install packages, and make decisions between steps without checking in with you. A poorly scoped prompt doesn’t just produce a bad answer; it can delete the wrong files, overwrite logic you need, or spin through fifty tool calls before you can intervene. Prompt Master applies agentic prompting rules that define not just what to build, but where to stop, what to leave untouched, and when to ask for human review.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/nidhinjs/prompt-master/llms.txt
Use this file to discover all available pages before exploring further.
Claude Code
Claude Code is Anthropic’s agentic coding tool. Opus 4.8 is the default model. It is exceptionally capable but tends to over-engineer solutions — adding abstraction layers, utility functions, and refactors that were never requested. Two constraints are non-negotiable in every Claude Code prompt.Always append
Only make changes directly requested. to every Claude Code prompt. Always include explicit stop conditions — without them, Claude Code will continue making decisions until it runs out of context or confidence.Template M: Claude Code Agentic Structure
Template M: Claude Code Agentic Structure
| Section | Purpose | Example |
|---|---|---|
| Starting state | What exists right now | Express 4.x app, no auth middleware, routes in /src/routes/ |
| Target state | The exact finished result | JWT auth on all /api/* routes; public routes unchanged |
| Allowed actions | What Claude Code may do | Edit files in /src/auth/ and /src/middleware/ only |
| Forbidden actions | What Claude Code must not do | Do not modify /src/routes/public.ts, do not install new packages |
| Stop conditions | When to pause and wait | Stop before running any migration; stop if a test fails |
| Checkpoints | Human review triggers | Show me the middleware file before applying it to routes |
Full Template M Example
Additional Claude Code Rules
- Session hygiene — start a new Claude Code session for each distinct task; accumulated context from prior tasks causes drift and unintended changes
- Scope to specific files — always name the exact files that may be changed; open-ended scope causes unwanted edits across the codebase
- Human review triggers — for high-risk operations (schema changes, auth logic, environment config), require Claude Code to show you the change before applying it
Cursor / Windsurf
Cursor and Windsurf are IDE-integrated AI tools. They work best with a precise six-part structure that pins the change to an exact location in the codebase and defines when the task is complete.File-Scope Template
| Field | Required | Notes |
|---|---|---|
| File path | ✅ | Exact relative path from project root |
| Function/component name | ✅ | Pin the change to a specific scope |
| Current behavior | ✅ | What it does now |
| Desired change | ✅ | What it should do instead |
| Do-not-touch list | ✅ | Files, functions, props, classes off-limits |
| Language/version | ✅ | e.g. TypeScript 5.x, Python 3.12 |
Done when: | ✅ | Observable completion condition |
Cline
Cline is an agentic VS Code extension that can run terminal commands, edit files, and install packages directly in your editor. Like Claude Code, it needs explicit scope and gate conditions — but it has one additional critical constraint.- Starting state + target state — same as Claude Code Template M; define where you are and where you’re going
- File scope — list the exact files Cline may read and edit
- Stop conditions — define when Cline should pause before continuing
- Approval gates — require confirmation before any destructive or irreversible action
Ask before running terminal commands— mandatory on every prompt
GitHub Copilot
GitHub Copilot’s suggestion quality is entirely dependent on the code immediately surrounding the cursor. It does not use long conversational context — it uses local code signals. The most reliable technique is to write the full function signature and a detailed docstring immediately before invoking a suggestion.- Exact function signature before invocation — Copilot reads the signature as the primary instruction
- Docstring with types, return value, and edge cases — more specific docstrings produce dramatically better suggestions
- Describe input types and return type explicitly — Copilot infers from the signature; make it unambiguous
- Describe edge cases in the docstring —
handles empty input,raises ValueError if x < 0,returns None when not found - The prompt IS the code context — position your cursor immediately after the docstring before accepting a suggestion
Antigravity (Google, Gemini 3 Pro)
Antigravity is Google’s agentic AI tool powered by Gemini 3 Pro. It uses task-based prompting and has browser automation built in. The recommended approach is to prompt for an Artifact (a self-contained deliverable) first, then use browser automation for tasks that require it.- Task-based prompting — describe the complete task as a unit of work, not a sequence of steps
- Prompt for Artifact first — request a concrete, self-contained output (document, code file, structured data) before complex automation
- Browser automation is built-in — specify if the task requires web research, form interaction, or page navigation
- Specify autonomy level — define how much Antigravity should decide independently vs. confirm with you
Bolt / v0 / Lovable / Figma Make / Google Stitch
These are full-stack UI and application generators. They scaffold entire projects from a prompt — which means an under-scoped prompt will generate a complete application with frameworks, auth, database, and features you didn’t ask for. The primary rule is scope down explicitly.- Scope down explicitly — list what you want built and what you don’t
- Specify stack and version —
React 18 + TypeScript,Next.js 14 App Router,Vue 3 + Vite - State what NOT to scaffold —
no authentication,no database,no deployment config,no testing setup - Define the single deliverable — these tools work best with one focused output per prompt
Devin / SWE-agent
Devin and SWE-agent are fully autonomous software engineering agents. They can clone repositories, navigate codebases, run tests, create branches, and submit pull requests with minimal check-ins. This autonomy makes forbidden actions and filesystem scope non-negotiable.- Explicit starting state + target state — same Template M structure as Claude Code; define both precisely
- Forbidden actions list is critical — specify every category of action the agent must not take
- Scope the filesystem — name which directories and files the agent may access; exclude everything else
- Define the completion artifact — specify what the final deliverable is (PR, diff, test results, modified file)