GitHub - nicolasakf/unity: Unity syncs your skills and rules across coding agents, ensuring continuity whenever you switch tools. · GitHub
/" data-turbo-transient="true" />
Skip to content
Search/
Sign in<br>Sign upAppearance settings
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
nicolasakf
unity
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Latest commit
History<br>64 Commits<br>64 Commits
Folders and files<br>NameNameLast commit message<br>Last commit date<br>assets
assets
docs
docs
src
src
test
test
.gitignore
.gitignore
CONTRIBUTING.md
CONTRIBUTING.md
LICENSE
LICENSE
README.md
README.md
SECURITY.md
SECURITY.md
package-lock.json
package-lock.json
package.json
package.json
tsconfig.json
tsconfig.json
tsup.config.ts
tsup.config.ts
vitest.config.ts
vitest.config.ts
View all files
Repository files navigation
Unity
Unity keeps Agent Skills and agent rule files in one source-of-truth tree and mirrors them into the folders and files used by coding agents such as Codex, Orion, Claude Code, Cursor, OpenCode, etc.
Demo
Install Unity
npm install -g @nicolasakf/unity<br>unity --help
How it works
Unity has source directories for skills and rules:
Scope<br>Skills source<br>Rules source
User<br>~/.agents/skills<br>~/.agents/rules
Project<br>/.agents/skills<br>/.agents/rules
Unity uses these as the source of truth. You or your agent can edit skills and rules in the source directories or in supported agent mirror locations. Unity will guarantee that all linked targets are kept in sync at each scope level.
Quickstart
Initialize user-level Unity:
unity init
On first init , Unity prompts for two things:
Targets — enter the coding agent(s) you work with separated by commas, e.g codex, orion.
Projects (optional) — type each repository path you want to sync, e.g ~/projects/my-app.
Note for Coding Agents:
If you are an AI coding agent, use --non-interactive to disable interactive prompts.
unity init --non-interactive [--targets codex,orion] [--projects /abs/path/to/repo]
If the targets and/or projects were not specified by the user in their prompt, ask them. At least one target must be enabled. Projects are optional.
Start the watcher:
unity watch --pull
Use --pull so Unity watches enabled agent skill directories and rule files as well as each scope’s Unity source. When something changes, Unity pulls from those mirrors into the source and then pushes back out, so edits made inside an agent stay consolidated in the canonical tree. Without --pull , only the Unity source directories are watched: changes there still propagate outward on each run, but edits confined to an agent mirror are not noticed until you run unity pull or unity sync yourself.
For pull , push , sync , env push , project registration, watcher options, targets, diagnostics, import repair, and related CLI workflows, see the Full Setup Guide . Config files, built-in target paths, and sync state are described in Configuration .
About<br>Unity syncs your skills and rules across coding agents, ensuring continuity whenever you switch tools.<br>Resources<br>Readme<br>MIT license<br>Contributing<br>Contributing<br>Security policy<br>Security policy<br>Activity<br>Stars<br>4 stars<br>Watchers<br>0 watching<br>Forks<br>0 forks<br>Report repository
Releases
Packages
Contributors
Languages
You can’t perform that action at this time.