Cursor prompts for project rules, AGENTS.md and review lists

Turn this README into a root AGENTS.md for Cursor. README: [PASTE README]. Keep sections: What this repo is, How to run, Where new code goes, What not to do. Use short imperative bullets. Copy commands and paths only if they appear in the README. If a run command is missing, write [VERIFY] in How to run rather than inventing one. Do not invent a stack, a cloud host or a script. Output the full AGENTS.md in one code block, under 200 lines, with no frontmatter.

Write a nested AGENTS.md for the folder [PACKAGE PATH] in this monorepo. Package README or notes: [PASTE PACKAGE NOTES]. Root rules already say: [ROOT RULES SUMMARY]. The nested file should add only what is true inside [PACKAGE PATH]: commands, entry files and conventions from the notes. If the notes lack a test command, write [VERIFY]. Do not invent a package manager or a deploy target. Do not repeat the root summary. Explain in one line at the top that these instructions apply when Agent works under this folder.

I have both files. AGENTS.md: [PASTE AGENTS MD]. CLAUDE.md: [PASTE CLAUDE MD]. Cursor reads both as always-on project instructions. Make a table with columns Topic, AGENTS.md says, CLAUDE.md says, and Action (keep one, merge, or [VERIFY] if they conflict and I gave no winner). Do not invent a third policy. Do not add a tool either file omitted. After the table, draft a merged AGENTS.md under 160 lines that prefers [SOURCE OF TRUTH] when both speak, and tags gaps [VERIFY] when neither does.

Cut this AGENTS.md to [TARGET LINE COUNT] lines without losing commands. Current file: [PASTE AGENTS MD]. Keep: runnable commands, paths, and hard forbids. Drop: history, praise, and duplicated bullets. If a command is mentioned but not shown, write [VERIFY] rather than inventing flags. Do not invent a new section. Output the shortened file, then a list of dropped bullets grouped as safe to drop or ask me. Stay under the target line count.

Write a 80 to 120 word 'First hour' section for AGENTS.md for a new teammate on [PROJECT NAME]. Allowed facts: [ONBOARDING FACTS]. Include: which folder to open, which command to run, which rule files to read. If a fact is missing, put [VERIFY] in that sentence. Do not invent a Slack channel, a person or a badge. Do not mention debug workflows. Output only the section, as markdown, ready to paste under a heading First hour.

Create a Cursor project rule that applies only to files matching [GLOB PATTERN]. Confirmed conventions for that area: [AREA CONVENTIONS]. Frontmatter: alwaysApply false, globs: the pattern I gave, and a one-line description. Body: at most 10 bullets copied from the conventions. If a convention names a file that I did not list in [AREA FILE EXAMPLES], tag that bullet [VERIFY] and do not invent a path. Do not invent a linter. Output the full .mdc I can save under .cursor/rules/.

Write the description field and body for a rule the agent should pull in only when relevant. Topic: [RULE TOPIC]. When it should apply: [WHEN TO APPLY]. When it must stay out: [WHEN TO STAY OUT]. Frontmatter: alwaysApply false, no globs, description under 20 words that a model can match. Body under 10 bullets from [CONFIRMED FACTS]. If a fact is missing, write [VERIFY]. Do not invent an API, a flag or a folder. The description must not repeat the whole body.

Write a rule I will @-mention as @[RULE SLUG] when I want it. Job it encodes: [MANUAL JOB]. Steps the agent must follow, from my notes: [PASTE STEPS]. Frontmatter: alwaysApply false, no globs, no description (so it stays manual). If a step needs a path or command I did not give, write [VERIFY] in that step. Do not invent a CLI flag. Output the .mdc and, under it, the exact @ mention I should type in chat. Keep the body under 15 numbered steps.

This single rule file mixes concerns: [PASTE MDC]. Split it into up to four .mdc files. For each, choose Always, Glob [suggested glob from [KNOWN PATHS]], Intelligent, or Manual. Copy bullets; do not invent new ones. If a bullet needs a glob but [KNOWN PATHS] has no match, mark that file's glob [VERIFY]. Output each file with frontmatter. Do not invent a fifth concern. End with a one-line note on which file should stay always-applied, if any.

Write two glob-scoped rules, one for [FRONTEND GLOB] and one for [API GLOB]. Frontend conventions: [FRONTEND CONVENTIONS]. API conventions: [API CONVENTIONS]. Each file: alwaysApply false, matching globs, description in one line, body of at most 8 bullets. If a convention would apply to both, put it in neither file and list it under Shared for me to add to AGENTS.md. Do not invent a component library or an HTTP framework. If a glob is blank, write [VERIFY] in that file's frontmatter instead of inventing a pattern.

Write a Cursor rule that Agent must walk before it says a change is ready. Change type: [CHANGE TYPE]. Checklist items I already use: [PASTE CHECKLIST]. Format the body as a numbered list the agent prints and ticks. If an item needs a command I did not give, write [VERIFY] beside it. Do not invent a coverage number, a reviewer name or a merge bot. Frontmatter: alwaysApply false, globs [REVIEW GLOBS], description 'print this review checklist before claiming done'. Keep the list to 12 items or fewer.

Create a review checklist rule for HTTP or RPC changes. Endpoints I actually have, from [PASTE ROUTES OR SCHEMA]: only those. The agent must list each changed endpoint, the request fields, the response fields, and whether a field was added, removed or renamed. If a field appears in the diff but not in the pasted schema, mark it [VERIFY] and do not invent a type. Do not invent an endpoint. Output .mdc with globs [API GLOBS], alwaysApply false, and a body that forbids claiming 'no breaking change' without filling the table.

Write a checklist rule for schema migrations in [MIGRATION FOLDER]. Required checks from our notes: [MIGRATION CHECKS]. The agent must refuse to mark a migration done if a check is unanswered. If a check needs a production fact I did not paste, that line is [VERIFY], not a guess. Do not invent a lock, a vendor, or a rollback tool. Frontmatter: globs [MIGRATION GLOB], alwaysApply false. Body: numbered checks, then a final line the agent must print: safe to apply or hold.

Draft a review rule for UI files matching [UI GLOB]. Checks I require: [A11Y CHECKS]. The agent must inspect only files in context and tick each check with evidence from the markup I pasted or @-mentioned. If a check needs a design token I did not give, write [VERIFY]. Do not invent a contrast ratio, a screen reader, or a legal standard. Frontmatter: alwaysApply false, globs [UI GLOB]. Body: at most 10 checks, each with a pass, fail or [VERIFY] slot.

Write a rule that forces a changelog line before Agent finishes a user-facing change. Changelog path: [CHANGELOG PATH]. Format we use: [ENTRY FORMAT]. The agent must draft one entry from the diff summary [DIFF SUMMARY] and stop if [CHANGELOG PATH] is blank, writing [VERIFY] instead of inventing a file. Do not invent a version number or a date. Do not claim a user-facing change is done with no entry. Frontmatter: alwaysApply false, description 'add a changelog line for user-facing diffs'.

Compare these Cursor instruction files for contradictions. Files: [PASTE RULE FILES]. List each conflict as a row: Topic, File A quote, File B quote, Suggested winner from [SOURCE OF TRUTH], or [VERIFY] if I named no winner. Do not invent a third quote. Do not add a rule that is in neither file. After the table, write two bullets I can paste to make the winner explicit in AGENTS.md. Keep quotes under 20 words each.

Here are our rule files and a list of paths that exist: [PASTE RULES] and [EXISTING PATHS]. Flag any glob that matches nothing in [EXISTING PATHS] as dead. Flag any always-applied bullet that names a command not in [CONFIRMED COMMANDS] as suspect. Output a table: Rule file, Issue, Evidence, Action (delete glob, retag [VERIFY], or keep). Do not invent a path. Do not invent a command. If [EXISTING PATHS] is short, say the hunt is incomplete rather than declaring the repo clean.

Measure these instruction files against a budget of [MAX LINES PER FILE] lines and [MAX ALWAYS APPLY FILES] always-applied files. Files: [PASTE FILES WITH NAMES]. Table: File, Lines, Apply mode, Over budget (yes or no). Then propose cuts that only delete repetition, listing each cut as a quote. If you cannot tell the apply mode from frontmatter, write [VERIFY] in Apply mode. Do not invent a line count. Do not invent a new file to hold leftovers unless I set [ALLOW SPLIT] to yes.

I want to add this rule: [PROPOSED RULE]. Evidence from the repo: [PASTE EVIDENCE]. For each bullet, mark Supported, Unsupported or [VERIFY]. Unsupported bullets must be deleted in a rewritten rule, not softened. Do not invent evidence. Do not keep a bullet because it sounds like a best practice. Output the rewritten .mdc with the same apply mode as [APPLY MODE], and a short list of bullets you dropped.

I changed a rule. Old: [OLD RULE]. New: [NEW RULE]. Same task I will ask Agent: [SAMPLE TASK]. List what the agent is now told to do that it was not told before, and what it lost. If the new rule names a path, command or library that is not in [CONFIRMED FACTS], mark it [VERIFY] as a possible invention. Do not invent a quality score. End with keep, revert or edit again. Stay under 180 words.

Sort these bullets into User rules (this machine, all repos) versus Project rules (this repo). Bullets: [PASTE BULLETS]. Project: [PROJECT NAME]. Output two lists. A bullet that names a path in this repo goes to Project. A bullet about my tone or editor goes to User. If a bullet could be either, mark it [VERIFY] and ask one question. Do not invent a bullet. Do not put secrets in either list. After the lists, draft the Project list as AGENTS.md bullets only.

Write a glob-scoped rule for imports under [SOURCE GLOB]. Confirmed examples from the repo: [PASTE IMPORT EXAMPLES]. Encode: alias versus relative, barrel files yes or no from the examples, and forbidden packages from [FORBIDDEN PACKAGES]. If the examples disagree, write [VERIFY] and do not pick a winner. Do not invent an alias that is not in the examples. Frontmatter: alwaysApply false, globs [SOURCE GLOB]. Body: at most 8 bullets plus one counter-example copied from the paste.

Draft a rule for how we handle errors in [AREA GLOB]. Patterns I confirmed: [ERROR PATTERNS]. The agent must follow those patterns and must not invent a new helper, a telemetry vendor or a catch-all. If a pattern names a type that is not in [PASTE TYPE NAMES], mark it [VERIFY]. Frontmatter: alwaysApply false, globs [AREA GLOB], description under 18 words. Body: do, do not, and one example copied from [PASTE EXAMPLE], shortened to 20 lines.

Write a rule for feature flags in [FLAG FILES GLOB]. Flag names already in the repo: [FLAG NAMES]. Naming pattern I want: [NAMING PATTERN]. The agent must reuse a name from the list when the job matches, and must not invent a flag. If it needs a new name, it must propose one that matches the pattern and wait, tagging the proposal [VERIFY] until I accept. Do not invent a flag service. Frontmatter: alwaysApply false, globs [FLAG FILES GLOB]. Body under 10 bullets.

Write an always-applied rule for chats that only edit docs under [DOCS GLOB]. If the user is clearly asking for documentation, the agent must not change application code. If the request is mixed, it must list the code files it would touch and wait. Docs folder: [DOCS GLOB]. Do not invent a docs generator or a site host. If [DOCS GLOB] is blank, write [VERIFY] and still forbid surprise code edits. Frontmatter: alwaysApply true. Body under 100 words.