First Steps

Do these once per project, after installing.

1. Build the code map

/quack:index

It writes documentation/INDEX.md: folder, file, purpose, and symbols with line ranges. From now on agents read the map before opening files, and Quack refreshes it at the start of every session. Commit it so your whole team shares it. See Code map.

2. Check your setup

/quack:checkup

It measures what is loaded into every message: memory files, skill descriptions, MCP servers, settings. It suggests fixes and applies only the ones you approve. See Checkup.

3. A ready prompt

Paste this inside your project to do both and get a plain explanation:

Use the quack:checkup skill on this project.
Show me what weighs on every message in a simple table: item, how much it weighs, what to do about it.
Suggest the fixes one at a time and apply only the ones I approve.
Then use the quack:index skill to build the code map.
At the end, explain in plain words what changed and how best to work from tomorrow.

A small test

Before installing, open the chat you have used for days and type /context: see how many tokens it carries. After installing, /clear and take your next task in a new chat. After a week, compare /usage with the week before.