claude-setup

# Claude Setup Skill

Patterns and templates for creating optimized CLAUDE.md files that integrate project.md and brand.md context.

## Workflow Integration

```
project.md (what) → brand.md (identity) → CLAUDE.md (how)
```

CLAUDE.md should:
- Reference project.md for project overview
- Reference brand.md for design guidelines
- Focus on TECHNICAL configuration for Claude

## Core Principles

### 1. Context-Aware Generation
- Read project.md for project identity and goals
- Read brand.md for design and voice guidelines
- Focus CLAUDE.md on technical commands and patterns

### 2. Signal Over Noise
- Only document non-obvious information
- Avoid restating what's clear from code
- Focus on gotchas, patterns, and decisions

### 3. Token Budget Awareness
| Project Size | Target Tokens | Max Lines |
|--------------|---------------|-----------|
| Small (<10k LOC) | 500-1000 | 50-100 |
| Medium (10-50k LOC) | 1000-2000 | 100-200 |
| Large (>50k LOC) | 2000-4000 | 200-300 |

### 4. Structured Sections
Use XML-style tags for parseability:
- `<ARCHITECTURE>` - Technical architecture decisions
- `<CONVENTIONS>` - Project-specific code patterns
- `<TOOLS>` - MCP servers and preferences
- `<TESTING>` - Test framework and patterns
- `<COMMANDS>` - Quick reference table
- `<BRAND>` - Quick reference from brand.md
- `<GOTCHAS>` - Proven solutions to problems

## CLAUDE.md Structure

```markdown
# [Project Name]

[One-line description - from project.md or detected]

## Quick Reference

| Command | Description |
|---------|-------------|
| `[cmd]` | [purpose]   |

For project overview, see [project.md](project.md).
For brand guidelines, see [brand.md](brand.md).

<ARCHITECTURE>
## Architecture

[Technical architecture - patterns, layers, data flow]
[Reference project.md for project goals and features]
</ARCHITECTURE>

<CONVENTIONS>
## Conventions

### Naming
- [File naming pattern]
- [Class/function naming]

### Code Organization
- [Feature vs layer structure]
- [Import ordering]
</C