Master router for the Taste Skill Pack. Reads the user brief, chooses the most suitable UI style, then delegates to the matching style skill plus the shared components library.
3e:T1f3f,
You are the entrypoint for this entire frontend taste system.
Use this file first. Do not jump straight into a style folder before making a style decision.
Your job is to:
If the user already names a style, use that style unless it directly conflicts with the brief. Treat an explicit style request as a strong override, not a weak hint.
If the user does not name a style, you must choose one yourself. Do not ask the user to pick from a long list unless the brief is genuinely split across very different directions.
Follow this sequence every time:
skill.md.components/style-recipes.md and use the matching section for that chosen style.components/ library only when they reinforce the chosen style.If the user explicitly asks for one of these styles, honor it directly:
brutalismcinematic-productdark-luxedashboardseditorial-premiumgallery-minimalminimalismmonochrome-modernpremium-bentoquiet-luxurysoftsoft-brutalismswiss-systemwarm-modernAlso honor obvious close phrasings such as:
brutalist -> brutalismcinematic product -> cinematic-productdark luxe -> dark-luxeeditorial premium -> editorial-premiumgallery minimal -> gallery-minimalmonochrome modern -> monochrome-modernpremium bento -> premium-bentoquiet luxury -> quiet-luxurysoft brutalism -> soft-brutalismswiss or swiss design -> swiss-systemwarm modern -> warm-modernWhen the style is explicitly named, do not ask the user to choose again. Route straight into that style and use the component recipes for it.
Use this routing logic:
minimalism
editorial-premium
dashboards
swiss-system
brutalism
cinematic-product
dark-luxe
gallery-minimal
monochrome-modern
premium-bento
quiet-luxury
soft
soft-brutalism
warm-modern
If the user is vague, decide by these signals:
editorial-premiumswiss-systemminimalismpremium-bentobrutalismdark-luxegallery-minimalsoftwarm-moderndashboardsDo not default to the same style every time. Make a real selection.
After choosing a style, you must use the shared support files:
components/style-recipes.mdcomponents/Use them like this:
style-recipes.md to find strong component patterns for that exact styleDo not treat the component library as optional inspiration when the recipes explicitly point to it. Do not skip opening those files just to move faster. Do not blindly paste flashy components into every design.
Only use components that fit the style's pacing, materiality, and density.
The final result must:
Never generate a generic fallback UI just because the prompt is broad.
If the brief is broad:
If the brief mixes two neighboring moods, choose the dominant style and borrow only light support from the component recipes. Do not mash multiple style skills together into a confused result unless the user explicitly asks for a hybrid.