AkiClaudeDoc

One-command install, full baseline

A single curl command turns a fresh Claude Code 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.

A rule corpus that routes itself by naming

A strict naming convention: RULE-*.md are constraints (what Claude must or must not do — behavior, coding, docs, content, stack, SEO, release, DB design); 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 Claude to Read the file from ~/.aki/claudedoc/ when signals match.

Five skills, each sharp at one job

akirule (automatic rule router), 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.