The Builder Bundle

Solo SaaS founder shipping the next feature

A founder running a $5K MRR micro-SaaS picks up the next ticket. Researcher dispatches parallel workers to map user pain. Plan Challenger stress-tests the proposed solution. Context7 injects the current Supabase and Next.js docs during the build. Impeccable polishes the new flow. /ship opens the PR. /land-and-deploy merges and verifies production. /canary watches the post-deploy window. One operator. Seven roles. No tooling friction between phases.

Indie hacker running multiple products simultaneously

An indie hacker with three products in different stages keeps shipping rhythm with the same skill set across all three. Each product is a separate repository. The bundle installs once at the user level and applies to every project. Context-switching between products no longer means relearning a tooling stack per repo. The Builder Bundle is the same in every working surface.

AI agent builder working at the frontier

A builder working on Claude Code plugins or n8n workflows operates where documentation is incomplete and APIs change weekly. Context7 is the load-bearing skill: live docs on every coding pass remove the hallucination tax that compounds across an unstable surface. Source Harvest (from the Foundational layer) extracts integration patterns from upstream MCP servers. Plan Challenger catches MCP integration assumptions before they break at runtime.

Plugin author extending an existing platform

A builder shipping Obsidian, VS Code or Figma plugins works inside platform constraints. Impeccable enforces visual fluency that matches the host platforms expectation. /ship and /land-and-deploy handle the marketplace publishing rhythm. /canary monitors the install metrics post-publish. The substrate plus the Builder Bundle covers the full plugin lifecycle from idea to deprecation.

Does the Builder Bundle include the Foundational Creator Bundle?

No. The Builder Bundle assumes the Foundational Bundle is already installed. Install /bundles/foundational-creator first if you have not already. The two-layer architecture means the medium-specific skills (gstack, Context7, Impeccable) install once on top of the universal substrate (Researcher, Plan Challenger, Source Harvest, Skill Creator, Systematic Debugging plus Content Strategy and AI SEO).

Why does gstack install differently from Context7 and Impeccable?

Context7 and Impeccable ship as Claude Code marketplace plugins, so they install via settings.json registration. gstack ships as a single repository with 30+ slash commands and its own setup script. The gstack maintainer chose this distribution model intentionally to keep the toolkit tightly integrated. The Builder Bundle install script handles both patterns in one run.

I only want /ship, /land-and-deploy and /canary from gstack. Can I skip the rest?

gstack distributes as one bundle. Installing brings the full slash-command set. The other commands (CEO review, eng manager, QA, retro and the rest) do not auto-execute. They become available when you invoke them. Most solo builders find at least three or four additional gstack commands useful within the first week. Skipping the install would mean cherry-picking individual command files manually, which the gstack repo does not support cleanly.

Is Context7 a Claude Code plugin or an MCP server?

It ships as a Claude Code marketplace plugin (context7-plugin under the context7-marketplace marketplace). The plugin internally manages the MCP-style live-docs lookup. You install it via the Builder Bundle script and it works across Claude Code sessions. For Cursor or other AI editors, follow the alternate install path documented in the upstash/context7 repository.

What does the install script actually change on my system?

It edits Claude Code settings.json (default ~/.claude/settings.json) to register two marketplaces (context7-marketplace, impeccable) and enable two plugins. It clones github.com/garrytan/gstack into ~/.claude/skills/gstack and runs the gstack setup script. It writes a timestamped backup of settings.json before any edit. The script prints every change before applying.

Is the install reversible?

Yes. To remove the marketplace plugins, restore settings.json from the backup the script writes, or run /plugin uninstall for each plugin from inside Claude Code. To remove gstack, delete ~/.claude/skills/gstack. No system-level changes happen.

How does the Builder Bundle relate to the other avatar bundles?

Same two-layer pattern across every avatar bundle. The Foundational Bundle is the substrate. The Writer, Performer, Teacher, Curator and Strategist bundles each ship a small medium-specific layer on top. A creator who works as both a Builder and a Writer installs the Foundational Bundle once plus both avatar bundles. No skill duplication.