If you use Claude Code, you already know that a good CLAUDE.md is the difference between Claude following your conventions and Claude doing whatever it wants.
The problem is writing a genuinely useful one takes real effort. You need to think through:
- File naming conventions with examples
- Library preferences (and why NOT the alternatives)
- Anti-patterns specific to your stack
- TypeScript/language strictness rules
- Architectural decisions Claude should always respect
I spent time building 20 production-ready templates so you don't have to start from scratch.
👉 https://github.com/sx4im/awesome-claude-md
Stacks covered: Next.js 14, React/Vite, FastAPI, Flutter, SaaS boilerplate, Turborepo, ML Python, OSS libraries, Go, Rust, SvelteKit, Nuxt, Astro, Electron, Laravel, Express/TypeScript, React Native/Expo, Django, CLI Node, Chrome Extension.
All MIT licensed. Contributions welcome.
What stack would you want added next?
Top comments (0)