# CLAUDE.md — Project Configuration

> Auto-generated by `npx @jamie-tam/forge init`. Run `/setup` to detect your stack and fill the project profile, then customize as needed.

@AGENTS.md

## Project Profile

```yaml
project:
  name: "{detected name}"
  mode: "{production | prototype | greenfield}"   # authoritative input to skill-selection mode detection; set by /setup Step 2.5
  aiwiki_enabled: true   # set by /setup Step 4; false means downstream skills surface upgrade hints instead of writing typed pages
  stack: "{detected stack}"
  database: "{detected database}"
  test_runner: "{detected test_runner}"
  package_manager: "{detected package_manager}"
```

## First Prompts

New to this project? Describe your goal in plain English — forge auto-routes via skills, OR invoke a command directly:

- `/discover` — one-screen orientation: what's installed, what's in flight, what to run next
- `/setup` — detect your stack and install matching language rules (run this first)
- `/feature <name>` — develop a feature end-to-end with quality gates
- `/bugfix <name>` — systematic debugging with root-cause analysis
- `/refactor <name>` — restructure code without new functionality
- `/note <text>` — capture an ad-hoc research note or brainstorm to `aiwiki/raw/`
- `/parallel <list>` — parallel agents for a punch list of ad-hoc tasks
- `/validate` — check skill/rule/command consistency

Operational state lives in `.forge/state/`; project knowledge in `aiwiki/`.
Claude Code's auto-memory (v2.1.59+) lives in `~/.claude/projects/<project>/memory/` — separate from `.forge/state/notepad.md`.

<!-- FORGE:START — do not edit between markers; updated by forge -->

## Development Workflow

This project uses **forge** as its development workflow. Every session should follow it: route via skills, use the `/feature`, `/bugfix`, `/refactor` etc. commands, and keep work artifacts in `.forge/`.

When the **aiwiki knowledge layer** is enabled (`project.aiwiki_enabled: true`), durable findings accumulate in **`aiwiki/`** — typed pages (`decisions/`, `gotchas/`, `conventions/`, `architecture/`, `oracles/`, `sessions/`) read by subagents during their work, plus `raw/` for free-form research and brainstorm capture (use `/note <text>`). The `wiki-lint` hook validates every `aiwiki/**` write against its schema, and `support-dream` consolidates raw → typed at phase-close and PreCompact (~85% context). When `aiwiki_enabled: false`, downstream skills (`support-gotcha`, `harden`, `iterate-prototype` capture, `/note`, `/wrap`) surface an upgrade hint instead of writing. Operational state (manifests, telemetry) stays separate in **`.forge/`** regardless.

System structure — skills (prefix-grouped), commands, `.forge/` layout, `aiwiki/` integration, context recovery — lives in **`.claude/rules/common/forge-system.md`** (always-on rule, auto-loaded every session).

<!-- FORGE:END -->

## Project-Specific Notes

<!-- Add project-specific context below: key decisions, architecture notes, known issues -->