stark
Gives AI coding agents design guidance for building UI, routing work across web, Apple, Android, Windows, cross-platform, and design token tasks. Covers platform idioms and design token systems.

Gives AI coding agents design guidance for building UI, routing work across web, Apple, Android, Windows, cross-platform, and design token tasks. Covers platform idioms and design token systems.
Use when the user asks for an Android app, Compose UI, Material 3, Material You, Material 3 Expressive, Pixel-style app,…
Use when the user asks for SwiftUI, UIKit, AppKit, iOS, iPadOS, macOS, watchOS, visionOS, Liquid Glass, HIG, SF Symbols, App…
Use when the user wants one codebase or one product design across web, iOS, Android, Windows, and Mac, asks for the same app on…
Use when the user asks to build, design, mock up, scaffold, audit, translate, or improve any interface, flow, screen, page,…
Use when the user asks for design tokens, DTCG tokens, theme systems, color/typography/spacing/radius/elevation/motion tokens,…
Use when the user asks for UX, product flow, user journey, wireframes, usability, conversion, onboarding, checkout, signup,…
Use for web interfaces, landing pages, product sites, dashboards, React, Next.js, Astro, Tailwind, frontend audits, responsive…
Use when the user asks for a Windows app, Win11/Win12 UI, XAML, Fluent design, WinUI, WPF, PowerToys-style tool, Microsoft Store…
Generate or improve UI/UX for the specified platform - ux, web, windows, apple, android, or cross-platform. Routes to matching…
Use this command when the user asks for high-end animation direction, Luma-level landing pages, cinematic product reveals, or…
Plan UI assets for a Stark design before implementation, including references, icons, typography, generated product mocks, and…
Audit existing UI/UX code, flows, or screenshots against UX heuristics plus the matching platform's anti-slop ban list and…
Use this command when the user asks Stark to go all out, raise design quality broadly, use libraries well, make a UI feel…
Use this command when testing whether Stark actually generates better designs, refreshing proof screenshots, creating showcase…
Use this command to require proof before calling a UI "good."
Score a UI, design brief, or generated implementation against Stark's design quality metrics.
Use this command when a web UI should be maintained, released, compared across runs, or used as public proof. It turns visual QA…
Analyze real shipped UI/UX references without copying visuals, then produce a structural reference extraction brief for Stark.
Create a reference board before designing.
Use this command when the user wants another attempt at a design after critique, or asks Stark to generate better/original…
Is this you? Claim your profilePut a plugin at the top of Plugins, from $9