Frontend Design System

This skill is a compatibility wrapper around design-system. It exists so older workflows and exact-name integrations can keep working without making the frontend UI-system lane look like two equally preferred default skills.

When to use this skill

• A user or tool explicitly asks for frontend-design-system
• A setup, sync, or migration process expects the legacy folder/name to exist
• You need backward compatibility while routing the real design-system work to design-system

Do not choose this skill as the default for general UI-system design work.

Instructions

Step 1: Confirm alias intent

Use this alias only when the exact legacy name matters.