chainhub.one — One Chain Hub to sync them all. (No magic ring required — just symlinks.)
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.
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.
.cursor/rules/ in its own Markdown format.
~/.claude/ for skills and CLAUDE.md files.
Chain Hub maintains one canonical directory for all your AI knowledge, then symlinks it precisely into every editor — simultaneously.
chain command is available in your shell.
To upgrade later, run the same install again, then
chain init to refresh bundled core (see
docs).
chain init to install the protected
core/ into your CHAIN_HOME.
chain setup once to detect installed IDEs and create symlinks.
Then maintain your playbooks in skills/,
workflows/, and rules/.
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.
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.
The chain CLI handles the full lifecycle — from initial setup to publishing new skills.
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.
chain setup.
chain validate and blocks broken skills automatically.
chain add github:owner/repo.
~/chain-hub, or persist your own path with chain config set chain_home <path>.