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…
Analyze real shipped UI/UX references without copying visuals, then produce a structural reference extraction brief for Stark.
> /plugin marketplace add f0d010c/stark > /plugin install stark@stark
How it fires
How this command gets triggered: by you, by Claude, or both.
/stark-referenceContext preview
What this command does when you run it.
Analyze real shipped UI/UX references without copying visuals, then produce a structural reference extraction brief for Stark.
description: Analyze real shipped UI/UX references without copying visuals, then produce a structural reference extraction brief for Stark. argument-hint: "<product, flow, screenshot, URL, or design problem>"
Legacy Claude Code command. In Codex, ask:
> Use stark reference analysis for this flow before designing.
Read:
Inspect 3-5 shipped references when available. Use official docs, live public pages, first-party screenshots, or approved reference libraries. If using Mobbin/Figma/reference screenshots, extract structure only.
Output:
Reference extraction brief - Pattern chosen: ... - Why it fits this user's job: ... - Structural decisions to borrow: ... - Decisions to reject: ... - State/responsive requirements: ... - Asset/source constraints: ...
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."