Taste-Skill selector

When the user asks /taste-skill list, show the six installed Taste-Skill options with a short purpose, whether the agent may select it automatically, and one prompt example. Do not implement or modify a project just to display the list.

Skills are selected automatically when the task matches their descriptions, but automatic selection is not guaranteed and only relevant skills should be loaded. For a specific visual direction, explicitly name the skill with /skill-name. The examples below are prompt templates; the selected skill generates project code when used on a project.

Prompt examples

Use /design-taste-frontend to build this landing page: [brief]
Use /image-to-code to create and analyze visual references before implementing: [brief]
Use /redesign-existing-projects to audit and improve this existing UI without changing its behavior.
Use /high-end-visual-design for a premium visual direction for: [brief]
Use /minimalist-ui for a restrained editorial interface for: [brief]
Use /stitch-design-taste to create a Google Stitch DESIGN.md for: [brief]

If the user asks for the list only, return the index and examples without choosing a skill or starting implementation. Explain that 9router routes model requests; the agent client must load these local skills and include their instructions in the request. If the client does not support Agent Skills, the user must provide the relevant instructions in the prompt.