code

# Code

## Purpose

Discover, validate, and guide code style. Ensures consistent code patterns across the project by learning from existing configurations and code.

## Quick Reference

- **Setup**: `/code configure` (run once during framework setup)
- **Usage**: `/code guide`, `/code check`
- **Update**: `/code learn <path>` (analyze specific path)
- **Config**: `.claude/skills/code.yaml`

## Commands

| Command | Purpose | When to Use |
|---------|---------|-------------|
| `/code configure` | Analyze project for code style | Framework setup / wizard |
| `/code learn <path>` | Analyze specific path, update config | New module/patterns |
| `/code check [path]` | Validate code follows style | Before commit |
| `/code guide [context]` | Get style guidance | When writing code |

---

## /code configure

**When**: Framework setup wizard (one-time)

**What it does**:
1. Scans project for linter/formatter configs
2. Analyzes code patterns
3. Proposes style configuration to user
4. Saves to `.claude/skills/code.yaml`

### Discovery Process

```
1. DETECT LANGUAGE & TOOLS
   ├─ TypeScript: eslint, prettier, biome, tsconfig
   ├─ Python: ruff, black, flake8, isort, mypy, pyproject.toml
   ├─ Go: golangci-lint, gofmt, goimports
   ├─ Rust: clippy, rustfmt, Cargo.toml
   ├─ Java: checkstyle, pmd, google-java-format
   └─ Generic: .editorconfig

2. READ CONFIG FILES
   ├─ Extract rules from linter configs
   ├─ Extract formatting rules
   └─ Identify custom rules

3. ANALYZE CODE PATTERNS (sample 20-30 files)
   ├─ Naming conventions (functions, variables, classes, constants)
   ├─ Import organization (grouping, ordering)
   ├─ Formatting (indent, quotes, semicolons, line length)
   └─ Code structure patterns

4. PROPOSE TO USER
   └─ Show discovered style, wait for approval
```

### Proposal Format

```yaml
# Proposed Code Style Configuration
# Review and approve to save to .claude/skills/code.yaml

language: typescript
confidence: high

tools:
  linter: eslint
  formatter: p