Ultima attività 1 day ago

Sharizzle ha revisionato questo gist 1 day ago. Vai alla revisione

1 file changed, 14 insertions

claude-md-command.md(file creato)

@@ -0,0 +1,14 @@
1 + Analyze this codebase and create a CLAUDE.md file following these principles:
2 +
3 + 1. Keep it under 150 lines total - focus only on universally applicable information
4 + 2. Cover the essentials: WHAT (tech stack, project structure), WHY (purpose), and HOW (build/test commands)
5 + 3. Use Progressive Disclosure: instead of including all instructions, create a brief index pointing to other markdown files in .claude/docs/ for specialized topics
6 + 4. Include file:line references instead of code snippets
7 + 5. Assume I'll use linters for code style - don't include formatting guidelines
8 +
9 + Structure it as: project overview, tech stack, key directories/their purposes, essential build/test commands, and a list of additional documentation files Claude should check when relevant.
10 +
11 + Additionally, extract patterns you observe into separate files:
12 + - .claude/docs/architectural_patterns.md - document the architectural patterns, design decisions, and conventions used (e.g., dependency injection, state management, API design patterns). Make sure these are patterns that appear in multiple files.
13 +
14 + Reference these files in the CLAUDE.md's "Additional Documentation" section.
Più nuovi Più vecchi