CLAUDE.md templates
Battle-tested project context for React / Next.js, Python / FastAPI, Node / Express, React Native, and Data Science / ML. Each specifies stack, conventions, testing posture, and off-limits files.
Five CLAUDE.md templates, ten slash commands, a hooks cookbook, and twenty power prompts — written and used by people who ship with Claude Code daily. Drop them in, get productive immediately.
If you've used Claude Code for more than a week you've hit all of these.
The first 10 minutes of every session go to correcting the same mistakes.
Claude touches files you told it not to touch. It picks the wrong library. Writes tests that check implementation details instead of behavior. Commits directly to main. Chooses a pattern that doesn't match your codebase.
The fix is CLAUDE.md — a project context file Claude reads at the start of every session. With a well-written one, Claude knows your stack, your conventions, which files are off-limits, and how you want tests written.
Writing a good CLAUDE.md from scratch takes hours of trial and error. This kit gives you five battle-tested ones — plus the slash commands, hooks, and prompts that make Claude Code work reliably.
Not a course. Not a Notion page. Drop-in configuration you paste and keep.
Battle-tested project context for React / Next.js, Python / FastAPI, Node / Express, React Native, and Data Science / ML. Each specifies stack, conventions, testing posture, and off-limits files.
Install once, use in any project. Each command gives Claude a precise, repeatable workflow instead of having to explain the same thing every time.
Five practical hooks, each with copy-paste settings.json and a plain-English explainer: block commits to main, run tests on edit, show git status on stop, warn before delete, log all tool calls.
Solo and team profiles. One trusts Claude broadly with destructive-command guards; the other enforces branch protection and no direct-to-main commits. New to the file? Read the settings.json scopes & keys guide.
High-signal prompts for where Claude users most often stall: prod-error stack traces, integration tests, auth audits, schema design, CLI generation, README-from-code. Copy and paste straight into any session.
Answers the "am I buying five Markdown files or a real kit" question up front.
Concrete differences in how every Claude Code session starts.
/debug instead of describing your entire debugging process from scratch every time you hit a bug./code-review before every commit — catch security issues, logic errors, and quality problems before they ship./plan before any multi-file change — Claude produces a step-by-step plan and waits for your approval before writing code./ship before opening a PR — automated checklist covering tests, security, scope, and documentation.The kit isn't instructions. It's the configuration you wish someone had handed you on day one.
— the whole point
One click. No account. No payment.
Kit is free to use in any project, commercial or personal. If it saves you time, consider tipping the maker via BTC (optional).
No obligation. Only if the kit saved you time.
5,000 sats = "thanks" · 50,000 sats = "this saved me hours"
Common questions about the kit.
A ZIP file containing Markdown files (.md) and JSON files. Everything opens in any text editor — VS Code, Cursor, Sublime, or the built-in macOS/Windows editors. No special software required.
All current versions of Claude Code (1.x and 2.x). The templates use standard CLAUDE.md syntax that Claude Code has supported since launch. The slash commands use the skill/SKILL.md format introduced in late 2024.
Copy the .md files from skill-templates/ to ~/.claude/skills/ for global use, or to .claude/skills/ in your project for project-specific commands. The included README has exact instructions.
Yes. The slash commands, hooks cookbook, settings profiles, and power prompts work regardless of your stack. The CLAUDE.md templates are also easy to adapt — the structure and conventions transfer to any language or framework.
Click the "Download the kit (ZIP)" button above. It links directly to the GitHub Release — no sign-up, no payment, no wait. The ZIP is free to use in any project.
Hand-built single-file games, quizzes, and visualizers — no signup, no tracking, no cost.