From pell
Use at the START of any user-facing UI work in a Pell repo — building React components, pages, layouts, design systems, styling, Tailwind/CSS, marketing pages, dashboards, forms, or any task whose deliverable is something a human will look at in a browser.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pell:frontend-routerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You're about to do user-facing UI work in a Pell repo. Pell's house style is that visual work should go through the `frontend-design` plugin — it generates distinctive, production-grade interfaces that avoid generic AI aesthetics, which matches how Pell wants UIs to feel.
You're about to do user-facing UI work in a Pell repo. Pell's house style is that visual work should go through the frontend-design plugin — it generates distinctive, production-grade interfaces that avoid generic AI aesthetics, which matches how Pell wants UIs to feel.
Announce at start: "Frontend work detected — checking whether /frontend-design:frontend-design is available."
Skip this skill (and proceed normally) when the work is:
Apply this skill when the work is:
If skipping, say so in one short sentence and continue with the original task.
frontend-design is availableLook in your available skills list for frontend-design:frontend-design.
If it's available:
Tell the user:
Pell routes UI work through the
frontend-designplugin for distinctive, production-grade output. I'll use/frontend-design:frontend-designfor this work unless you'd rather I build it directly.
Then invoke the frontend-design:frontend-design skill via the Skill tool and follow its guidance. Do not duplicate its workflow — let it own the design loop.
If it's NOT available:
Tell the user (notify, don't block — this is per the Pell architecture spec §4):
Heads up: this UI work would benefit from the
frontend-designplugin, which isn't installed. You can install it with:
/plugin install frontend-design@claude-plugins-officialWant to install it before continuing, or should I build the UI directly without it?
Possible continuations:
/reload-plugins, then invoke frontend-design:frontend-designfrontend-design so the user can revisit laterOnce routed (or after the user opts to skip), continue with the original task. This skill is a router, not a workflow — its job ends after the decision is made.
frontend-designnpx claudepluginhub froncekb/pell_skills --plugin pellGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.