AkiDevRule

One-command install, full baseline

A single npx @akinet/akidevrule@latest command turns a fresh Claude Code or Antigravity environment into Aki’s full working baseline. You can also run node install.mjs from a local checkout (Node 18+). 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, test); METHOD-*.md are analytical frameworks, heavy, loaded only when the task genuinely needs them; since 3.6.0 there is no index.md manifest, the akirule router is the single place that lists the routes.

Meaning-based routing, with a gate

Only two files are resident, loaded every session via @-import in CLAUDE.md: RULE-agent-behavior.md and the akirule router. Every other rule is routed by the meaning of the task (the domains it touches and the act: create, decide, audit, ship) in any language, so a paraphrase routes as well as the listed word. On Claude Code the aki-route-guard PreToolUse hook guarantees the Read: the first Edit/Write of each artifact type (code, .md, CHANGELOG.md, .vue/.css, .rs, .sql, locales/, test files) is denied until the matching rule has been read since the last context compaction. It fails open on any error and AKI_ROUTE_GUARD=0 disables it. A turn that only reads, counts or explains loads nothing extra.

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.

Eleven 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), akiopen (a session-opening brief that reports only what is still pending, at most seven items, read-only).

One brain, three thinking modes

METHOD-deep-think.md is a single analytical brain (goal excavation, first principles, mandatory critique, conditional techbiz lens) consumed three 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; Triggered self-run (new in 3.1.0) — fires non-interactively on any of agent.A3's six mandatory conditions (about to ask/escalate, a one-way-door action, conflicting rules, …), depth scaled to difficulty, ending in decide-and-report or escalation; 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 (npx @akinet/akidevrule@latest or git pull && node install.mjs). It never downloads or installs anything on its own.