# CLAUDE.md

@AGENTS.md

## Always-loaded project rules

Only the two rule files every task needs are loaded here; the rest are read on
demand (below) to keep each session small.

@.kiro/steering/business-logic.md
@.kiro/steering/api-surfaces.md

## Load on demand (read the file before you start that kind of work)

| Before you… | Read |
|-------------|------|
| write or edit any PHP file | `.kiro/steering/code-standards.md`, `.kiro/steering/architecture.md` |
| touch an admin controller, service, request or resource | + `.kiro/steering/crud-conventions.md`, `.kiro/steering/base-project-style.md` |
| add or change a Form Request or a route | `.kiro/steering/postman-collection.md` |
| write or edit anything in `docs/` | `.kiro/steering/feature-documentation.md` |

Read each file once per session; don't re-read it for every edit.

## Claude Code notes

- **Start a feature with its brief, not with whole files:**
  `php artisan docs:brief {surface} {feature}` (or the `project-docs` MCP tool
  `get-integration-brief`) prints the registry row, the BRD section, the decisions
  and the feature doc's Quick reference in one go. Open more only if it is not enough.
- Never read `docs/PROJECT_BRAIN.md`, `docs/DECISIONS.md`, `docs/CHANGELOG.md` or a
  BRD file end to end: `grep -n` for the ID, then read that slice (budget table in
  `docs/PROJECT_BRAIN.md` §1).
- No BRD yet: when files appear in `docs/brd/` or `docs/app_screens/`, run the
  `project-init` skill (steps 2 and 3) before building any BRD feature.
- When the user asks "what changed in X?", answer from the feature doc's
  *Version history* and `docs/CHANGELOG.md`, not from git history alone.
- Do not edit `docs/brd/*` or `docs/app_screens/*` images — they are input. Record
  interpretations in `docs/DECISIONS.md`.
