Parallax
Docs for humans and agents that always follow the code.
parallax, noun, uk /ˈpær.ə.læks/ us /ˈper.ə.læks/ the effect by which the position of an object seems to change when it is looked at from different positions
Cambridge Dictionary
Your repo, seen from two positions
The object is your project, and it is seen from two positions. One is your agent's, working in the code and changing more of it than you can read. The other is yours: your understanding of what is going on, the picture you supervise through. Left alone, the two drift apart.
The moment your expectations are not met, when you think "that's not how I imagined it", is worth inspecting. It might be a stale page, a real bug, a design flaw, or a misunderstanding. Parallax gives your repo docs that make those moments visible: a User Guide where you check the design and the reasons behind it, and an Agent Guide that helps agents find their way around.
The code is the oracle, docs follow, and neither implies correctness.
If the code is buggy, the docs describe the bug, and a strange behaviour written in plain words is easier to question.
Five skills
| setup | Run once. Builds the docs or ports yours, after showing you the plan. |
|---|---|
| sync | Runs by itself. When code changes, pages move to match it. |
| dive | A read-only diver asks whether what docs and code agree on looks like a bug. Also the whole-repo check. |
| gap | When your picture differs from the docs, it reads the code and names the cause. |
| ticket | Keeps a bug or idea for later, and asks first on public repos. |
Install
In Claude Code, then run setup in the repo you want to document:
/plugin install parallax --marketplace LuCazzola/parallax
/parallax:setup