AkiDevRule

One-command install, full baseline

A single curl command turns a fresh Claude Code or Antigravity environment into Aki’s full working baseline. You can also run bash install.sh from a local checkout. The script is intentionally simple so you can inspect it before running.

One source, two agents

The rule corpus is generated from a single agent-neutral source, shared by both Claude Code and Antigravity/Gemini — not two separate rule sets that can drift apart. The rename from AkiClaudeDoc to akidevrule (27/07/2026) marks exactly this scope widening.

A rule corpus that routes itself by naming

A strict naming convention: RULE-*.md are constraints (what the agent must or must not do — behavior, coding, docs, content, stack, UI, SEO, release, DB design, business); METHOD-*.md are analytical frameworks, heavy, loaded only when the task genuinely needs them; index.md holds the manifest, precedence order and project-binding policy.

Three-tier akirule router

akirule routes with deliberately high sensitivity (err toward loading): Tier 1 core loads every conversation (index.md, RULE-agent-behavior, RULE-coding) via @path embed syntax; Tier 2 contextual is read on signal match; Tier 3 is the analytical METHODs. No harness magic — Tiers 2–3 are just trigger instructions telling the agent to Read the file from ~/.aki/claudedoc/ when signals match.

akiflow — a sized multi-agent delivery pipeline

The newest skill: a strict sizing gate classifies a request into Tier 0 (direct, the default), Tier 1 (an Architect plan plus an adversarial Reviewer), or Tier 2 (adds business/UX counsel) — spawning only the specialists that tier needs, handing work between stages through docs/ files rather than chat context.

Six skills, each sharp at one job

akirule (automatic rule router), akiflow (a sized multi-agent delivery pipeline), akithink (a 5-phase deep-thinking session ending in a docs/ decision record), akihtmlreport (distills a dense in-conversation analysis into one self-contained REPORT.html), akihelp (a live intro to the installed Aki system, rendered at runtime so it never goes stale), akigitcommit (turns a messy working tree into a few clean Conventional Commits, stages by path, never git add -A or auto-pushes).

One brain, two thinking modes

METHOD-deep-think.md is a single analytical brain (goal excavation, first principles, mandatory critique, conditional techbiz lens) consumed two ways: Passive — akirule auto-loads it inline when a normal task hits a signal ("should we…", "is it worth…"), applied briefly, at most one clarifying question; Active — run /akithink to drive the same METHOD through a full 5-phase protocol at maximum depth.

Update notifications — notify-only

A SessionStart hook compares the installed CHANGELOG.md against the public repo copy (at most once per 24h, fail-silent, non-blocking). When the remote is newer it only prints what’s new and the manual update command (git pull && bash install.sh). It never downloads or installs anything on its own.