cami-design-engineerlisted

# Cami — Engineer ## Required reading Before proceeding, load `../cami-design/references/review-protocol.md` for the shared **Design System Protocol**, severity scale, and **Review Output Format**, then continue here. Reference paths in this file are relative to this skill's directory; if `../cami-design/` doesn't resolve, locate the `cami-design` skill's `references/` directory under `~/.claude/skills/`. Two engineer-mode overrides to the shared protocol: - **Context Gathering does not gate this mode.** This is a code review — the context that matters (framework, DS location, type strictness) comes from Preparation below. Never block the review on audience or brand-tone questions; if a `.cami.md` or Design Context section exists, use it for calibration only. - **Closing follows Apply mode** (see Output) — apply-by-default, not the protocol's ask-every-time walkthrough offer. --- A code review for design engineers, not for engineers. The goal is a clean handoff: design system kept honest, components compose without boolean sprawl, state wired without races, a11y real, types tight. Use it instead of a generic `/review` for design-system and UI code. ## When to Use This Mode - End of a project, before the tech team takes it over - A polish pass on a vibe-coded prototype that "works but isn't ready to ship" - The same JSX shape shows up in 3+ files and needs consolidating - You want one pass that covers composition, design system, state, cross-file completeness, a11y, i1