skit-autopilotUse when the user points to a markdown checklist plan and wants hands-off execution. Not for coordinating several dependent workstreams or for unattended ticket runs.
skit-broRestate your last message in plain words, one human to another.
skit-design-grillUse to settle visual and behavioural interface decisions by a round-based interview, recording agreed design decisions and excluding implementation architecture; also for 'grill me on the design'. For a plan, decision or idea that is not an interface, use skit-grilling.
skit-grillingUse to stress-test a plan, decision, or idea by interviewing the user in rounds until nothing is left assumed, or when the user says 'grill me'. Asks through the harness's question tool when it has one. For visual or behavioural interface decisions, or 'grill me on the design', use skit-design-grill
skit-handoffUse when ending or pausing a session to write a structured handoff of decisions, progress, changes, and next steps for the next session. Not for issue-tracker upkeep or personal task capture.
skit-interfaceUse to review interactive controls, forms, lists, dashboards, settings, documentation, or non-happy-path screen states: structure, labels, focus, hit areas, field states. It owns UI review. Not for building a UI change (skit-vibe), marketing or brand pages, type scale (skit-type), or visual styling
skit-maintainability-reviewUse to review AI-generated frontend code for human maintainability: duplication, abstractions, naming, structure, silent failures, cross-session drift. Not for reviewing a plan before building (skit-self-review) or for diagnosing a defect.
skit-polishA finishing pass, run by name, for a page whose direction is right but still feels unfinished: hover shifts, press feedback, punctuation, and the small details other skills own.
skit-self-reviewUse immediately after proposing a non-trivial engineering plan or when a self-review is requested; critique your own plan against a fixed checklist and revise it to address every point. Not for trivial single-step plans, code diffs, or frontend code quality (skit-maintainability-review).
skit-strategyUse for product and UX strategy: business models, positioning, journey maps, teardowns, stakeholder narratives. Not for visual direction (skit-visual-design), interface states (skit-interface) or screen design decisions (skit-design-grill).
skit-typeUse for typeface and font choice, pairing, OpenType features, font loading, and language or script coverage across screen, print, or brand work. Not for general UI styling (skit-visual-design), interaction structure (skit-interface), or copy (skit-ux-copy).
skit-ux-copyUse for writing, editing, or auditing interface microcopy: controls, forms, errors, onboarding, empty states, notifications, voice, tone. Not for long-form prose, essays, or visual and type decisions.
skit-vibeUse to build any interface change (tweak, new screen, risky UI/data change): it owns building UI, choosing process depth and running build-review. Not for non-UI work, or for reviewing or critiquing an existing UI (skit-interface); visual direction and type come from skit-visual-design and skit-type
skit-visual-designUse for visual direction in a product UI: colour, hierarchy, responsive layout, CSS tokens, `@theme`, and OKLCH, while first classifying the surface intent. Not for a token or colour tweak inside an existing system, typography-primary work (skit-type), behaviour and states or UI review (skit-interfa