Documentation Project Structure

Q4_Sales_Report/ ├── CLAUDE.md # Writing conventions & style guide ├── executive_summary.md # High-level overview (write last) ├── methodology/ │ ├── data_sources.md # Where data comes from │ └── analysis_approach.md # How we analyzed ├── regional_performance/ │ ├── _overview.md # Regional summary │ ├── northeast_analysis.md │ ├── southwest_analysis.md │ ├── midwest_analysis.md │ └── trends.md # Cross-regional trends ├── product_lines/ │ ├── _overview.md # Product line summary │ ├── product_a.md │ ├── product_b.md │ └── comparison.md # Head-to-head comparison ├── financials/ │ ├── revenue_breakdown.md │ ├── cost_analysis.md │ └── projections.md ├── recommendations/ │ ├── immediate_actions.md # Quick wins (this quarter) │ └── long_term_strategy.md # 6-12 month roadmap ├── appendix/ │ ├── raw_data/ # Supporting data files │ │ ├── sales_q4.csv │ │ └── customer_survey.csv │ ├── glossary.md │ └── references.md └── assets/ ├── charts/ # Generated visualizations └── diagrams/ # CLAUDE.md for documentation projects: # - Use _overview.md as section summary (auto-generated from children). # - File names: snake_case, descriptive, no abbreviations. # - Every section folder must have an _overview.md. # - Data files go in appendix/raw_data/, never inline. # - Charts generated from data go in assets/charts/. # - Cross-references use relative markdown links. # - Style: professional, data-driven, avoid jargon. # - executive_summary.md is always written last, # synthesized from section _overview.md files.