Frontend Design
Detect that the renamed impeccable skill replaced this stub and update or delete the deprecated frontend-design folder in your agent setup.
Overview
frontend-design is an agent skill for the Build phase that redirects deprecated installs to the impeccable skill and must not be used for actual UI design.
Install
npx skills add https://github.com/pbakaus/impeccable --skill frontend-designWhat is this skill?
- Explicitly deprecated alias for the impeccable skill
- Instructs agents to run /impeccable when that skill is installed
- Recommends npx impeccable skills update when impeccable is missing
- Tells users the frontend-design folder is safe to delete after migration
Adoption & trust: 53.7k installs on skills.sh; 35.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent still loads a legacy frontend-design skill folder and might try to design from obsolete instructions instead of impeccable.
Who is it for?
Anyone auditing an impeccable-based skill install who wants a clear migration message when an old frontend-design path is still on disk.
Skip if: Solo builders who need typography, layout, or component design—use impeccable directly and remove this stub.
When should I use this skill?
Agent or user invokes the deprecated frontend-design skill instead of impeccable.
What do I get? / Deliverables
The agent stops design work here, routes to /impeccable or the skills update command, and you can delete the deprecated folder once impeccable is available.
- Redirect message to /impeccable
- Optional confirmation that the legacy folder can be deleted
Recommended Skills
Journey fit
The skill only exists as a frontend-facing redirect in the build phase; it does not perform design work itself. Catalog entry maps to frontend UI work, but the SKILL.md forbids design execution and points builders to impeccable instead.
How it compares
A deprecation pointer in a skill package, not a design workflow or MCP server.
Common Questions / FAQ
Who is frontend-design for?
It is for developers and agent setups that still reference the old frontend-design name in the impeccable repo; it explains the rename and next step.
When should I use frontend-design?
Only when an agent accidentally invokes this legacy skill during Build frontend work—then it should immediately switch to /impeccable or run npx impeccable skills update.
Is frontend-design safe to install?
It is low-risk documentation-only redirection; review the Security Audits panel on this Prism page before trusting any skill in your environment.
Workflow Chain
Requires first: impeccable
Then invoke: impeccable
SKILL.md
READMESKILL.md - Frontend Design
This skill has been renamed to **impeccable**. All design functionality now lives in the `/impeccable` skill. Check if the impeccable skill is available: - If `/impeccable` exists, use it directly. You can safely inform the user that the `frontend-design` folder is a deprecated leftover and can be deleted. - If `/impeccable` does NOT exist, tell the user to update their skills by running `npx impeccable skills update` in their terminal. Do NOT attempt any design work from this skill. Redirect to `/impeccable` instead.