This is a compatibility shim that exists so legacy workflows referencing frontend-design-system keep working while routing real design system work to the canonical design-system skill. Use it only when a script, migration tool, or user explicitly names the old skill identifier. For actual UI system work like design tokens, component libraries, or dashboards, go straight to design-system instead. The guidance is intentionally thin because this is just a redirect layer with alias routing notes, not a standalone knowledge base. Honest take: it's housekeeping infrastructure that prevents breaking old integrations during a consolidation cleanup, nothing more.
npx skills add https://github.com/akillness/oh-my-skills --skill frontend-design-system