dev-team

Use when writing a new module under `crew/`, adding a CLI verb or flag, touching a `.ts` extension, declaring a closed enum, choosing an import boundary, or emitting a usage or cost record. Use when a backend change must stay dependency-light, reject unknown command input, survive both TypeScript loaders, or distinguish an unmeasured value from a measured zero. Use when reviewing tests for import firewalls, frozen data contracts, flag windows, or complete-or-absent accounting.

Load when dispatching a crew lane: choosing a variant, preparing its worktree, compiling and verifying fences, selecting tier, or writing boot and run flags that must execute against the current CLI.

Load when recovering, proving, closing, or diagnosing a crew lane: preserve its state, interpret liveness and escalation stages, run mutation proof, publish the PR, and tear down only after closeout.

Use when creating or removing a Git worktree, preparing a lane branch, invoking `gh`, publishing from a checkout, investigating stray processes, reclaiming an orphan, or operating the crew daemon. Use when a linked checkout might share Git state, when a command needs an absolute body file, when a pull request must remain open, or when liveness is uncertain. Use when choosing dry-run versus reclaim, reading daemon paths and verbs, or recording an operational rule whose checkout has no local exhibit.

Constrains Svelte work to this repository's measured visualizer conventions while routing every Svelte API question to the svelte MCP. Load it before creating or editing a visualizer component, changing the app shell, adding a plain-module shaper, or deciding how a source-level test should pin Svelte code. It covers the component prop and rune idioms, module boundaries, theme ownership, and the fact that this checkout tests logic with node --test and components as source text.

Governs reviewing a change for correctness, contract drift, vacuity and scope, the typed findings shape, and divergence. Load it when reviewing a pull request or change and deciding findings, grades, or reviewer posture.

Writes and reviews tests for this repo against rules it has already paid for: proving a check can fail (vacuity), naming the mutation each check kills, building acceptance gates that are red at baseline and provably discriminating, pinning vendor stream formats with recorded captures instead of hand-built frames, declaring tripwires when a change moves code or changes a detector, and recording an unmeasured value as absent rather than zero. Use when writing a new test, reviewing whether an existing test pins anything, authoring an acceptance gate, deciding what a lane's tripwire tests are, debugging a test that passes when it should not, or judging whether a suite's green means anything.

Constrains new visualizer UI to the measured design boundary: theme-paired chrome, Tier-2 alias tokens, explicit status and identity colour routing, panel and spacing idioms, honest absence marks, and known contrast and enforcement limits. Load it before designing or reviewing a Svelte component, choosing a colour, adding a panel, or deciding how state, role, lane, and unmeasured values should appear. It records this checkout's evidence rather than inventing a generic design system.