The principles-driven stack materializer — implements the vwf stack-adapter contract with a dispatch rule: a technology a shipped pack covers is copied from the pack; anything uncovered is generated (Context7 research → vwf's principles catalog → the stackgen-skill-reviewer gate). Both paths land directly in the repo's committed .claude/ tree — skills, agents, hooks and rules only, structured per a closed kind vocabulary, recorded in a lockfile — editable and plugin-independent for collaborators. Re-sync is explicit and diffed, never silent. Waves A–C landed 21 packs and 19 bundles across seven kinds; Wave D adds the eighth kind, deploy-target, whose container-image pack is the curated answer the container-generic bundle used to generate, assets/artifact-doctrine.md — the host rules deciding whether a generated skill, agent or hook is valid at all — and the ninth kind, design-tool, whose three packs land vwf's design adapters at fixed names in the repo's own .claude/. Two tool axes (design, cicd) let a pack be reached by the config token that selects it, which is what rescued a CI pack no menu could offer.
Claude Code3 Skills