-
Notifications
You must be signed in to change notification settings - Fork 0
Commands
github-actions[bot] edited this page Apr 9, 2026
·
25 revisions
Interactive wizard that scaffolds AI tooling into a project.
Arguments:
-
directory— target directory (default: current directory)
What it does:
- Asks you to pick a team profile (sets smart defaults for all subsequent choices)
- Asks for project name, description, and package manager
- Asks you to pick platforms, rules, agents, skills, and MCP servers
- Creates
llm/directory with selected starter content - Generates
bluetemberg.config.json - Creates
AGENTS.mdandCLAUDE.md(if Claude selected) - Writes
llm/mcp.jsonwith chosen MCP preset ids (if MCP selected); the initial sync step generates.claude/mcp.json,.github/mcp.json, and/or.cursor/mcp.jsonfrom that manifest (per selected platforms) - Adds
sync:llm-configscripts topackage.json - Patches
.prettierignorewithllm/anddocs/wiki/to protect prose from formatters - Runs an initial sync to generate all platform-specific files
Universal guardrail rules are always included and shown as non-deselectable in the rules step. See Profiles for what each team profile pre-checks.
Example:
npx @prototypdigital/bluetemberg init
npx @prototypdigital/bluetemberg init ./my-projectReads vendor-neutral sources from llm/ and generates platform-specific files.
Arguments:
-
directory— project root directory (default: current directory)
Options:
| Option | Description |
|---|---|
--check |
Dry-run mode; exits with code 1 if any generated files are out of sync |
--dry-run |
Alias for --check
|
--silent |
Suppress all output (useful in scripts and CI) |
Example:
npx bluetemberg sync
npx bluetemberg sync --check
npx bluetemberg sync --dry-run --silent
npx bluetemberg sync ./my-projectWhen to run:
- After creating or editing any file in
llm/rules/,llm/agents/,llm/skills/,llm/mcp.json,llm/hooks.json,llm/commands/, orllm/prompts/, or after changing the optionaladapterslist inbluetemberg.config.json - In CI to verify generated files haven't drifted (use
--check)
After running init, these scripts are added to your package.json:
| Script | Command |
|---|---|
sync:llm-config |
npx bluetemberg sync |
sync:llm-config:check |
npx bluetemberg sync --check |