Skill Claude CodeCodex
Build or update UI screens, dashboards, forms, modals, and tables. Use when the subtask is primarily a frontend implementation — page layout, component composition, responsive design, interaction polish, or UI state wiring to existing APIs.
Skill Claude CodeCodex
Implement features that span backend and frontend together — API endpoints with their UI, auth flows, CRUD modules, validation. Use when the subtask requires both sides of the system to ship a working feature.
Skill Claude CodeCodex
Implement code changes from an existing specs/ /TECH.md, one Implementation Plan step per commit, and update the spec in the same PR whenever reality diverges. Use after write-tech-spec, or when the user points at an existing TECH.md and says "implement this".
Skill Claude CodeCodex
Review recent code changes for reuse, quality, and efficiency. Use when the user asks for a code-quality pass, requests "/simplify", or asks to audit recent changes for duplication or technical debt.
Skill Claude CodeCodex
Orchestrate the full spec-then-build workflow for a non-trivial task — write a tech spec, get review, then implement step-by-step keeping spec and code in sync. Use when the user asks to "spec-drive this", "do this properly with a spec", or wants the full Warp-style discipline.
Skill Claude CodeCodex
Polish existing UI to production quality — spacing, typography, color consistency, hover/focus states, responsive breakpoints. Use when the subtask is about visual polish, design-system enforcement, or beautifying an existing screen rather than building new features.
Skill Claude CodeCodex
Verify recent code changes work end-to-end by building, running tests, and exercising affected features. Use when the user asks to verify changes, requests "/verify", or wants confirmation a feature actually works.
Skill Claude CodeCodex
Draft a technical specification under specs/ /TECH.md before writing code. Use when the user asks for a "spec", "tech spec", or "implementation plan" — or when a task is large enough that getting the approach reviewed before coding is cheaper than writing the code twice.