init-project
/init-project
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.
- Author
- microbus-io ↗
- Repository
- fabric ↗
- Licence
- Apache-2.0
- Last repository change
- 23.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Original author 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.
How it works
- Workflow
SKILL.md preview
---
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.
## Workflow
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
```
#### Step 1: Check if a Microbus Project
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.
#### Step 2: Download Agent Rules and Skills
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.
```shell
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
```
#### Step 3: Scaffold the Project
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.
```shell
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.
#### Step 4: Verify the Build
Confirm the scaffolded project compiles.
```shell
go vet ./main/...
```
#### Step 5: Offer the Tour
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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · microbus-io/fabric | 100 | Apache-2.0 |
| cardene777/agent-shuriken | 100 | MIT |
| neuromechanist/research-skills | 100 | BSD-3-Clause |
| popiliadam/platinum-seo-engine | 100 | AGPL-3.0 |
| huangwb8/skills | 100 | MIT |
| kangig94/coral | 92 | MIT |
Database snapshot: 13.11.2026 · package version 3f095b52ba2e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100upgrade-microbus
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… - 100gitignore-builder
Build and merge .gitignore files using github/gitignore templates with smart project detection. Use when the user asks to "create gitignore", "build .gitignore", "add gitignore templates", "set up gitignore", "update gitignore", or requests "/gitignore". Also trigger when… - 95project-init
Use this skill when the user says 'create project structure', 'scaffold project', 'initialize project', 'set up folder structure', 'new project from scratch', or when a new project needs folders and config files created. This skill scaffolds the full project tree based on… - 100project-init
Interview-based project setup — generates CLAUDE.md, ROADMAP, .gitignore, .env.example from scratch. Use when: user says '/project-init', 'new project', 'project creation', 'project setup', 'create project'. NOT for AI agent/harness configuration (use setup for that).… - 100take-tour
Runs the agent-guided tour of Microbus using examples. Use when the user asks to take the tour. - 100init-repo
Bootstrap a new n8n workflow repo from scratch. Scaffolds directory structure, writes plugin-compatible CLAUDE.md/README/.gitignore/.env.example, runs the n8nac >= 2.3 setup flow (`env add` + `env auth set` + `env use`), pulls node schemas, and verifies setup. Use when starting…