stackgen
claudeThe principles-driven stack materializer — implements the vwf stack-adapter contract with a dispatch rule that runs per component: a component a shipped pack covers is copied verbatim; an uncovered one is generated (per-topic Context7 research → vwf's principles catalog → the stackgen-skill-reviewer gate, capped at four rounds). A materialization lands in the repo's committed .claude/ tree — skills, agents, hooks and rules — plus, for packs that ship one, a config/ tree mirroring the repo root; language servers go to the generated local plugin vwf-tools outside the repo, together with every MCP server a component declares, never into a repo file. Every artifact is shaped by a closed kind vocabulary, recorded per component in a lockfile, editable and plugin-independent for collaborators. Re-sync is explicit, per component and lockfile-diffed, never silent. Ships curated packs and bundles across a closed kind vocabulary, inventoried in stacks/inventory.md; a bundle is a recorded composition of component refs, never a directory. Three tool axes (design, cicd, stylesheet) let a pack be reached by the config token that selects it, which is what rescued a CI pack no menu could offer; optional tools (context7, notion, taste-skill) are an addon axis the user picks. assets/artifact-doctrine.md carries the host rules deciding whether a generated skill, agent or hook is valid at all, and assets/contracts/ the provider-neutral capability doctrine each category is compared against. .claude/settings.json is written only behind its own explicit consent line, merging never owning.
78 skills · 1 agent