| description | Prompt for analyzing Claude Code best practices from engineering sources |
|---|
Analyze best practices for using Claude Code based on sources listed in @sources.csv
(content available in source_content/ folder).
- Separate general vs. AI-specific practices: Identify content that applies to traditional software development vs. practices specifically important for agentic AI coding
- Highlight fundamentals: Mark general engineering practices (version control, testing, CI) that have heightened importance when working with AI agents
- Document criteria: Note why each practice is categorized as general or AI-specific
- Group by semantic areas: Create logical categories (e.g., Testing Strategies, Prompt Engineering, Code Review, CI/CD Integration)
- Highlight consensus: Identify practices mentioned in 2+ sources and note the frequency
- Note contradictions: Flag conflicting recommendations with source attribution
Apply these criteria to each practice:
- Impact: High/Medium/Low value for production software quality
- Effort: Implementation complexity and learning curve
- Specificity: How unique this is to Claude Code vs. general AI coding
- Evidence: Whether the source provides data, examples, or anecdotal support
Flag items as:
- ✅ Highly recommended (high impact, reasonable effort, well reasoned, well substantiated)
⚠️ Context-dependent (valuable in specific scenarios)- ❌ Low priority (minimal impact or excessive effort or insufficient evidence provided)
These are soft guidlines.
Format: Markdown report saved as claude-code-best-practices-report.md
Structure:
- Executive Summary (2-3 key takeaways)
- General Best Practices
- Best Practices that are eve more crucial in agentic AI coding workflows
- Core Recommendations by Category (with priority/importance/impact flags)
- Highlight consensus Findings (practices cited by multiple sources) in each category
- If sources conflict, present both views with source attribution rather than choosing
- Contradictions & Trade-offs
- Appendix:
- Source mapping table
- Complete set of recommendations
Style:
- Target audience: Software engineers building production systems with Claude Code
- Depth: Sufficient detail for actionability without excessive verbosity
- Include code examples where relevant
- Maximum length: 5000 words
- If
source_content/is missing, STOP AND RAISE A FLAG.