メニュー
TRIGGER when user asks to initialize, set up, or bootstrap a Microbus project. Scaffolds main/main.go, config files, agent files, .gitignore, VS Code launch config, Claude Code permissions, and the token-signing key.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
TRIGGER when the user asks to upgrade the project to a newer or the latest version of Microbus, or to update the framework. Each Microbus release ships this one self-contained skill; it applies that release's single-version migration, then chains to the next release's copy of this skill until the target version is reached.
TRIGGER when user asks to create, scaffold, or initialize a new microservice.
How to choose the hostname of a new Microbus microservice. Referenced by the add-microservice and add-sql-microservice scaffolding skills (and, through their delegation to add-microservice, by add-python-microservice and import-openapi-microservice). Consult it whenever a microservice's hostname is being chosen.
Performs an architectural review of a microservice-based system built on the Microbus framework. Covers only cross-cutting, cross-microservice concerns - service boundaries, the dependency graph, coupling, cross-service consistency, data ownership, workflow composition, edge security, and system operations. Anything judgeable inside a single microservice directory belongs to the review-microservice skill and is out of scope here. Produces a structured report with findings and recommendations.
Reviews the microservices touched by a set of changes - by default the whole current feature branch versus its merge-base with main, plus any uncommitted work. Runs the review-microservice skill on each changed microservice and the review-architecture skill scoped to those microservices and their graph neighbors, then consolidates one report. Use before merging a branch or before committing working-tree changes.
Performs a thorough review of a single Microbus microservice. Checks for completeness, framework compliance, code quality, security, test coverage, documentation, API design, and data access performance. Produces a structured report with findings and recommendations.
| name | init-project |
| description | TRIGGER when user asks to initialize, set up, or bootstrap a Microbus project. Scaffolds main/main.go, config files, agent files, .gitignore, VS Code launch config, Claude Code permissions, and the token-signing key. |
CRITICAL: Do NOT explore or analyze the project unless explicitly instructed to do so. The instructions in this skill are self-contained.
Copy this checklist and track your progress:
Initialize a project to use Microbus:
- [ ] Step 1: Check if a Microbus project
- [ ] Step 2: Download agent rules and skills
- [ ] Step 3: Scaffold the project
- [ ] Step 4: Verify the build
- [ ] Step 5: Offer the tour
If go.mod does not exist in the project directory, this is not a Go project. Exit this workflow.
If go.mod does not include a reference to github.com/microbus-io/fabric, this is not a Microbus project. Exit this workflow.
Note whether main/main.go already exists. If it does not, this is a new install - remember this for Step 5.
Copy the agent rules and skills from the pinned Microbus version already in the Go module cache. This is version-matched to go.mod and needs no network access. The module cache is read-only, so make the copies writable.
src="$(go list -m -f '{{.Dir}}' github.com/microbus-io/fabric)"
mkdir -p .claude
cp -R "$src/.claude/rules" "$src/.claude/skills" .claude/
chmod -R u+w .claude/rules .claude/skills
Run geninit to scaffold the project. It is idempotent: it creates main/main.go, main/env.yaml, CLAUDE.md, config.yaml, config.local.yaml, env.yaml, env.local.yaml, .gitignore, .vscode/launch.json, and .claude/settings.json, and generates a fresh Ed25519 token-signing key for bearer.token.core in config.local.yaml. Existing files are left intact.
go run github.com/microbus-io/fabric/cmd/geninit
.claude/settings.json auto-approves the Bash commands invoked by the housekeeping and regenerate-boilerplate skills, so an agent following them is not prompted for each invocation. The file is project-shared and should be checked into git.
Confirm the scaffolded project compiles.
go vet ./main/...
If this is a new install (from Step 1), tell the user the project is ready and offer to take the agent-guided tour, which runs the bundled example microservices. If they accept, follow the take-tour skill. If this is not a new install, skip this step.