Everyone teaches you to write prompts. In practice, a person looks at a sample a couple of pages long, with a stack, constraints, formats and edge cases, and closes the tab: there's no way I'll write that.
I needed a document camera: an Android phone on a tripod above the desk, a live preview in the PaperLedger browser page and a "Capture" button. Instead of a technical specification I told the agent: interview me, find out the stack, the architecture and the boundaries of the decisions.
An hour later there were 72 messages from me and 71 answers from the agent. Some of the questions were ones I would never have thought of myself: for example, what happens if the portal is open in several tabs at once. There was also a mistake by the agent: it questioned me at length about integration with PaperLedger before looking at its code.
I never wrote the final "prompt". It came together from the answers: the scenario, the boundaries, the contract between the phone and the portal. Then, on the "get started" command, the agent built the app, moved into the Python portal and connected both sides.
If a prompt feels out of reach, don't start with it. Ask the agent to ask you one question at a time and answer as you would. The decisions you would have made anyway end up written down.
The whole interview, without cuts, and what the agent did after it, are in the article: https://hram.github.io/en/articles/mobile-ledger/
Top comments (0)