frontend-skill-router

Routes frontend build, redesign, and audit requests to the appropriate installed UI skills.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/Yjj0333/skills-manager-backup --skill frontend-skill-router-yjj0333
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-skill-router
Source: https://github.com/Yjj0333/skills-manager-backup/tree/main/frontend-skill-router
Command: npx skills add https://github.com/Yjj0333/skills-manager-backup --skill frontend-skill-router-yjj0333

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When many frontend and design skills are installed, choosing the right one for a given UI task is ambiguous and error-prone. This Skill classifies the user's request and selects the correct primary skill, supporting skills, and validation gate before any UI work begins. ## Core Features & Use Cases - Task Classification: Distinguishes production app UI, landing pages, redesigns, screenshot-to-code, mobile concept images, brand identity, and GSAP motion work, with bilingual English/Chinese trigger support. - Skill Stack Selection: Picks one primary skill (e.g., impeccable, design-taste-frontend, image-to-code) plus supporting skills and a validation gate such as baseline-ui. - Boundary Management: Defers frontend skeleton planning to ai-frontend-scaffolder and respects the five-stage project toolkit specs. - Use Case: A user asks to "把这个后台页面做得更专业". The router classifies it as product UI polish, announces the stack primary=impeccable with validation=baseline-ui, then proceeds with that workflow. ## Quick Start Use the frontend-skill-router to decide which installed frontend skills to load for building, redesigning, animating, or auditing this UI.

Frequently Asked Questions about frontend-skill-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right frontend skill for a UI task?▼

Classify the artifact first: product UI and dashboards route to impeccable, landing pages and portfolios to design-taste-frontend, existing-site upgrades to redesign-existing-projects, and screenshot matching to image-to-code. Add baseline-ui as a late validation gate for Tailwind and component quality.

What is the difference between impeccable and design-taste-frontend?▼

impeccable handles production product UI such as dashboards, admin tools, forms, and UX polish. design-taste-frontend handles landing pages, marketing sites, portfolios, and editorial visual redesigns. Choose by surface type, not by preference.

Does this router handle Chinese frontend requests?▼

Yes, Chinese requests are first-class. Phrases like 落地页, 仪表盘, 截图转代码, and 重做官网 are mapped to the same routing rules as their English equivalents, based on the artifact the user wants.

When should I use ai-frontend-scaffolder instead of this router?▼

Use ai-frontend-scaffolder when the task is frontend skeleton planning: directory structure, framework choice, design tokens, and module boundaries. Use this router only when the user wants concrete UI surfaces built, redesigned, animated, or audited.

Can I combine multiple frontend skills in one task?▼

Yes, but keep the stack small: one primary skill, one or two supporting skills, and one validation gate. For example, a GSAP campaign page in Svelte uses gpt-taste as primary with gsap-frameworks for lifecycle-safe cleanup.

What happens if a recommended skill is not installed?▼

Confirm skill availability before relying on it. If a named support skill is missing, use the closest available fallback and briefly state the substitution before continuing the work.