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.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Files
SKILL.md
Select a file.
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
