stackgen

v0.15.0

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

By Viraj Patel1 GitHub starsUpdated 1 hour ago

Directory evidence

Runtimes: Claude Code
Parsed components: 3 skill or MCP entries
Source updated: Aug 30, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install plugin

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install stackgen@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/virajp/ai-plugins

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/stackgen/.

Plugin files

plugins/stackgen/

├── .claude-plugin/plugin.json
├── skills/stackgen-stack-menu/SKILL.md
├── skills/stackgen-stack-template/SKILL.md
└── skills/stackgen-sync/SKILL.md

Included Skills3

stackgen-stack-menuskills/stackgen-stack-menu/SKILL.md

Return the stack options the stackgen plugin offers — its shipped packs plus the one open entry, generate-for-anything-uncovered — as a vwf menu payload. Invoked by /vwf:architecture and /vwf:setup when `stackgen` is listed in the config's `stacks:` — not a general-purpose skill.

stackgen-stack-templateskills/stackgen-stack-template/SKILL.md

Return one stackgen stack as a vwf template payload — reading the materialized entry from the repo's .claude/ tree, or, on a first pin, resolving the bundle's composition and dispatching per component (shipped pack components copied, uncovered components generated) behind a consent gate. Invoked by /vwf:architecture, /vwf:setup, /vwf:plan and /vwf:execute — not a general-purpose skill.

stackgen-syncskills/stackgen-sync/SKILL.md

Diff the repo's materialized .claude/ entries against the current component packs (and offer regeneration per generated component), presenting the delta for consent — the explicit re-sync that makes drift visible without ever overwriting silently. Run after upgrading stackgen, or any time you want to see how far the repo's copies have drifted.

Plugin manifests1

plugins/stackgen/.claude-plugin/plugin.json

{
  "$schema": "https://www.schemastore.org/claude-code-plugin-manifest.json",
  "name": "stackgen",
  "version": "0.15.0",
  "description": "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.",
  "author": {
    "name": "Viraj Patel"
  },
  "keywords": [
    "stackgen",
    "stacks",
    "skills",
    "generation",
    "principles",
    "materializer",
    "vwf-stack-adapter"
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[stackgen on Agent Plugins Marketplace](https://pluginsmp.com/plugins/stackgen)