/stark-qa
Use this command to require proof before calling a UI "good."
$ npx -y skills add f0d010c/stark --agent claude-codeShips with stark. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/stark-qa
Context preview
What this command does when you run it.
Use this command to require proof before calling a UI "good."
Design direction for AI coding agents—grounded in product behavior, platform idiom, and rendered evidence. Stark routes UI work across web, Windows, Apple, Android, cross-platform, UX, and design tokens.
Repo: f0d010c/stark
Other commands on stark.
- /stark-animation
Use this command when the user asks for high-end animation direction, Luma-level landing pages, cinematic product reveals, or when an animated design feels messy, copied, cheap, or like random elements were pasted around a hero.
Open command - /stark-assets
Plan UI assets for a Stark design before implementation, including references, icons, typography, generated product mocks, and optional image generation when the agent supports it.
Open command - /stark-audit
Audit existing UI/UX code, flows, or screenshots against UX heuristics plus the matching platform's anti-slop ban list and idiomatic checklist. Reports specific violations with line numbers and proposed fixes.
Open command - /stark-director
Use this command when the user asks Stark to go all out, raise design quality broadly, use libraries well, make a UI feel actually designed, or coordinate research, typography, motion, usability, implementation, and QA in one pass.
Open command - /stark-dogfood
Use this command when testing whether Stark actually generates better designs, refreshing proof screenshots, creating showcase examples, or turning generated-output failures into guidance changes.
Open command - /stark-quality-gate
Use this command when a web UI should be maintained, released, compared across runs, or used as public proof. It turns visual QA into a repeatable local/CI gate instead of a one-off screenshot check.
Open command