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, RULE-pattern-core) 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/akidevrule/ when signals match. That is also why the four core files were promoted to @-import: a rule that loads only when the model decides to call a skill is never a guarantee.

akiflow — a lead-coordinated agent council

The lead pins the owner’s verbatim words as the run’s immutable anchor, splits the request into work items that must each quote a fragment of it, then convenes seats from the five installed agent definitions — every seat traced to a requirement, never picked from a menu. Three modes are discriminated by a single question, what changes outside the room: discuss, audit (read-only), execute (only aki-maker may write). A gate script refuses to close the run on a missing anchor, a requirement quoting nothing the owner wrote, or a declared seat that never posted.

Ten skills, each sharp at one job

akirule (automatic rule router), akiflow (the agent council), akithink (a 5-phase deep-thinking session ending in a docs/ decision record), akihtmlreport (distills a dense analysis into one self-contained REPORT.html), akihelp (a live intro to the installed system, rendered at runtime so it never goes stale), akigitcommit (turns a messy tree into a few clean Conventional Commits, stages by path, never git add -A or auto-pushes), aki-article-writer (an article pipeline with its own image-scout subagent), akidevsync-notes (reads and edits the Aki Dev Sync task list), akilint (mechanical sweep for hard-wrapped lines and rambling comments), akiship (runs the full release ritual in one command, autonomous under the B8 contract, stopping only for public-history ambiguity or a design contradiction).

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.