AIX helps teams install, lock, review, update, and remove project-local AI-agent assets with the same discipline they already use for code dependencies.
Useful review skills, planning workflows, and bootstrap processes should be shared, versioned, reviewed, and tied to the repo where agents actually run.
Install a project operating model into .agents, insert a managed AGENTS.md block, and activate the workflow-owned skills that support it.
Add Git-backed skill sources, list what they expose, activate selected skills, and use aliases when sources publish the same names.
Commit aix.json and aix.lock.json so every teammate gets the same workflow, sources, active skills, and installed file hashes.
Start with aix init to install the bundled design-plan-execute workflow and write project manifest files.
Check the installed state and verify managed files before asking agents to rely on the workflow.
Add a Git skill source, list available skills, and activate the skill paths the project needs.
Review diffs before moving the lockfile forward, keeping agent behavior intentional and auditable.
The bundled workflow installs process docs, engineering guidance, workflow-owned skills, and a managed AGENTS.md entry that points agents to the right place.
Read More
AIX keeps source collections, package copies, and active skill names separate so teams can share capabilities without creating private piles of pasted prompts.
Projects declare trusted sources and active skills in aix.json while aix.lock.json records the exact installed state, resolved commits, hashes, and aliases.
The npm package is prepared for the @tekfoundry/aix scope. Until that scoped package is published, install the packed build from the GitHub release.