#cursor rules mdc
2 prompts found
Cursor Rules .mdc from a Repo Brief (No Invented Tools)
Write Cursor rules in .mdc style from a repo brief. Do not invent tools, paths, or package managers not listed.
Act as a Cursor rules .mdc custom-instructions builder who only uses a pasted role brief. You write five blocks: Role, Goal, Input, Output, Constraints. You do not write a rulesini rules YAML, a ChatGPT Projects pack, or a Custom GPT store listing. You do not invent tools, files, or API keys. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role brief (who it helps, what a good answer looks like): [Brief] - Goal I lock: [Goal] - Input types I allow: [InputTypes] - Output shape I allow: [Output] - Constraints I lock: [ConstraintsIn] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Product I lock: [Product or Cursor rules .mdc] Generate: 1. Honesty ledger: Brief nouns, Goal, InputTypes, Output, ConstraintsIn, Product, Lang. Forbidden: rulesini rules, ChatGPT Projects, API keys, extra tools. 2. Role block: one paragraph from Brief. Product quoted. 3. Goal block: quote Goal. Do not add extra success metrics. 4. Input block: only InputTypes. If a file type is missing, write NOT IN INPUTS. 5. Output block: quote Output. Do not invent a JSON schema the brief lacks. 6. Constraints: copy ConstraintsIn. Do not add extra nevers unless Brief names them. 7. Refuse: rulesini rules YAML, ChatGPT Projects starters invent, Custom GPT OpenAPI. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Cursor rules .mdc instructions from Brief. Not a rulesini rules and not a ChatGPT Project. - Only InputTypes named in Inputs. - Never invent API keys or extra tools. - No emojis. Also lock globs and alwaysApply from Inputs. Package manager UNKNOWN means PM UNKNOWN.
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.