/cleanup
Turn a solana-ai-kit fork into a project: set up CLAUDE.md, remove kit files
> /plugin marketplace add solanabr/ai-kit> /plugin install solana-ai-kit@stbr
Command definition
cleanup.mddescription: "Turn a solana-ai-kit fork into a project: set up CLAUDE.md, remove kit files"
disable-model-invocation: true
Turn a fork or clone of the solana-ai-kit repo into a working project: install the project `CLAUDE.md` and delete the files that only serve maintaining or publishing the kit.
Steps
1. **CLAUDE.md.** If it is missing, or is the maintainer version (contains "Meta Configuration"), copy `CLAUDE-solana.md` to `CLAUDE.md`, create a starter `CLAUDE.local.md` for private notes if absent, and add `CLAUDE.local.md` to `.gitignore`. Leave an existing project `CLAUDE.md` alone. 2. **.env.** Leave it alone — don't read it, don't create it. `.env.example` is on the keep list, so print `cp .env.example .env` in the step 5 summary and point the user at `/setup-mcp` to fill it. safe-ai-skill and the High tier deny reading it, and nothing here needs its contents. 3. **Plan the removals**, each only if present (a missing path is not an error):
- Maintenance: `install.sh`, `validate.sh`, `tests/`, `CLAUDE-solana.md`, `QUICK-START.md`, `README.md` (the kit's; the user writes their own), `docs/` and `FIREWALL-SPEC.md` (the kit's own documentation), `.claude/CHANGELOG.md` (the kit's changelog), `.github/workflows/ci.yml`, `.github/workflows/claude-code-review.yml` (its prompt reviews the kit itself; keep `.github/templates/claude-code.yml`)
- Distribution infra, only needed to publish the kit: `.claude-plugin/` (plugin marketplace manifest), `plugin/` (symlinked plugin subtree), `vercel.json` (install-endpoint redirect)
- Keep: the rest of `.claude/` (agents, commands, skills, settings, `security.json`, `bin/` self-update tooling), `CLAUDE.md`, `CLAUDE.local.md`, `.mcp.json`, `.env`, `.env.example` (the tracked list of key names that `/setup-mcp` and `/doctor` read), `.env.schema` (the varlock schema for those keys), `.gitmodules`, `.github/dependabot.yml` (keeps the `ext/` skill pins current) with `.github/workflows/submodule-review.yml` and `.github/scripts/submodule-bump-review.sh` (flag risky content in those bumps), `.gitignore`, `LICENSE` (unless the user wants another), and anything the user created. If another file looks kit-specific, flag it instead of deleting it.
4. **Confirm.** Show the CLAUDE.md action and the exact removal list, and wait for the user's go-ahead. 5. **Execute**, print a summary of what was done, and suggest `git add -A && git commit -m "chore: initialize project from solana-ai-kit template"`.
Read more
description: "Turn a solana-ai-kit fork into a project: set up CLAUDE.md, remove kit files" disable-model-invocation: true
Turn a fork or clone of the solana-ai-kit repo into a working project: install the project `CLAUDE.md` and delete the files that only serve maintaining or publishing the kit.
Steps
1. **CLAUDE.md.** If it is missing, or is the maintainer version (contains "Meta Configuration"), copy `CLAUDE-solana.md` to `CLAUDE.md`, create a starter `CLAUDE.local.md` for private notes if absent, and add `CLAUDE.local.md` to `.gitignore`. Leave an existing project `CLAUDE.md` alone. 2. **.env.** Leave it alone — don't read it, don't create it. `.env.example` is on the keep list, so print `cp .env.example .env` in the step 5 summary and point the user at `/setup-mcp` to fill it. safe-ai-skill and the High tier deny reading it, and nothing here needs its contents. 3. **Plan the removals**, each only if present (a missing path is not an error):
- Maintenance: `install.sh`, `validate.sh`, `tests/`, `CLAUDE-solana.md`, `QUICK-START.md`, `README.md` (the kit's; the user writes their own), `docs/` and `FIREWALL-SPEC.md` (the kit's own documentation), `.claude/CHANGELOG.md` (the kit's changelog), `.github/workflows/ci.yml`, `.github/workflows/claude-code-review.yml` (its prompt reviews the kit itself; keep `.github/templates/claude-code.yml`)
- Distribution infra, only needed to publish the kit: `.claude-plugin/` (plugin marketplace manifest), `plugin/` (symlinked plugin subtree), `vercel.json` (install-endpoint redirect)
- Keep: the rest of `.claude/` (agents, commands, skills, settings, `security.json`, `bin/` self-update tooling), `CLAUDE.md`, `CLAUDE.local.md`, `.mcp.json`, `.env`, `.env.example` (the tracked list of key names that `/setup-mcp` and `/doctor` read), `.env.schema` (the varlock schema for those keys), `.gitmodules`, `.github/dependabot.yml` (keeps the `ext/` skill pins current) with `.github/workflows/submodule-review.yml` and `.github/scripts/submodule-bump-review.sh` (flag risky content in those bumps), `.gitignore`, `LICENSE` (unless the user wants another), and anything the user created. If another file looks kit-specific, flag it instead of deleting it.
4. **Confirm.** Show the CLAUDE.md action and the exact removal list, and wait for the user's go-ahead. 5. **Execute**, print a summary of what was done, and suggest `git add -A && git commit -m "chore: initialize project from solana-ai-kit template"`.
Claude Code, set up to ship on Solana. Not programs alone — the whole lifecycle: validating the idea, building the program and the app around it, shipping it, and the launch and growth work that follows.
Other commands on ai-kit.
More commands from other plugins.
build
CommandImplement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.

