Single Source of Truth

chainhub.one — One Chain Hub to sync them all. (No magic ring required — just symlinks.)

Your AI assistants,
finally in sync.

Chain Hub ships a small, curated core — skills, workflows, rules, and agents to get you started. You then grow your own library: scaffold skills, author rules, add workflows, and pull extras from GitHub so every assistant reflects your stack, language, and way of working.

Broad editor support
Core + your skills
CLI: new, add, validate
Self-healing symlinks
Open format
The problem

One machine.
Five configs.

Every AI editor has its own convention for storing rules and instructions. You maintain the same content in five places and they drift apart the moment you update one.

01
Cursor reads rules from .cursor/rules/ in its own Markdown format.
02
Claude Code looks in ~/.claude/ for skills and CLAUDE.md files.
03
Windsurf, Gemini CLI, Trae, Kiro, Mistral Vibe — each with entirely different paths and expectations.
04
The result: stale duplicates everywhere. Your best skills live in one editor only.
How it works

Write once.
Run everywhere.

Chain Hub maintains one canonical directory for all your AI knowledge, then symlinks it precisely into every editor — simultaneously.

01
Install Chain Hub
Install the published npm package globally so the chain command is available in your shell. To upgrade later, run the same install again, then chain init to refresh bundled core (see docs).
$ npm install -g chain-hub
02
Initialize your hub
Run chain init to install the protected core/ into your CHAIN_HOME.
$ chain init
03
Run setup and sync
Run chain setup once to detect installed IDEs and create symlinks. Then maintain your playbooks in skills/, workflows/, and rules/.
$ chain setup
Supported editors

Works where
you work.

Targets the environments people use most. chain setup only links editors it detects on your machine — you grow skills and rules in the hub; the CLI wires them through.

Content model

Skills,
workflows
& rules.

Chain Hub organizes AI knowledge into three first-class types. The bundled core gives you a working baseline; everything beyond that is yours to define — so your library stays aligned with how you actually build.

Skills are invocable playbooks you add with chain new or install from registries and GitHub. Workflows are step-by-step procedures you maintain under your hub. Rules are always-on editor conventions — global or per project. Agents and registry metadata live beside them. Together they form a portable system that scales from solo defaults to a fully custom playbook.

Skills
Core starter + unlimited yours
A few protected core skills ship with the hub; you scaffold the rest with the CLI and tune triggers, sections, and quality gates so assistants pull in exactly your playbooks.
Workflows
You author the flow
Core includes example workflows; you add your own markdown procedures for how your team specs, debugs, ships, or reviews — one source of truth, linked everywhere.
Rules
Shape every session
Bundled global rules get you consistent defaults; extend or replace them with your own Markdown rules so tone, stack, and boundaries match your projects.
CLI reference

Everything from
one command.

The chain CLI handles the full lifecycle — from initial setup to publishing new skills.

$ chain setup
Detect all installed IDEs and create or repair symlinks from your hub into each editor.
$ chain validate
Lint all skill frontmatter and structure. Run before every commit — also enforced as a pre-commit hook.
$ chain list
Show all active skills with their source, type, and sync status across editors.
$ chain new <slug>
Scaffold a new skill from the canonical template with correct frontmatter pre-filled.
$ chain add github:…
Install a skill directly from any GitHub repository. Pulled into your hub and linked instantly.
$ chain reflect
Analyze recent session logs and surface patterns worth encoding as permanent skills or rules.
Quick start

Up in
three steps.

Clone, initialize core, link editors. Then invest in your skills and rules — the bundled set is a launch pad, not the ceiling. Chain Hub still finds each editor's paths on its own.

Self-healing — broken symlinks are automatically repaired on the next chain setup.
Compiled binary — the CLI builds to a native Bun binary. No runtime required in production.
Validated on commit — the pre-commit hook runs chain validate and blocks broken skills automatically.
Extensible — bring any skill from GitHub with chain add github:owner/repo.
Flexible hub path — default is ~/chain-hub, or persist your own path with chain config set chain_home <path>.
bash
# 0. Overview: https://www.chainhub.one/
# 1. Install Chain Hub globally
$ npm install -g chain-hub

# 2. Initialize your hub
$ chain init

# 3. Sync all your AI editors in one shot
$ chain setup

# Optional: persist a custom hub location
$ chain config set chain_home ~/my-chain-home

# ✓ Claude Code → ~/.claude/skills # ✓ Cursor → ~/.cursor/rules # ✓ Windsurf → ~/.codeium/windsurf # ✓ Gemini CLI → ~/.gemini/skills # ✓ Kiro → ~/.kiro/skills # ✓ Trae → ~/.trae/skills # ✓ Mistral Vibe → ~/.vibe/skills
# Example: detected IDEs linked. Then extend skills/, workflows/, rules/.