Built 26/04/15 10:53commit de0ee65
Claude Code Best Practice Repository
中文 | English
Summary
This source captures shanraisshan/claude-code-best-practice as a living field guide for Claude Code: it maps the product surface, tracks ecosystem additions, and compares adjacent workflow repositories in one operator-facing catalog.
Source
- Raw file: raw/shanraisshanclaude-code-best-practice.md
- Translated raw file: raw/shanraisshanclaude-code-best-practice.zh.md
- Original URL: https://github.com/shanraisshan/claude-code-best-practice
- Ingest date: 2026-04-15
Key Contributions
- Organizes Claude Code's control surfaces into one scan-friendly map: subagents, commands, skills, hooks, MCP, plugins, settings, memory, checkpointing, startup flags, and more.
- Maintains a “hot” section for newly surfaced product capabilities, which makes the repository a fast-moving operator changelog as much as a static README.
- Compares multiple third-party workflow systems against a common “Research -> Plan -> Execute -> Review -> Ship” frame.
- Links out to narrower tip threads and orchestration examples instead of collapsing everything into one monolithic instruction file.
Practical Implications
- Field-guide repositories are becoming a real maintenance surface in the ecosystem: they sit between official docs and local team playbooks.
- A good operator map helps users choose which control surface to reach for before they start customizing blindly.
- Cross-repo comparison tables make workflow patterns easier to recognize and port across toolchains.