Claude Code Starter Kit plugin

Q: What does `init` install?

The kit's commands, hooks and skills go into ~/.claude/. After that /new-project, /review and /commit work in any Claude Code session.

Q: Can the kit be added to an existing project?

Yes. /convert-project-to-starter-kit merges commands, hooks, skills and CLAUDE.md rules without deleting existing files and makes a safety commit.

Claude Code scaffold with 27 commands, 10 hooks and 25 skills installed globally to set common rules for every project.

342 ★ on the repository
Last commit Jun 29, 2026
MIT

Plugin

thedecipherist/claude-code-mastery-project-starter-kitAuthor:TheDecipherist

Install

Works in: Claude Code

Manual install

npx @claude-code-mastery/starter-kit init

The first README command installs commands, hooks and skills globally into `~/.claude/`.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

Hooks and commands are written to `~/.claude/` and run scripts in every session.

This is third-party code. Review the repository files before installing.

What it does

Starter Kit is a project template for Claude Code. Running `npx @claude-code-mastery/starter-kit init` places 27 commands, 10 hooks and 25 skills in `~/.claude/`, after which `/new-project`, `/review`, `/commit` and `/mdd` work in any session. Hooks block dangerous Bash commands, commits to the main branch and secret leaks, and run a linter when a file is saved. The main MDD (Manual-Driven Development) flow runs documentation, tests, then code; audits and MDD modes live in a separate `@thedecipherist/mdd` package.

Who it is for. Claude Code developers who want ready commands, hooks and rules in every session without configuring from scratch.

Good fit when

A new project starts with `/new-project my-app clean` and a ready structure.
Before a commit, `/review` shows rule violations with severity ratings.
An existing project is brought to common rules with `/convert-project-to-starter-kit`.
A team forks the kit and publishes its own package with shared standards.

Not a fit when

You need a runnable app template: the repository is not an application itself.
The team does not want enforced rules and hooks: the kit enforces its own rules.
You need one skill rather than 27 commands and ten hooks.

Example request

Create a project `my-app` with `/new-project`, configure `.env` with `/setup` and show the command list with `/help`.

Limitations

The repository is a template, not an application: `pnpm dev` there starts nothing. Global install writes to `~/.claude/`, and `/install-global` reports conflicts with existing files separately. The README recommends WSL mode on Windows. MDD modes install as a separate package. The kit sets working rules firmly through `CLAUDE.md` and hooks, so read them before adopting it in a team and drop what is unneeded. Last commit: June 2026.

How to disable. Remove the kit's commands, hooks and skills from `~/.claude/` and the hook entries from `settings.json`. In projects created with `/new-project`, delete the copied `.claude/` directory by hand.

FAQ

What does `init` install?

The kit's commands, hooks and skills go into `~/.claude/`. After that `/new-project`, `/review` and `/commit` work in any Claude Code session.

Do I need to clone the repository?

No. The global npm install works without a clone. Clone it only to change the templates.

What is MDD?

A flow where every feature starts with documentation and every fix with an audit. It ships as a package: `npm install -g @thedecipherist/mdd && mdd install`.

Can the kit be added to an existing project?

Yes. `/convert-project-to-starter-kit` merges commands, hooks, skills and `CLAUDE.md` rules without deleting existing files and makes a safety commit.

What if hooks do not fire?

The README has a Hooks Not Firing section with diagnostics. Start by checking that the hooks are registered in `settings.json` and the scripts are executable.

Discussion

No questions or reviews yet.

Plugins