Power your agent
पब्लिशर की अपनी कमांड। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
npx -y [email protected]Claude Code में लोकल कमांड के लिए इंस्टॉल लिंक नहीं है। नीचे दी गई कमांड कॉपी करें और टर्मिनल में चलाएँ।
claude mcp add bluetemberg -- npx -y bluetemberg@0.20.1टर्मिनल में चलाएँ।
{ "mcpServers": { "bluetemberg": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
AI coding standards, shipped like a dependency. Version-locked, integrity-verified, signed, and routed to the right engineer and the right stack version. Installed with one command.
A platform team maintains packs in bluetemberg-packs. Developers run bluetemberg init --profile frontend + bluetemberg install. Teammates with no local tooling install a Claude Code Marketplace plugin with one click. Everyone stays in sync.
Published on npm as
bluetemberg— MIT licensed. Requires Node.js 20+.
prototypdigital.github.io/bluetemberg → — install guide, pack browser, and docs.
Supply-chain controls: SHA-512 integrity and ECDSA registry signatures verified on every install. Registry host is pinned — metadata cannot redirect downloads to an attacker-controlled host. Tarballs are size-capped and path-traversal-filtered on extraction. See SECURITY.md.
Good. That solves the format, not the distribution.
A shared file still has no versioning, no integrity verification, no
per-role filtering, and no way to stop a Payload 2 rule from reaching a
Payload 3 repo. Bluetemberg emits AGENTS.md too. It also answers who
gets which rules, at which version, and how you know the content was not
tampered with in transit.
Profiles are role-matched default selections — not bundles. The wizard pre-selects the collections, agents, and skills most relevant to your role. You can add or remove anything. The value is that the content behind those selections is versioned, integrity-verified, and fetched from npm like an ESLint plugin.
npx bluetemberg init
Or add it as a dev dependency:
npm install -D bluetemberg
# or
pnpm add -D bluetemberg
Agents and CI never get a usable TTY, so init also supports deterministic paths:
# Profile defaults (+ optional overrides) without prompts
npx bluetemberg init --non-interactive --profile devops
# Full answers from JSON (matches the `InitAnswers` field list in packaged types / `bluetemberg --help --json`)
npx bluetemberg init --config ./bluetemberg.init.json
# Quiet CI logs (still check exit codes; pairs with `--non-interactive` or `--config`)
npx bluetemberg init --non-interactive --profile devops --silent
# Machine-readable catalogs (profiles, rules, agents, skills, MCP presets, CLI flags)
npx bluetemberg --help --json
Developing from a clone: run npm run build before bin/cli.js — the CLI imports dist/ (including --help --json and preset validation constants).
The interactive wizard will ask you to pick:
--profile agentic in headless runs)stacks (--stacks [email protected],nextjs@auto in headless runs)llm/mcp.json → Claude / Copilot / Cursor MCP config (interactive, context7, figma, github)llm/rule-sources.json (--sources <csv> in headless runs)--force to replace; --omit-github to skip them in headless runs)You can also add llm/hooks.json (Cursor hooks), llm/hooks.claude.json (Claude Code hooks — honored from the project's own llm/ only; packs cannot ship them), llm/commands/*.md (Claude slash commands), llm/prompts/*.md (Copilot *.prompt.md), and optional adapters in bluetemberg.config.json for custom ESM emitters; see the wiki (Writing Hooks, Writing Commands, Writing Prompts, Adapters).
It scaffolds llm/ as the vendor-neutral source of truth, generates platform-specific files, and patches .prettierignore to protect your prose files from the formatter.
your-project/
├── bluetemberg.config.json # Platforms, targets, source dir
├── AGENTS.md # Project context for AI tools (Codex rules block appended if Codex selected)
├── CLAUDE.md # `@AGENTS.md` import + Claude-specific notes (if Claude selected)
├── GEMINI.md # Gemini CLI pointer (if Gemini selected) — do not edit
├── llm/
│ ├── rules/ # Vendor-neutral rules
│ ├── agents/ # Specialist agent definitions
│ ├── skills/ # On-demand skill workflows
│ ├── mcp.json # Optional — MCP presets and/or inline servers (if you add it)
│ ├── hooks.json # Optional — Cursor hooks (if you add it)
│ ├── hooks.claude.json # Optional — Claude Code hooks (project-local only)
│ ├── commands/ # Optional — Claude slash commands (if you add it)
│ └── prompts/ # Optional — Copilot prompt sources (if you add it)
├── .cursor/rules/ # Generated — do not edit
├── .cursor/skills/ # Gitignored — source of truth is llm/skills
├── .cursor/agents/ # Gitignored — source of truth is llm/agents
├── .cursor/mcp.json # Generated (Cursor) — do not edit
├── .cursor/hooks.json # Generated (Cursor) — do not edit
├── .claude/rules/ # Generated — do not edit
├── .claude/agents/ # Generated — do not edit
├── .claude/skills/ # Generated — do not edit
├── .github/instructions/ # Generated — do not edit
├── .github/agents/ # Generated — do not edit
├── .github/skills/ # Generated — do not edit
├── .gemini/context/ # Generated — do not edit
├── .windsurf/rules/ # Generated — do not edit
├── .windsurf/skills/ # Generated — do not edit
├── .windsurf/workflows/ # Generated — do not edit
├── .agents/skills/ # Generated (Codex skills, vendor-neutral) — do not edit
├── .codex/agents/ # Generated (Codex subagents, TOML) — do not edit
└── .codex/config.toml # Generated MCP block (Codex) — managed section only
Every generated Markdown and TOML file carries that warning in the file itself, right after its frontmatter — rules, agents, skills, commands, Copilot prompts, Windsurf workflows, Codex agents, marketplace plugin content, and the GEMINI.md / copilot-instructions.md copies of AGENTS.md. JSON outputs can't carry a comment, so mcp.json and the marketplace manifests are the exception:
A .gitignore entry and a comment in this tree only help someone reading the repo root. The banner travels with the file, so an editor who opens .claude/rules/x.md directly — or an agent that greps into it — sees that edits there are disposable and where the real source is. This matters most in projects that commit their generated output so sync --check can verify parity in CI: generated and hand-authored markdown then sit side by side, otherwise indistinguishable.
When claude-marketplace is in platforms, sync also generates:
.claude-plugin/
└── marketplace.json # Root manifest listing all plugins
plugins/
└── <plugin-name>/ # One directory per plugin defined in marketplace.plugins
Official Bluetemberg plugin packs (frontend, fullstack, backend, devops) are served from prototypdigital/claude-marketplace, generated from bluetemberg-packs content — add them with /plugin marketplace add prototypdigital/claude-marketplace. See Marketplace.
Rules are delivered as versioned npm packages from the bluetemberg-packs registry. The init wizard pre-selects collections based on your team profile; you can add or remove any collection before confirming.
Core packs (all standard profiles) — auto-included for all profiles except Custom (Custom users must opt into these collections manually):
Profile-specific packs:
After init, run bluetemberg install to download the packs listed in llm/packages.json into the local cache (.bluetemberg/packs/); sync merges them with your local llm/ content.
Use bluetemberg install --dry-run to preview what would be installed without writing anything to disk.
Detail: docs/wiki/Registry.md and docs/wiki/Profiles.md.
bluetemberg init records the selected team profile under profile in bluetemberg.config.json. To change profile later without re-running the full init wizard:
npx bluetemberg switch-profile backend
The command is non-destructive:
llm/packages.json if missing.llm/ files.profile in bluetemberg.config.json.Run bluetemberg install and npx bluetemberg sync afterwards to download new packs and regenerate platform files.
After init you can manage packs directly without touching llm/packages.json by hand:
npx bluetemberg install # download all packs listed in llm/packages.json
npx bluetemberg update # update all packs to latest matching semver range
npx bluetemberg update bluetemberg-rules-nextjs # update a single pack
npx bluetemberg add bluetemberg-rules-nextjs # add a new pack
npx bluetemberg remove bluetemberg-rules-nextjs # remove a pack
npx bluetemberg list # show installed packs and resolved versions
Run bluetemberg sync after any change to regenerate platform files. See Registry for the manifest format, lockfile, and pack cache layout.
Packs can also come from a private registry — a private scope on npmjs.org, GitHub Packages, Verdaccio, Artifactory. Credentials are read from .npmrc or NPM_TOKEN/NODE_AUTH_TOKEN exactly as npm reads them, and are only ever sent to the host they are scoped to, over https. Registries that do not sign need an explicit opt-in:
NODE_AUTH_TOKEN=... npx bluetemberg install --skip-signature-verification
Signature verification stays mandatory for registry.npmjs.org. See Private registries.
A second routing axis orthogonal to profiles (role): stacks answer what you build with. Tag a rule or guardrail with a version range and sync delivers it only where it's correct — a Payload-2 rule never reaches a Payload-3 repo.
# llm/rules/payload-rsc-admin.md frontmatter
stacks:
payload: '>=3 <4'
// bluetemberg.config.json — declare or pin the project's stacks
{ "stacks": { "payload": "3.4.1", "nextjs": "auto" } }
sync detects the project's stacks (declared version → node_modules → lockfile → coerced package.json range), then hard-excludes rules, guardrails, agents, and skills whose range the detected version doesn't satisfy — listing what it filtered so you can audit it. Content with no stacks: is stack-agnostic and always applies, so projects that declare no stacks behave exactly as before.
Inspect detection and coverage — these have a --json twin for agents:
npx bluetemberg detect # detected stacks, versions, confidence, gaps
npx bluetemberg coverage payload@3 # is there version-correct guidance for this stack?
Or expose the same model to an agent as MCP tools (bluetemberg_detect_stacks, bluetemberg_query_coverage, bluetemberg_list_stacks, bluetemberg_org_histogram) — read-only, over stdio:
npx bluetemberg mcp serve
Maintainers can scan several repos at once to see which (stack, version) eras are worth authoring rules for — a read-only usage histogram ranked by coverage gaps. Scan local clones, or read manifests straight from a GitHub org over the API (no cloning) with a GITHUB_TOKEN/GH_TOKEN in your environment:
npx bluetemberg scan-org ../app-a ../app-b # local clones
npx bluetemberg scan-org --org acme --json # every repo in the acme org
npx bluetemberg scan-org --repos acme/app,acme/web # specific repos
See Configuration, Writing Rules, and Commands for the full model.
After editing anything in llm/, regenerate platform files:
npx bluetemberg sync
Check mode for CI (exits 1 if out of sync):
npx bluetemberg sync --check
Add --diff to see what drifted, not just how many files — a per-file unified diff (summary counts + @@ hunks) under each out-of-sync path. It implies --check, honors --silent, and never changes counts or the exit code:
npx bluetemberg sync --check --diff
Exit codes: the CLI exits 1 if sync records any error (invalid llm/hooks.json, unknown MCP id, adapter failure, etc.), not only when --check finds drift. Use the exit code in CI, especially with --silent.
--check also reports generated files that no source produces any more (a deleted or renamed rule, or one a stack change filtered out) as STALE:, so CI never stays green over output the tools are still loading. Remove them with --prune:
npx bluetemberg sync --prune
--prune deletes only files that carry the generated-file banner. A hand-written file in a managed directory, or a JSON output (which can't carry a banner), is kept and listed; a dropped marketplace plugin whose files all carry the banner is removed whole. --prune is ignored with --check. See the wiki (Commands, Configuration) for exit codes, .gitattributes, and prune caveats.
Pull rules from outside the npm pack registry — e.g. a community GitHub repo of .cursorrules/.mdc files — and Bluetemberg translates them into native frontmatter, caches them, and includes them on sync:
npx bluetemberg source add "github:PatrickJS/awesome-cursorrules#HEAD:rules"
npx bluetemberg sync
Sources are pinned in llm/rule-sources.json + llm/rule-sources-lock.json (commit both; run bluetemberg source install on a fresh clone) and are the lowest priority during sync, so your local rules always win. GitHub repos, PRPM packages, and cursor.directory plugins are all supported backends. See Sources.
¹ Gemini CLI has no native rules API — rules are emitted as plain context files under .gemini/context/ and prepended to the model context on each request. Agents and skills are not supported by the Gemini CLI extension at this time.
² Codex has no per-file rule API — rules are folded into a managed block in AGENTS.md, which Codex reads natively. Only Codex gets that block. Every other platform receives scoped rules through its own directory, and most of them also read AGENTS.md, so folding rules in for them would load each rule twice. Agents become per-file TOML under .codex/agents/, and skills go to the vendor-neutral .agents/skills/. See the Codex mapping below.
¹ Claude Code plugins have no native "rules" component, so the marketplace emitter converts each
rule into a rule-{id} skill — see Marketplace.
Rules get platform-specific frontmatter transforms:
scope: '**' -> alwaysApply: true; otherwise globs: [scope]paths: [scope]applyTo: scopeglob: scopescope: '**' -> trigger: always_on; otherwise trigger: glob, glob: scopeAGENTS.md (see below)Agents and skills keep their body unchanged. Sync adds the generated-file banner, changes the filename extension, and for Claude Code maps the abstract tools names in agent frontmatter to Claude's tool names.
Claude Code and AGENTS.md: Claude Code reads AGENTS.md natively (v2.1.277+), but only when there is no CLAUDE.md. Once a CLAUDE.md exists, AGENTS.md is ignored unless the CLAUDE.md imports it. That is why the scaffolded CLAUDE.md starts with @AGENTS.md, the pattern Anthropic recommends. sync warns when a root CLAUDE.md, .claude/CLAUDE.md, or CLAUDE.local.md would hide AGENTS.md this way. See Architecture.
OpenAI Codex consumes config differently from the table above — it reads AGENTS.md natively and uses TOML config rather than per-file rule directories:
AGENTS.md and .codex/config.toml are edited in place via fenced managed blocks, so hand-authored content outside the markers is preserved. When Copilot or Gemini are also enabled, the Codex rules block is stripped from their derived copilot-instructions.md / GEMINI.md (they receive scoped rules through their own directories). Codex subagents are limited to name, description, and developer_instructions; source-only fields like tools and profiles are not mapped.
Monorepo and shared rule packs: Add an extends field to bluetemberg.config.json to merge rules/agents/skills from additional source directories — relative paths (e.g. "../../" for the monorepo root) or npm package names (e.g. "@company/ai-rules"). Local files always take priority. See Configuration for details.
Programmatic API: import { sync, loadConfig, shouldExitWithFailure } from 'bluetemberg'. sync() returns a Promise (it may load optional adapters). Always await it, e.g. const results = await sync(root, { config: loadConfig(root), prune: true });. Use shouldExitWithFailure(results, checkMode) to mirror CLI exit semantics. Release notes for each version live in CHANGELOG.md (updated by Release Please). Breaking changes should use conventional commits—see Contributing — Changelog and breaking changes.
Add "claude-marketplace" to platforms and define plugins in bluetemberg.config.json to emit installable Claude Code plugin bundles:
{
"platforms": ["claude", "claude-marketplace"],
"marketplace": {
"remote": "your-org/claude-marketplace",
"plugins": [
{ "name": "frontend", "displayName": "Frontend Developer", "profiles": ["frontend"] },
{
"name": "fullstack",
"displayName": "Full-Stack Developer",
"profiles": ["frontend", "backend", "fullstack"]
},
{ "name": "backend", "displayName": "Backend Developer", "profiles": ["backend"] },
{ "name": "devops", "displayName": "DevOps Engineer", "profiles": ["devops", "pure-infra"] }
]
}
}
Each plugin bundles only the skills and agents whose profiles frontmatter (or preset tags) overlap with the plugin's profiles list. Skills and agents with no profile are included everywhere.
When remote is set, bluetemberg sync writes extraKnownMarketplaces to .claude/settings.json — Claude Code then auto-prompts teammates to install the relevant plugin when they open the project. Teammates need no local bluetemberg install.
See docs/wiki/Marketplace.md for the full setup guide.
See the Wiki for full documentation:
git clone https://github.com/prototypdigital/bluetemberg.git
cd bluetemberg
npm install
npm run build
npm test
The checked-in CLI invokes dist/ (init, catalogs, --help --json): keep npm run build up to date locally.
See Contributing for commit conventions and release process.
Bluetemberg is written and maintained by Josip Ravas — DevOps & Architecture Lead at PROTOTYP.
Issues and pull requests welcome. For anything security-related, see SECURITY.md.
AI coding standards shipped like a dependency — version-locked, integrity-verified, signed, and routed by role and stack version. Emits AGENTS.md plus native config for Cursor, Claude Code, GitHub Cop
{ "mcpServers": { "bluetemberg": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}ओवरव्यू
AI coding standards shipped like a dependency — version-locked, integrity-verified, signed, and routed by role and stack version. Emits AGENTS.md plus native config for Cursor, Claude Code, GitHub Copilot, Gemini CLI (Enterprise), Antigravity CLI, Devin D
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Bluetemberg stdio पर लोकल चलता है।
पिछली जाँच 2026-11-17 को हुई। AI coding standards shipped like a dependency — version-locked, integrity-verified, signed, and routed by role and stack version. Emits AGENTS.md plus native config for Cursor, Claude Code, GitHub Copilot, Gemini CLI (Enterprise), Antigravity CLI, Devin D