Intelligence

Intelligence

**Build, version and distribute AI coding intelligence from one project source.**

Intelligence keeps rules, agents and skills in tool-neutral Markdown, installs shared content as versioned packages, and renders each enabled AI tool's native files. One CLI owns the manifest, lockfile, package store and sync engine.

Intelligence is currently a release candidate. Use the `next` npm tag until a stable release is announced.

Quick start

Requirements: Node.js 18+, Git, Bash and awk. On Windows, use Git Bash or WSL.

npm install -g @ainova-systems/intelligence@next

cd your-project
intelligence init --targets claude,codex

`init` is the universal project entry point:

• with no Intelligence setup, it creates intelligence.yaml, the lockfile and the initial package store;
• in a legacy Intelligence Sync project, it previews conversion and asks before applying it;
• in an Intelligence project, it aligns the schema and engine-content package with the installed CLI.

Use `intelligence init --preview` to inspect without writing and `intelligence init --apply` for explicit non-interactive application.

After the first successful sync, ask your agent to run `/intelligence-learn-from-repository`. It inspects the repository and proposes the smallest useful set of project-owned rules, agents and skills. Analysis is read-only; each proposed change requires approval.

Create project-owned content only when you need it:

intelligence/
├── rules/
│   └── context.md
├── agents/
│   └── backend-developer.md
└── skills/
    └── backend-add-endpoint/
        └── SKILL.md

Then render every enabled adapter:

intelligence sync

After a fresh clone, the same command restores a missing `.intelligence/` package store strictly from the committed lockfile before rendering.

What it solves

• Author shared context once instead of maintaining separate copies for Claude Code, Cursor, GitHub Copilot, Codex, Pi and OpenCode.
• Preserve nat