CLAUDE.md.template

<!--
⚠️ TARGET: UNDER 60 LINES (Anthropic Official Guidance)

This template is 117 lines to show all possibilities. Your CLAUDE.md should be MUCH shorter.

RULE: "Would removing this cause mistakes? If not, cut it."

KEEP: ✅ Project purpose (1-2 sentences) ✅ Key commands ✅ Known gotchas ✅ Current focus
CUT: ❌ Examples ❌ Essays ❌ Edge case docs ❌ Long command lists

See FOUNDATIONAL-PRINCIPLES.md for rationale.
-->

# {{PROJECT_NAME}} Project Context

## Project Purpose

{{PROJECT_PURPOSE}}

## Key Documentation Files

{{#if HAS_ARCHITECTURE}}
### ARCHITECTURE.md
**Purpose**: System architecture, directory structure, workflows
**Update Trigger**: Major milestones, infrastructure changes
{{/if}}

{{#if HAS_PLAN}}
### PLAN.md
**Purpose**: Current priorities, immediate next actions
**Update Trigger**: Weekly priority shifts, milestone completions
{{/if}}

{{#if HAS_INDEX}}
### INDEX.md
**Purpose**: Automated document inventory
**Update Trigger**: File structure changes
{{/if}}

## Current Phase

{{CURRENT_PHASE}}

## Project Structure

```
{{PROJECT_STRUCTURE}}
```

## Code Quality Standards

{{#if IS_CODING}}
- Write clean, maintainable code with clear intent
- Test-driven development where applicable
- Meaningful commit messages following conventional format
- No premature optimization
{{/if}}

{{#if IS_WRITING}}
- Evidence-based claims with documented sources
- Balanced perspective acknowledging trade-offs
- Academic quality suitable for peer review
- Intellectual honesty over marketing claims
{{/if}}

{{#if IS_RESEARCH}}
- Evidence tier classification for all claims
- Hypothesis tracking with confidence levels
- Source attribution and citation
- Reproducible methodology
{{/if}}

## Thinking Methodology

For deep analysis of complex topics, use the UltraThink methodology:

Apply the FRAME-ANALYZE-SYNTHESIZE protocol for:
- Technology evaluation and architecture decisions
- Problem-solving and strategic planning
- Complex debugging and root cause analysis

**FRAME**: Define problem, identify assumptions, clarify success criteria
**ANALYZE**: Evaluate alternatives, identify failure modes, assess trade-offs
**SYNTHESIZE**: Recommend approach, document rationale, plan implementation

## Claude Skills Infrastructure

### Personal Skills (6 universal skills)
Available via `~/.claude/skills/`:
- **systematic-debugger** - 4-phase root cause debugging
- **tdd-enforcer** - RED-GREEN-REFACTOR cycle
- **ultrathink-analyst** - FRAME-ANALYZE-SYNTHESIZE deep analysis
- **git-workflow-helper** - Commit message formatting
- **academic-citation-manager** - Evidence tier validation (Tier A-D)
- **voice-consistency-enforcer** - Intellectual honesty standards

{{#if PROJECT_SKILLS}}
### Project-Specific Skills
{{PROJECT_SKILLS}}
{{/if}}

## Git Workflow

Commit messages follow conventional format:
- `feat:` New features
- `fix:` Bug fixes
- `docs:` Documentation changes
- `refactor:` Code refactoring
- `test:` Test additions/changes
- `chore:` Maintenance tasks

{{#if EMOJI_COMMITS}}
Emoji prefixes:
- `✅` Milestone completions
- `📊` Research and analysis
- `🔧` Fixes and corrections
- `📚` Documentation improvements
- `📋` Session archives and updates
{{/if}}

{{#if SENSITIVE_DATA}}
## Sensitive Data

{{SENSITIVE_DATA}}
{{/if}}

---
*Generated by Claude Excellence Kit v1.0.0*
*Template: {{PRESET_TYPE}}*