菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when an AI agent needs to manage Built With Django blog posts through the site API, including creating, reading, listing, updating, or deleting posts. Covers the superuser-token-only CRUD endpoints under /api/v1/posts/, required headers, payload fields, status/type/level choices, tag behavior, safety checks, and troubleshooting for permission or validation errors.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Senior UI/UX Engineer for severe, industrial, poster-like, and tactical brutalist interfaces. Uses the full Taste Skill baseline but tunes the output for hard structure, mechanical hierarchy, and anti-softness.
Senior UI/UX Engineer for keynote-style product storytelling and scene-based launch pages. Uses the full Taste Skill baseline but tunes the output for product-as-protagonist composition, chapter flow, and premium motion.
Senior UI/UX Engineer for atmospheric dark luxury interfaces. Uses the full Taste Skill baseline but tunes the output for material-rich darkness, light control, and premium restraint without neon or gamer drift.
Senior UI/UX Engineer for polished operator dashboards, admin surfaces, control panels, and monitoring interfaces. Uses the full Taste Skill baseline but tunes the output for task-first hierarchy, actionable density, and calm operational clarity.
| name | design-taste-skill-pack |
| description | 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. |
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:
Default stack: React or Next.js. Unless the user explicitly requests another framework or stack, assume React/Next.js conventions by default.
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.