ai-design-vault: Skill for Claude Code

Adapt the kit to this project

The kit ships framework-neutral. This procedure fits it to the host project once, so every rule, skill and check afterwards points at real paths and real packages.

Detect from evidence, not from vibes. A package.json dependency, a config file, a directory that exists — those are evidence. "It's probably Next" is not.

1. Gather evidence

.claude/scripts/detect-stack.sh

Read its output fully. Then open what it flagged: the manifest, the framework config file, the top-level source tree. If the framework is one you have not seen in this exact version, read the installed docs rather than recalling an API (node_modules/<framework>/**, the framework's own docs site). Frameworks rename things between majors — that is exactly what this kit warns about.

references/frameworks.md in this skill folder holds the mapping for the common stacks: paths, bindings, capabilities and the trap each one carries. Use it as a starting point, then confirm each value against the real repo — a project is allowed to lay itself out however it likes, and the repo wins over the table.

2. Resolve every field

Work through .claude/stack.schema.json field by field. Rules:

• Paths must exist, or be deliberately created. Never record a path that is not there. The one exception is paths.views — most frameworks have no such concept, and the route→view convention is one of the kit's load-bearing rules (see obsidian/frontend/routing-views.md). Create the directory, and say so.
• paths.protected starts empty unless the project actually carries a vendored motion engine or generated code that must not be hand-edited.
• paths.routeEntryGlob matters where any file is a route. Astro (["*.astro"]) and Nuxt (["*.vue"]) name pages freely; leave it empty where the framework has a fixed entry filename. Get this wrong and the route→view check silently inspects nothing.
• Bindings come from what is installed. Read package.json — do not assume the house default is present. A binding that does not exist yet is null.
• envPublicPrefix is not cosmetic. It is what verify.sh uses to tell a leaked secret from a public value. Get it right per framework (Vite VITE_, SvelteKit/Astro PUBLIC_, Next NEXT_PUBLIC_, Nuxt NUXT_PUBLIC_).
• Commands are verbatim, with the package manager — pnpm build, not build. Take them from scripts in the manifest; if a script is missing, record null rather than inventing one.
• Capabilities decide which checks run. serverComponents: false on a SPA is correct and makes the server-first check skip instead of failing noise.
• notes[] is for what the fields cannot say — a non-standard layout, a deliberate deviation, a quirk you hit while detecting. Later agents read it.