AI management
Compose the ASO playbook your assistant works from: fifty blocks of method, your own measurements, API access and your house rules.
Everything the panel measures ends up on a screen a person reads. This is the screen that writes it out instead - one Markdown file you compose from fifty blocks and hand to Claude, Cursor or any assistant, so it can work from what has actually been measured rather than from a description of it.
Four kinds of block
Every section in the file is labelled with where it came from, because an agent will act on all four and only one of them is a fact about the store.
| Label | What it is |
|---|---|
| METHOD | Doctrine - how the discipline works. Thirty blocks: the cusp band, the three fields Apple indexes, how to read popularity and difficulty, choosing a niche, sequencing markets, the launch checklist, running a portfolio, attribution, and the ways rank data lies. |
| MEASURED | Read off your app and storefront: the cusp band, the opportunity band, the metadata audit, the storefront scores, the rivals, the unmet needs. |
| ACCESS | How the assistant reaches the API itself - MCP, the nine tools, REST and the CLI - so it can check a claim rather than take it. |
| MODEL | Written by a language model from the sections you chose above it: what earns first, a thirty-day plan, where the next app should go. It is given those sections and nothing else. |
Why the file is always English
The panel reads in your language and the document does not. It is read by a model far more often than by a person, models follow English instructions more reliably, and a file whose rules arrive in one language and whose tables arrive in another is one an agent reads inconsistently. The block library is translated - choosing is the part you do.
Your own blocks
The library ships fifty and they are all about the discipline or about the account. An agency has a third kind: house rules, a client's tone of voice, a category it never touches, a checklist that cost money to learn. Write those as blocks and they sit in the file beside the doctrine, verbatim - nothing summarises or rewrites them.
Embedding an API key
A brief with a key in it lets the assistant measure for itself rather than only read what was measured. The key is created at the moment you copy or download - nothing can hand back the secret of a key that already exists - and it is a service key, because a device key belongs to one machine. The file says on its first page that it carries a live credential, and the key appears on the Account screen so it can be revoked there.
Using it
- 1Pick the blocks. Search the library, tick what you need; the document builds as you go.
- 2Drag them into the order you want the assistant to read them in.
- 3Run the model blocks if you want the judgement as well - they are the only ones that cost anything.
- 4Copy or download, and paste the file into your assistant as its first message.