# Claude Code — FA 2.0 Design System

Follow all rules in `AGENTS.md`. This file contains Claude-specific behaviour only.

## Session startup (automatic)

At the start of every session, automatically:
1. Read `docs/memory/session-log.md`, `decisions-log.md`, `component-registry.md`
2. Check `docs/reference/retroactive-review-plan.md` for pending review tiers
3. If reviews remain, run the next step (~30-60 min) before the user's main request
4. Report findings, then shift to whatever the user wants to work on

This is "morning housekeeping" — the user has approved this and expects it.

## Memory system

Before starting any work, read:
- `docs/memory/decisions-log.md` — all design decisions with rationale
- `docs/memory/component-registry.md` — status of every component
- `docs/memory/token-registry.md` — all tokens with values and usage notes
- `docs/memory/session-log.md` — recent sessions; older in `docs/memory/archive/`

After completing work, update the relevant memory files and `session-log.md`.

## MCP servers

- **Figma remote MCP** — read FA 1.0 designs, extract design context
- **Storybook MCP** — query component library for available components and props

Setup instructions: `docs/reference/mcp-setup.md`

## Commit co-author

Append to every commit message:
```
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
```

## Cross-tool workflow

This project uses both Claude Code and Google Antigravity.
See `docs/reference/cross-tool-workflow.md` for task routing and coordination.

Claude Code owns: component building, token creation, code quality, memory updates, git.
Antigravity owns: visual QA, browser-based verification, page-level review screenshots.