Help us improve
Share bugs, ideas, or general feedback.
From stark
Routes ambiguous UI/UX requests to the correct platform or UX skill. Activates when a build, design, or audit request does not clearly name one platform.
npx claudepluginhub f0d010c/stark --plugin starkHow this skill is triggered — by the user, by Claude, or both
Slash command
/stark:design-routerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is the entry point when a UI/UX request is ambiguous. Goal: pick the right UX and platform skill, do not over-eagerly route to web.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Guides systematic root-cause debugging when tests fail, builds break, or unexpected errors occur. Provides a structured triage checklist to preserve evidence, localize, and fix issues instead of guessing.
Share bugs, ideas, or general feedback.
This skill is the entry point when a UI/UX request is ambiguous. Goal: pick the right UX and platform skill, do not over-eagerly route to web.
Route to ux-design before platform visuals when the request includes:
If the request is both UX and platform-specific, read ux-design first, then the matching platform skill.
Scan for explicit signals (in priority order):
| Signal in request | Route to |
|---|---|
| "onboarding", "checkout", "signup", "form flow", "empty state", "loading state", "error state", "admin workflow", "CRM", "internal tool", "SaaS dashboard", "user journey" | ux-design first, then platform skill |
| "translate this UI", "translate this screen", "translate this design", "port this UI", "convert this screen", "from iOS to Windows", "from Apple to Android" | cross-platform-design first, then the target platform skill |
| "design tokens", "export tokens", "DTCG", "token JSON", "ColorScheme", "Typography tokens", "Tailwind tokens", "SwiftUI tokens", "Compose tokens" | design-tokens |
.tsx .jsx .html .svelte .vue, "Tailwind", "Next.js", "Astro", "shadcn", "landing page", "marketing site", "dashboard in React" | web-design |
.xaml .cs (with WinUI/UWP/WPF), "Windows app", "Fluent", "Mica", "WinUI", "Win11", "Microsoft Store app", "PowerToys-style" | windows-design |
.swift .swiftui, "SwiftUI", "iOS app", "iPadOS", "macOS", "Liquid Glass", "HIG", "SF Symbols", "App Store", "Tahoe" | apple-design |
.kt .kts, "Compose", "Jetpack Compose", "Material 3", "Material You", "Pixel app", "Android app" | android-design |
| "Tauri", "Electron", "Flutter", "React Native", "Expo", "Compose Multiplatform", "CMP", "Uno Platform", "Avalonia", "MAUI" | cross-platform-design |
Ask one question, no more:
"Which platform is this for? (1) Web - React/Tailwind/Astro (2) Windows - WinUI 3 / WPF (3) iOS / macOS - SwiftUI (4) Android - Jetpack Compose (5) Cross-platform - Tauri 2, Compose Multiplatform, React Native, Flutter. If this is mainly UX, describe the user flow and I'll start there."
Do not assume web. Web defaults are how the official frontend-design skill produces native-looking-wrong code.
If the user wants the same product on multiple platforms (e.g. "iOS + Android + web"):
cross-platform-design or successive single-platform skills, respecting each idiom, not pixel-cloning.Same product ≠ same UI. A Settings screen on iOS uses grouped Form, on Android uses LargeTopAppBar + LazyColumn, on Windows uses NavigationView + SettingsCard. Translate idiom, not pixels.
Once routed, the UX or platform SKILL.md takes over. State what you picked and why in one sentence, then proceed.
If UX ran first, carry its UX decision brief into the platform skill and preserve the job, state coverage, action hierarchy, and recovery path.
For any build/redesign request, also carry a UI decision brief from ../../references/ui-patterns/ui-decision-brief.md into the platform skill. This keeps visual hierarchy, density, component grammar, and motion budget explicit.
When uncertain, ask. One clarifying question is cheaper than 800 lines of wrong-platform code.