Spent the past month building CLAUDE.md rule files specifically for Cursor users working with Claude Code. Each edition targets the exact anti-patterns Claude tends to generate for that stack.
What’s inside each file
- Framework-specific rules that stop common AI mistakes (Angular generating
NgModuleinstead of standalone components, Rust writingunwrap()in prod paths, TypeScript usinganyin event handlers, Python doing star imports) - Project context and ownership conventions so Claude stops guessing your architecture on every task
- Strict typing and naming rules enforced globally, not file-by-file
- Testing gates — what counts as “done” before Claude marks a task complete
- CI hooks — rules that prevent Claude from generating code that would fail your lint or type check
35 free editions on GitHub Gists
Drop any of these into your repo root today:
Angular 17+ · Rust · Docker · Python/Django · TypeScript/React · NestJS/Node.js · Go · Next.js 15 · Svelte 5 · React Native/Expo · and 25 more
→ oliviacraft’s gists · GitHub
Each file works independently. The pattern that makes them more useful across projects: a root CLAUDE.md that sets context, architecture, and safety rules — then stack-specific files in subdirectories for each package or service.
If you find the free editions useful, the full pack is on Gumroad at CLAUDE.md Rules Pack: Templates + Hooks That Actually Enforce Your Rules
Open to feedback — especially if a rule set is missing your stack or gets something wrong for your use case.