Loading…
Loading…
Documentation fails in predictable ways: it describes the happy path and stops, it repeats what the code already says, it was accurate eighteen months ago, and it is written for the person who built the thing rather than the person meeting it. These prompts are written against those failures. They ask for the reader's actual starting state, insist on working examples over descriptions, require the limitations section to be honest, and in the audit prompts they hunt for the sentence that quietly stopped being true. Use them on a page you are about to publish, or on one you inherited and do not trust.
36 prompts in 5 groups
READMEs, setup guides, onboarding and glossaries for the person meeting this for the first time.
The lookup layer: function docs, config options, error codes and examples worth copying.
Changelogs, migration guides and decision records that explain what changed and why.
What to do at 3am, the failures that keep arriving, and the limits nobody wrote down.
Finding what is stale or undocumented, cutting what the code already says, rewriting for the reader.
Send a prompt you keep coming back to. A person reads every one.
Suggest a prompt