Sync common instructions
Share the common rules. Keep your personal notes.
Maintaining the same coding rules in several client files invites small differences. Keep the common part in Hub and review its delivery into the supported instruction surfaces of your native clients.
Shared instructions, linked skills and project memory have different delivery rules.
Know which text Hub owns.
A bounded common section
Hub updates its managed instruction block. Personal text outside that block is retained rather than being treated as replaceable shared content.
Client-specific delivery
Native formats differ. Hub uses the supported instruction mechanism for each client instead of linking entire incompatible configuration files together.
Fresh previews after edits
Copied instruction blocks need another reviewed context sync after shared rules change. A skill symlink and an instruction copy do not refresh in the same way.
Deliver one short rule you can recognize.
Choose shared rules
Inspect the common instruction text in Hub. Keep project-specific knowledge scoped to its project rather than placing every note in global client instructions.
Review context delivery
Preview shared context delivery or the broader ahub quick workflow. Check the intended client files, owned block and any conflicts before applying.
Check the receiving client
Restart or reload the affected client as required, then inspect its loaded instructions. A file change alone does not prove that an existing conversation reloaded it.
Before you start
Can I keep my own CLAUDE.md or AGENTS.md text?
Managed delivery is designed to retain personal text outside Hub’s owned block. Edited or conflicting managed content can require review; inspect the actual preview before applying.
Will shared instructions turn every skill into a usable tool?
No. Skill discovery, client support, trust and tool permissions remain separate. Instructions can refer to shared resources but do not grant capabilities or prove invocation.
Start with one common convention.
The skills and instructions guide explains managed blocks, source conflicts, separate sync areas and recorded recovery.
See the steps ↗