wizard
Skill1 starsChanged 4 months agoMITView on GitHub
First-run onboarding — detect the host Vue project's stack, confirm via checkbox prompts, sync CLAUDE.md to the real project (structure, commands), then offer /prune (opt-in — removes nothing itself). Use after copying the kit into a repo, or re-run after a stack change.
183 other projects use a version of this.
Adopted by
Most recently taken up by
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- kyoo-147/MinimalShiptheir own version, first seen Nov 15, 2026
- JamalLyons/Agent-Skillstheir own version, first seen Nov 15, 2026
- daryaKuto/claude-skillstheir own version, first seen Nov 15, 2026
- ArtisanXL/etsy-mcptheir own version, first seen Nov 15, 2026
- trajectonomics/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use setup-ts-deep-modules, writing-beats and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 42 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 56 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 49 projects that use this
ryotaroh180105Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 41 projects that use this
LesaniSkillwriting-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
Also in 54 projects that use this
simo97Skillmigrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Also in 47 projects that use this
- +1 more from Lesani
Other versions183 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 183
- mattpocock/skills★ 325ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 4.9ksame name
- bestofjs/bestofjs★ 3.1ksame name
- CelestoAI/SmolVM★ 1.2ksame name
- mdiri-ai/SoduWork★ 930same name
- moeru-ai/xsai★ 667same name
173 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- from-figmaSkill
- pruneSkill
- releaseSkill
- scaffold-componentSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 168 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Refresh the facts: Run node .claude/scripts/detect-stack.mjs (cheap, fail-open), then read .claude/.wizard/facts.json.
- Very specific: line 16
If isProject is false, there is no host project here — this is the kit repo itself or an empty dir.
- Very specific: line 17
Read isVue and metaFramework (nuxt or null).
- Very specific: line 20
If kit.onboarded is already true, this is a re-sync — say so and continue (re-running is supported).
- Distinctive: line 23
Guard the working tree: Run git status --short. If it is not clean, tell the user the wizard will edit CLAUDE.md and ask whether to proceed …
- Distinctive: line 39
Leave every other line untouched (surgical edits only).
- Very specific: line 60
Drop the marker: Write .claude/.onboarded — one short line: the date and the resolved stack (e.g.
“Common” is measured: kept by at least 6 in 10 of the 168 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Onboarding wizard
Adapts the kit to this project: detect the stack, confirm it with the user, sync CLAUDE.md to the real project, then optionally hand off to /prune. The wizard itself deletes no agents/skills/rules — pruning happens only if the user opts in at the end (step 10).
Work through the steps in order. Stop and ask whenever a value is ambiguous; never guess a stack choice silently. Prefer AskUserQuestion (checkbox/radio prompts) over asking the user to type "1, 2, 3".
- Refresh the facts. Run
node .claude/scripts/detect-stack.mjs(cheap, fail-open), then read.claude/.wizard/facts.json.- If
isProjectisfalse, there is no host project here — this is the kit repo itself or an empty dir. Stop, say so, edit nothing. - Read
isVueandmetaFramework(nuxtornull). The kit is Vue-3-only:isVue: true→ proceed.isVue: false→ tell the user the kit's rules, skills, and agents are written for Vue 3 and won't fit another framework; stop unless they explicitly confirm they want to onboard anyway (e.g. Vue lives in a workspace package the detector can't see).
- If
kit.onboardedis alreadytrue, this is a re-sync — say so and continue (re-running is supported). Cross-checkkit.claudeMdHasPlaceholders:onboarded: truetogether with placeholders still present means a previous run was interrupted or CLAUDE.md was replaced — treat it as a first run. - Surface every entry in
warningsto the user — they flag ambiguous or conflicting detection.
- If
- Guard the working tree. Run
git status --short. If it is not clean, tell the user the wizard will edit CLAUDE.md and ask whether to proceed anyway or stop to commit/stash first. Never edit a dirty tree without an explicit go-ahead (git is the only undo). - Confirm the stack — use
AskUserQuestion, not free text. Present each value as a radio question (multiSelect: false) with the detected value first, labelled(detected); rely on the automatic "Other" for the long tail. The tool caps each call at 4 questions and each question at 4 authored options — the "Other" free-text choice is added automatically on top and costs no slot. Split into two calls:- Call 1 — basics:
- Package manager —
npm|pnpm|yarn|bun. IfpackageManagerAmbiguousis true or it isnull, the user must choose (surface anywarnings). - Language — TypeScript or JavaScript (default
language). - Styling — Tailwind / Sass-SCSS / CSS Modules / scoped
<style>(defaultstyling).
- Package manager —
- Call 2 — layout:
- Structure — layer-first or feature-first (default
structure; cross-check against the realsrcDirs). - Project name — detected
projectNamefirst, the repo folder name second.
- Structure — layer-first or feature-first (default
- Skip a question only when the value is certain and there's nothing to confirm; when in doubt, ask.
- Call 1 — basics:
Apply the confirmed values to CLAUDE.md. Surgical edits only — the file may already be hand-edited (see CLAUDE.md → Working principles):
- Title
# <PROJECT_NAME>→ the project name. - Package manager — keep the
<pm>token wherever it appears. The kit is PM-agnostic by design (README: the config never hardcodes npm/pnpm/yarn/bun): the agent substitutes<pm>from the lockfile. In the Package-manager section, just state the detected manager (e.g. "Detected: pnpm (frompnpm-lock.yaml)") and drop the generic lockfile table. Do not rewrite<pm>to the concrete manager anywhere — in CLAUDE.md or the rules. - JavaScript projects: drop the TypeScript-only guidance wherever it appears — the
typecheckstep in Quality gate, and thetypescript-6 pin incode-style.md. Match on meaning, not on a remembered sentence; the wording changes between kit releases. - Leave every other line untouched (surgical edits only).
- Do not re-add what CLAUDE.md deliberately dropped — a Stack list, a Commands list, a project-structure tree, or a TypeScript-vs-JavaScript line. All four are readable from
package.json,tsconfig.json, and the source tree, and a copy in always-loaded memory only drifts (the old Commands block had already gone stale against the gate's own script resolution). The file's own header states this rule; don't work around it. One exception: add a curated Commands block if this repo'sscriptsare numerous or non-obvious enough that a short list genuinely helps — and say in the summary that you did.
The confirmed styling choice goes in
.claude/rules/styling.md, not CLAUDE.md — that rule owns the topic, and it's the one confirmed valuepackage.jsoncan't reveal (CSS Modules and scoped<style>are both built in, so no dependency distinguishes them). State the chosen approach in its opening line and drop the "if the project uses …" alternatives once decided.- Title
- Verify the rules actually attach — mechanically, then by eye. A
paths:glob that matches nothing is not an error: it fails silently and takes its whole rule with it, which is the one failure mode onboarding must not leave behind.- Run
node .claude/scripts/check-rule-globs.mjsand show the user the output. Every rule it flags with!would never load in this project. For each one, decide with the user which it is: the rule doesn't apply here (note it for the/prunehandoff in step 10) or its globs don't fit this layout (this project's source root isn't in the enumerated brace prefix — add it to that rule'spaths:, and say which rules you edited). - Then confirm by eye, because the script's matcher is not Claude Code's: open one real file per shape this repo has (a component, a composable/store, a test, the build config) and check
/context→ Memory files.srcRootin facts says where those live (src,app,resources/js,.for a flat Nuxt layout, or a monorepo package path) — scan that root, not a hardcodedsrc. - Re-run the script after any
paths:edit and don't finish this step while a rule the project needs is still flagged.
- Run
- Confirm the machine-local paths are ignored. Running
detect-stack.mjsin step 1 auto-adds.claude/.wizard/to.gitignore(ensureWizardIgnored) — confirm it, and append it manually only if it's missing (it holds the machine-local detection cache, which must not be committed). Also ensure the other two machine-local entries from the README quick-start:.claude/settings.local.jsonand.claude/worktrees/— append any that are missing. Do not ignore.claude/.onboarded(it's the committed marker teammates rely on). - Offer the native pre-commit gate (opt-in). The shipped
PreToolUsehook gates only commits made through Claude Code — a commit from a plain terminal bypasses it. Ask viaAskUserQuestion(yes/no) whether to install the same gate as a native git hook. If yes: when the repo already uses a hook manager (husky/lefthook — checkpackage.jsonand existing hook dirs), addnode .claude/hooks/pre-commit-gate.mjs --nativeto its pre-commit config instead of fighting it; otherwise write.git/hooks/pre-commit(#!/bin/sh+exec node "$(git rev-parse --show-toplevel)/.claude/hooks/pre-commit-gate.mjs" --native) andchmod +xit. Note that.git/hooks/is machine-local — teammates re-run/wizardor copy the snippet from the README. If no, mention the README documents the one-liner. - Drop the marker. Write
.claude/.onboarded— one short line: the date and the resolved stack (e.g.2026-06-26 · vue · pnpm · TypeScript · Tailwind · layer-first). It is committed, so teammates can see the repo is onboarded and skip/wizard. - Summarize. Tell the user exactly what changed in CLAUDE.md — placeholders resolved, structure synced, commands reconciled. Suggest they review
git diff CLAUDE.mdand the new.claude/.onboarded, then commit on a branch (nevermain— see CLAUDE.md → Git). - Offer to prune (opt-in). The kit still ships every agent, skill, and rule — nothing was removed. Ask the user via
AskUserQuestion(yes/no) whether to remove the capabilities this project won't use now. If yes, tell them to type/prune— it is user-invocable only (disable-model-invocation), so you cannot start it for them; that is deliberate for a destructive skill. Mention/prunewants a clean tree, so recommend committing the onboarding first. If no, remind them/pruneis available anytime later. Never remove anything without this explicit go-ahead.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

