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…
Score a UI, design brief, or generated implementation against Stark's design quality metrics.
> /plugin marketplace add f0d010c/stark > /plugin install stark@stark
How it fires
How this command gets triggered: by you, by Claude, or both.
/stark-qualityContext preview
What this command does when you run it.
Score a UI, design brief, or generated implementation against Stark's design quality metrics.
Score a UI, design brief, or generated implementation against Stark's design quality metrics.
Use `references/ui-patterns/design-quality-metrics.md`, `references/ui-patterns/quality-calibration-ladder.md`, `references/ui-patterns/qa-evidence-contract.md`, `references/ui-patterns/rendered-quality-gate.md` when rendered or screenshot evidence exists, `references/ui-patterns/visual-repair-playbook.md`, and `references/ui-patterns/design-acceptance-gate.md`.
Output:
Design quality report - Surface/user mode: - Scores: product specificity _, state coverage _, hierarchy _, originality _, typography _, motion _, assets _, accessibility _, responsive _, implementation _ - Hard fails: - Evidence: - Rendered quality: - First repair: - Fix applied after critique: - Acceptance gate: - Remaining risk:
Rules:
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
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…
Plan UI assets for a Stark design before implementation, including references, icons, typography, generated product mocks, and optional image generation when…
Audit existing UI/UX code, flows, or screenshots against UX heuristics plus the matching platform's anti-slop ban list and idiomatic checklist. Reports…
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…
Use this command when testing whether Stark actually generates better designs, refreshing proof screenshots, creating showcase examples, or turning…
Use this command to require proof before calling a UI "good."