Summary
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.
Install to Claude Code
npx -y skills add akillness/oh-my-skills --skill frontend-design-system --agent claude-codeInstalls into .claude/skills of the current project.
Plug Mailtrap into your AI workflow and let it handle the email.
Connect Mailtrap MCP →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
Make coding agent sessions - Searchable, Shareable, Vendor-neutral & Scored.
Try For Free →
Your agent targets a perfect 10 Code Health score. Deterministic. Every commit.
Try For Free →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →
Files
SKILL.md
Select a file.
Featured
Plug Mailtrap into your AI workflow and let it handle the email.
Connect Mailtrap MCP →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →Make coding agent sessions - Searchable, Shareable, Vendor-neutral & Scored.
Try For Free →Your agent targets a perfect 10 Code Health score. Deterministic. Every commit.
Try For Free →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →
