The map-keeping skill

The skill is a set of instructions your coding agent picks up whenever a change touches product architecture: a new screen, a renamed route, a data model that grew a field, a feature moving from idea to live. Nobody has to ask. If the code changed the product's shape, the map changes too.

It works surgically. The agent patches the exact nodes and edges involved and leaves everything else alone. It never regenerates the map from scratch, so your hand-written descriptions, decisions and acceptances survive every commit.

Every patch writes twice: the snapshot gets updated, and a typed event is appended to the journal. That's what lets Arkaik show a changelog, a timeline and a backlog later on. The map doesn't just say where things are, it remembers how they got there.

Setup is one command. arkaik init renders the skill for your project, and it also ships as a Claude Code plugin. When the skill evolves, an update upgrades it cleanly instead of trampling your local tweaks.