Lucas WintherandClaude Opus 5
fe9f6c6dec
TODO.md carries the remaining work with the reasoning already settled, so the next agent does not re-derive decisions: tasks 3-6 of the versioned-rules plan, the designed-but-unbuilt baked FX rates, the queued visual redesign, the small residuals, and an explicit list of what only a human with a browser can check. ARCHITECTURE.md explains the layer rules, the single-implementation fold, the mutation pipeline's three deliberate properties, and the gotchas that each cost a real bug — reading a deferred event.target.value, an unset BUN_PUBLIC_* var reaching the browser, and overriding shadcn's --accent. CLAUDE.md gains those gotchas, the dated-rule model that replaced standingRule, the validation this project deliberately omits, and an explicit statement that visual and offline behaviour cannot be verified in the agent environment. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1.0 KiB
1.0 KiB
Agent guide
This repository's agent instructions live in CLAUDE.md — read it first.
It carries the project invariants, the gotchas that cost real bugs, and the
validation this codebase deliberately does not perform.
Then, depending on what you are doing:
- Changing anything structural →
ARCHITECTURE.md(layers, data flow, and why the non-obvious choices are what they are). - Picking up queued work →
TODO.md(ordered, each item carrying the reasoning already settled). - Making a product decision →
PRODUCT.md(who this is for, what must never break, and what must not be invented). - Wondering why something is the way it is →
docs/superpowers/specs/records the decisions and the alternatives that were rejected.
Two rules worth knowing before your first edit:
- Bun only.
bun test,bun run,bunx. Never npm, jest, vitest or vite. - There is no browser here. Anything visual, offline, or focus-related cannot be verified in this environment. Say so rather than claiming it works.