Claude Code folder structure cheat sheet from Reddit user
A Reddit user shared a cheat sheet for Claude Code's folder structure after repeatedly getting tripped up by documentation that required jumping between multiple pages. The cheat sheet covers practical implementation details that caused real time-wasting issues.
Key folder structure details
- Skills belong in
.claude/skills/, not a top-levelskills/folder - Each skill needs its own directory with an
SKILL.mdfile inside it - Subagents live in
.claude/agents/, not a standaloneagents/folder at the root
Hook configuration specifics
- For PostToolUse hooks, the matcher needs to be
"Edit|MultiEdit|Write"— using just"Write"misses edits - SessionStart and SessionEnd are real hook events (contrary to some community discussions)
Installation and documentation notes
npm installis no longer the recommended install path- The native installer is:
curl -fsSL https://claude.ai/install.sh | bash - Documentation updates happen quietly, so the cheat sheet may contain inaccuracies as docs evolve
The cheat sheet is currently available as an image, though the creator mentioned potentially converting it to a proper Markdown file if there's sufficient interest. The image format was chosen for faster initial creation.
📖 Read the full source: r/ClaudeAI
👀 See Also
Fix for sub-agents not showing up in OpenClaw v2026.3.13
A workaround for OpenClaw v2026.3.13 where custom sub-agents don't appear in the agent list: simplify the openclaw.json agent list to only include IDs and manually register agents in runs.json with status set to 'idle'.
OpenClaw 2026.3.7 breaks Kimi tool calls, downgrade to 2026.3.2 fixes regression
OpenClaw version 2026.3.7 has a regression where the Kimi API provider outputs raw <function_calls> XML instead of executing tools. The solution is to downgrade to version 2026.3.2 and restore a compatible config file.
Creating Custom Skills for Claude Co-Work: Best Practices and Formats
Explore best practices for creating custom skills for Claude Co-Work with specific formatting tips and implementation advice from user-experienced insights.
100 Tips for Building a Personal AI Agent: From Cloud Prototype to Production
Six weeks of building a persistent AI agent — not a chatbot wrapper — that manages tasks, tracks deals, reads emails, and analyzes data. Key lessons: Write a Constitution not a system prompt, use flat markdown files for memory, and version your identity file in git.