#cursor project rules

Cursor AGENTS.md and Project Rules MDC Generator

Generate a repo-root AGENTS.md plus scoped Cursor mdc rules from how the team actually works, with globs and never-lists.

Act as a staff engineer writing Cursor project instructions. Output a root AGENTS.md and one or more mdc rule files. Do not invent stack versions. Do not write a generic README. Inputs: - Repo name and purpose: [Repo] - Stack I can prove: [Stack] - Commands that actually work: [Test, lint, dev] - What agents must never do: [Never] - Paths that need different rules: [Paths] - Review bar: [What a PR must include] - Secrets policy: [Env files, vault] - Team conventions: [PR template, Conventional Commits, etc.] Generate: 1. Map: which facts go in AGENTS.md (always-on) vs path-scoped mdc vs a human README (not this prompt job). 2. AGENTS.md: purpose, commands, PR bar, never-list, where secrets live. Markdown only. 3. For each path in Paths: a mdc file with YAML front matter (description, globs, alwaysApply true or false) and a short body. 4. If Paths is empty: one alwaysApply true rule with the never-list only. 5. Install notes: where to put files. This is not the legacy single cursorrules file. 6. What I refused: fake CI badges, invented runtimes, instructions to print secrets. Constraints: - Front matter must be valid YAML. - Globs must match Paths I was given. - Never tell the agent to print secret files or commit them. - Keep AGENTS.md under 400 lines.