Documentation21 categories
Write the limitations bullets
Docs that describe the happy path and stop.
Write the limitations section this page is missing: hard limits with numbers, cases that work but perform badly, and anything the feature name implies but does not do. One bullet each, stating what happens rather than what is unsupported. Do not soften it. Docs or code:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Runbooks and support. What to do at 3am, the failures that keep arriving, and the limits nobody wrote down.
Related prompts
Write a runbook for someone woken at 3amAn alert exists and the only person who knows what to do is on holiday.Build a troubleshooting page from real failuresThe same three problems keep arriving in your support inbox.Make the docs honest about what this can't doDocs that read like marketing and leave users to discover the edges themselves.Turn a support thread into a docs pageYou just answered the same question for the fourth time in a ticket.Structure a README that gets someone runningA project with working code and a README that says only its name.Generate API reference from this codeA module whose public surface needs documenting properly, not just typed.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free