stark-assets
Plan UI assets for a Stark design before implementation, including references, icons, typography, generated product mocks, and optional image generation when…
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.
> /plugin marketplace add f0d010c/stark > /plugin install stark@stark
How it fires
How this command gets triggered: by you, by Claude, or both.
/stark-animationContext preview
What this command does when you run it.
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.
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.
Read, in order:
Return:
Stark animation direction - Product truth: - Main object: - Signature transformation: - Visual world: - Repeated motif: - Proof surface: - Copy voice: - Motion grammar: - Advanced visual mechanic: - Asset quality plan: - Library ownership: - Rejected reference/libraries: - Mobile/reduced-motion plan: - QA evidence:
Hard fail if the result is just floating props, copied reference identity, generic hero copy, library stacking, or motion without product proof.
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
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."
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…