Thanks for wanting to help. Here's how to make it easy for both of us.
- Fix a typo: edit any
.mdxfile incontent/docs/and open a PR - Suggest a topic: open an issue
- Share your template: submit your CLAUDE.md
- Report a bug: open a bug report
content/docs/
foundations/ # Core concepts (CLAUDE.md, sessions, memory, permissions)
workflows/ # Daily practice, debugging, team adoption, CI/CD
patterns/ # Advanced features (hooks, agents, MCP, autonomous loops)
templates/ # Copy-paste CLAUDE.md files
comparisons/ # Claude Code vs other tools
Every page should sound like a practitioner talking to a friend. Not documentation. Not a textbook.
Do this:
- Hook with a real question or hot take
- Take clear stances ("this is great" / "this is a waste of time")
- Short paragraphs, conversational rhythm
- Say "here's the deal" or "let me be real"
Don't do this:
- "In this section, we will explore..."
- "It is important to note that..."
- Walls of text without examples
- Feature lists without opinions
No exceptions. Every page must have at least one interactive terminal animation showing the feature in action:
<DemoCard title="What you'll see" steps={[
{ type: 'cmd', text: 'claude "your prompt here"' },
{ type: 'out', text: 'Claude Code output...' },
{ type: 'success', text: '✓ Something good happened' },
{ type: 'error', text: '✗ Something went wrong' },
{ type: 'warn', text: '→ The takeaway message' },
]} />Step types: cmd (user input), out (output), success (green), error (red), warn (amber).
- Create a
.mdxfile in the right folder - Add frontmatter:
---
title: Your Page Title
description: "A punchy one-liner. Not a paragraph."
---- Write content following the voice guide above
- Add at least one DemoCard
- Add the page slug to the folder's
meta.json - Open a PR
npm install
npm run devOpen localhost:3000.
Be kind. Be helpful. Everyone starts somewhere. If someone's contribution doesn't match the voice, help them fix it instead of rejecting it.