About setup-brad-frost-skills
A setup router for the Brad Frost skills collection. It checks which skills are installed, starts setup only where needed, and briefly points out how to run skills that need no setup.
Key features
- 01Check which skills are installed
- 02Identify skills requiring setup
- 03Invoke the relevant setup flow
- 04Show how to start skills needing no setup
Use cases
- 01Set up the Brad Frost skills collection
- 02Check setup needs after adding skills
- 03Find launch commands for installed skills
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/setup-brad-frost-skillsin Claude Code to confirm it loaded.
Details
From the project READMESetup: Brad Frost skills
You are the front door for this collection. Your job is to find out what the person actually installed, run the setup that those skills need, and get out of the way. You are a router, not a second interview — never duplicate or paraphrase another skill's questions; invoke that skill and let it speak for itself.
1. Find what's installed
Check which of these skills are available to you. Prefer your own view of
the installed skills; otherwise look for the directories in the agent's
skills locations (~/.claude/skills/, .claude/skills/,
~/.agents/skills/, .agents/skills/, or wherever this agent keeps
them):
| Family | Skills | Needs setup? |
|---|---|---|
| Limits | limits-setup, limits-sessions, limits-quiet-hours, limits-endings, limits-energy | Yes — the interview |
| Design systems | ds-inspection, ds-adoption-plan | No |
| Design systems | ds-ai-rails | No; discovers the environment on its first run |
| Design systems | ds-ascii | Yes — build the design system profile |
| Product design | product-inspection | No |
| Product design | vibe-killer | Yes — build the design system profile |
| Product design | product-to-storybook | Yes — learn the host Storybook |
| Product design | storybook-to-product | No |
| Judgment | what-do-i-make-of-this | No |
If none of them are present, say so plainly and stop — tell them to
install first (npx skills add bradfrost/skills -g). Don't guess, and
don't run setup for a skill that isn't there.
2. Say what you found
One short line, then get on with it. For example:
"Found the limits skills and the design system inspection skills. The limits skills need a quick setup; the inspection skills don't. Let's do the limits."
Nothing more — no feature tour, no list of everything each skill can do.
3. Run the setups that are needed
If any limits-* skill is installed: run the limits-setup skill and
follow it exactly. It owns its own script, its own questions, and its own
close. Do not restate its questions here, and do not add your own framing
around them.
If a config already exists at ~/.config/ai-limits/config, say so and ask
whether they want to review and change their limits or leave them as they
are. Never silently overwrite limits someone already set.
If ds-ascii is installed: it needs a profile of the design system
it will be labeling before its first render. Ask whether they have a design
system they want it pointed at. If they do, run that skill's
intake/PROFILE-INTAKE.md, which reads the component vocabulary from a
manifest or an MCP where it can and interviews them where it can't. If they
don't have one, or they'd rather do it later, say that the skill will build
the profile the first time they use it and move on.
If vibe-killer is installed: it needs a profile of the design system
it will be converting pages onto. Ask whether they have one in mind. If they
do, run that skill's intake/SYSTEM-INTAKE.md, which reads the component
vocabulary and the runtime out of an MCP, a manifest, or a repo where it can
and interviews them where it can't. If they don't have a design system yet,
or they'd rather do it later, say the skill will build the profile the first
time they use it and move on.
If product-to-storybook is installed: it needs a profile of the
Storybook it will be relocating product screens into: how a story is
written there, where product screens should live, and how the design
system loads. Ask whether they have a design system Storybook. If they do,
run that skill's intake/STORYBOOK-INTAKE.md, which reads most of it out
of the repo and asks about the rest. If they don't have one yet, say the
skill will build the profile the first time they use it and move on.
If more than one of ds-ascii, vibe-killer, and product-to-storybook
is installed, run whichever intake they want first and say that the others
will read that profile rather than asking everything again.
As more skills in this collection grow setup steps, they get added here — this skill is the one place a person has to remember.
4. Point at what needs no setup
For anything installed that needs no setup, one line each — what it does and how to start it:
ds-inspection— run/ds-inspectionfrom inside your design system's projectproduct-inspection— run/product-inspectionfrom inside the product's projectds-adoption-plan— run/ds-adoption-planfrom inside a product you want moved onto your design systemds-ai-rails: run/ds-ai-railsfrom a project and point it at your design system to assess, set up, or verify the AI workflowstorybook-to-product— run/storybook-to-productfrom inside the product, and point it at the Storybook story you want to shipwhat-do-i-make-of-this— run/what-do-i-make-of-thisand paste the thing you're trying to make sense of; it asks what it needs to know about you the first time
Skip the ones they didn't install.
5. Close
If the limits interview ran, it already delivered its own close — don't add a second one. Otherwise end plainly: they're set up, and they can run this again any time they install more of these skills.