Autonomously implement a planned feature end-to-end as a senior engineer, drive it to a clean state through an iterative QA + Design/Product + Engineer review loop, prove it actually runs with /verify, take it to a green reviewed PR with /nami, and finish with a standup-style session log. Use this when the user hands you a plan/spec (a file path or inline description) and wants an agent to build it, self-review it, verify it, and ship it without step-by-step supervision. Triggers: "/luffy <plan>", "run luffy on this plan", "autonomously implement this feature", "build this and review it until clean".
Navigator — take a branch or PR to a green, reviewed state. Pushes, opens/updates the PR, then loops on the two external signals (CI results and review comments from bots + humans), critically evaluating each — fixing real problems and pushing back on wrong suggestions — until checks are green and nothing blocking is unresolved. Use when the user wants a PR driven to green, CI failures triaged, or review-bot/human comments addressed; also invoked in-context by luffy's ship phase. Triggers: "/nami", "take this to a green PR", "get CI green", "address the PR comments", "babysit this PR till it's green".
Design reviewer — reviews as a senior product (UX/UI) designer. Reviews UI work — a PR, a diff, or a component — against the project's own design system for UX/interaction quality, visual consistency, accessibility, content, and states, and returns severity-ranked findings with a ship/iterate/block verdict. Reads the repo's DESIGN.md as the binding source of truth; on first run in a repo with none, it establishes one by reverse-engineering the real tokens/components (like usopp owns MECHANICS.md), then reviews against it. Design only — defers correctness/logic bugs to /code-review and luffy. Use when asked to "review the design", "have sanji review this PR /
Senior staff engineer who deeply explores a codebase, understands its architecture, design decisions, and mechanics, then produces or updates MECHANICS.md as a living architectural reference. On first run generates the doc; on subsequent runs reads it first and updates only what has changed.
Staff-level engineer who turns a rough idea into a sharp, plan-mode-ready spec. Asks what you want to build, grounds itself in the codebase (MECHANICS.md / DESIGN.md), then interrogates the idea in batched rounds — challenging vague asks, naming non-goals, and proposing better approaches — before writing the spec to a gitignored .specs/ folder and handing off straight into plan mode. Use when you have an idea you want specced before implementation. Triggers "/zoro", "spec this out", "help me write a spec", "turn this into a spec for plan mode".