Quickstart
Get AIM governance running in under 5 minutes.
1. Install
npm install -g manifest-aim2. Generate a Manifest
Auto-detect your project’s languages, frameworks, and tooling:
manifest generateThis creates an aim.yaml with rules tailored to your stack. Or start from a template:
manifest init --template enterprise-typescript3. Validate
manifest validateChecks your manifest against the AIM v1.0 schema and reports any issues.
4. Inject into Your Agent
manifest wrap claude-codeThis generates a CLAUDE.md file with your governance rules, knowledge, and quality gates injected into the agent’s context.
Other platforms:
manifest wrap cursor # → .cursorrules
manifest wrap windsurf # → .windsurfrules
manifest wrap generic # → .aim/aim-context.md5. Enforce
After the agent produces output, verify compliance:
manifest enforce src/Output:
src/api/handler.ts
✗ BLOCK src/api/handler.ts:15:10
eval() is forbidden.
matched: eval(
⚠ WARN src/api/handler.ts:22:1
Remove console.log before production.
matched: console.log(
✗ 1 blocking violation
⚠ 1 warning6. Add to CI/CD
# .github/workflows/aim.yml
name: AIM Governance
on: [pull_request]
jobs:
enforce:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: RCOLKITT/Manifest-AIM/manifest-aim/action@main
with:
manifest: aim.yaml
target: src/Next Steps
- Writing Rules — Create custom governance rules
- Detection Modes — Pattern, tool, semantic, composite
- Manifest Gallery — Browse reference manifests
- Progressive Loading — Tier 0-3 capability system