stark

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.

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.

Analyze real shipped UI/UX references without copying visuals, then produce a structural reference extraction brief for Stark.

Translate a UI from one platform's idiom to another's — same product, different idiom — respecting target platform's HIG/Material/Fluent rather than pixel-cloning. e.g., "translate this iOS Settings screen to Windows".

Generate or improve UI/UX for the specified platform - ux, web, windows, apple, android, or cross-platform. Routes to matching skill which then asks the user which product flow, track, or aesthetic direction before generating code.

Use when the user wants one codebase or one product design across web, iOS, Android, Windows, and Mac, asks for the same app on all platforms, asks to translate/port a UI between platforms, or names Compose Multiplatform, Tauri 2, Electron, React Native, Flutter, .NET MAUI, Avalonia, or Uno Platform. Builds cross-platform UI by preserving UX decisions, originality seed, desktop archetype, state coverage, tokens, and product job while translating each surface into the host platform's native idiom rather than pixel-cloning. SKIP when only one platform is targeted and no translation/cross-platform tradeoff is involved.

Use when the user asks to build, design, mock up, scaffold, audit, translate, or improve any interface, flow, screen, page, component, app, UX, onboarding, checkout, dashboard workflow, product flow, design system, asset plan, motion plan, or non-generic UI and the target platform or flow is ambiguous. Routes to ux-design, web, Windows, Apple, Android, cross-platform, design-token, originality, asset/reference, and platform skills. SKIP when the request explicitly names one platform and no UX flow work is implied.

Use when the user asks for design tokens, DTCG tokens, theme systems, color/typography/spacing/radius/elevation/motion tokens, translating tokens, exporting tokens, making a Compose color scheme from a palette, auditing tokens, or sharing a single token source across web and native. Generates, audits, and translates W3C DTCG tokens to Tailwind v4 @theme, CSS variables, Compose Material3 ColorScheme/Typography, SwiftUI Color/Font extensions, and WinUI ResourceDictionary while preserving semantic naming and platform constraints. SKIP when no token/theme-system work is involved.

Use when the user asks for UX, product flow, user journey, wireframes, usability, conversion, onboarding, checkout, signup, navigation, forms, state design, dashboard workflows, command palettes, settings, permissions, long-running task progress, admin/internal tools, activation, retention, or making an app easier to use over time. Designs and audits user experience flows, information architecture, content hierarchy, forms, onboarding, dashboards, settings, empty/loading/error/permission/success states, recovery paths, and repeated-use product ergonomics before visual polish. Pair with platform UI skills after the UX flow is clear.

Use for websites, web apps, landing pages, dashboards, SaaS products, docs, checkout, agent/tool runs, React/Next/Vite/Astro/Tailwind frontends, web UI reference planning, originality, typography, assets, animation, motion, scrolling, GSAP, Motion, Lenis, View Transitions, command palettes, split panes, inspectors, and frontend interaction decisions. Builds web surfaces with surface type, UX handoff, visual direction, hierarchy, layout sketch, copy, assets, responsive containment, motion/library choices, and anti-slop discipline. ALWAYS choose surface type and ask which aesthetic direction first. SKIP when the target is a native desktop/mobile app.