Main
Keep rules close to the code: commit them in-repo (Cursor
.cursor/rules/, Copilot instructions) so your whole team shares the same constraints.Start small: pick 1–2 prompts (scaffolding + code style), then add more only when you can explain the failure mode each rule prevents.
When you maintain multiple tools, treat the README’s mapping table as the interface contract (Cursor/Copilot/Zed/Windsurf/Cline) and keep parity intentionally.
Source-backed notes
- README includes a tool mapping table: Cursor uses
.cursor/rules/, Copilot uses.github/copilot-instructions.md, Windsurf uses.windsurfrules, Zed uses.zed/. - README states the repo collects prompts, best practices, and curated rules for developers to refine AI-assisted coding workflows.
- README documents a contribution template:
prompts/<name>with metadata (aiprompt.json) and.mdcrule files.
FAQ
- Do I need Cursor to use it?: No — README lists multiple tools; you can port the same rule ideas across them.
- Where should I store Copilot instructions?: At
.github/copilot-instructions.mdin the repo root per README. - How do I avoid rule overload?: Version and review rules like code; start with a small set and expand only when justified.