project-starter

claude-toolkit

BeSpunky's one place for Claude Code skills, subagents, and commands. Develop them here once, install them into any project, and upgrade everywhere with a single update.

This is a Claude Code plugin marketplace (a git repo). It currently ships one plugin:

Plugin	Provides	Purpose
project-starter	skill new-project	Scaffold a new BeSpunky-standard project: integrated Nx monorepo + Angular (clean --minimal app) + devcontainer (Claude CLI & VS Code extension) + tailored CLAUDE.md.

Layout

claude-toolkit/
├── .claude-plugin/marketplace.json          # lists the plugins in this marketplace
└── plugins/project-starter/
    ├── .claude-plugin/plugin.json
    └── skills/new-project/
        ├── SKILL.md                          # the scaffolding skill (orchestrator)
        └── assets/
            ├── scaffold.sh                   # nx generators run inside the devcontainer base image (Docker, no nvm)
            ├── devcontainer.json             # Claude CLI feature + Claude VS Code extension + .claude persistence
            ├── project-settings.json         # .claude/settings.json wired into new projects
            └── CLAUDE.md.tmpl                # base CLAUDE.md (generator-first guidance)

To add a skill: plugins/<plugin>/skills/<name>/SKILL.md. To add a subagent: plugins/<plugin>/agents/<name>.md. To add a slash command: plugins/<plugin>/commands/<name>.md. Register new plugins in .claude-plugin/marketplace.json.

Install

/plugin marketplace add BeSpunky/claude-toolkit
/plugin install project-starter@claude-toolkit

…or add to ~/.claude/settings.json so every project sees it:

{
  "extraKnownMarketplaces": {
    "claude-toolkit": { "source": { "source": "github", "repo": "BeSpunky/claude-toolkit" } }
  },
  "enabledPlugins": { "project-starter@claude-toolkit": true }
}

Skills are namespaced as project-starter:new-project. Scaffolded projects already get a .claude/settings.json referencing this marketplace, so the toolkit's skills are available inside every new project automatically.

Upgrade everywhere

Every project points at the same marketplace repo, so upgrading is central:

git -C ~/projects/claude-toolkit pull        # or push new skills up
/plugin marketplace update claude-toolkit     # in any session
/reload-plugins                               # pick up changes mid-session

Enable auto-update for the marketplace (in /plugin → Marketplaces) to fetch updates at startup.

How the scaffolder works

scaffold.sh <project> [app]:

1. Resolves the newest mcr.microsoft.com/devcontainers/typescript-node:<major> tag (Node source — no nvm).
2. Runs the Nx generators inside that base image via docker run (as your uid, mounting ~/projects):
   • yarn create nx-workspace <project> --preset=apps --packageManager=yarn --nxCloud=skip --no-interactive
   • yarn nx add @nx/angular
   • yarn nx g @nx/angular:application apps/<app> --minimal --style=scss --routing --e2eTestRunner=none
3. Writes the files Nx does not own: .devcontainer/devcontainer.json, .claude/settings.json, .gitignore entry.

The new-project skill then authors a tailored CLAUDE.md.

The generated .devcontainer/devcontainer.json pre-installs this marketplace on build via its postCreateCommand (claude plugin marketplace add BeSpunky/claude-toolkit && claude plugin install project-starter@claude-toolkit --scope project), so the toolkit's skills/agents are live the moment the container comes up. Declaring enabledPlugins in settings alone does not auto-install — the CLI step is what makes it immediate inside the container; on the host, the settings declaration offers a one-click install on first run.

Generator-first, manual last. A literal angular-* preset always forces a demo app (verified against Nx source), so we use apps + nx add @nx/angular + a --minimal app — the only one-shot path to an Angular workspace with no demo content.