Prompts for READMEs, API notes, runbooks and explanations that match the code or product you paste.
Documentation prompts that forbid inventing flags, endpoints or env vars you did not provide. The pack contains 30 reusable prompts written for Claude. After payment we send the Markdown file to the Telegram username you give at checkout, usually within 24 hours of payment confirmation. Example outputs on the product page are labelled illustrative unless we captured a real run. This is not a subscription and not professional advice.
Who it is for
Engineers and technical writers documenting systems they can inspect.
Includes “README from a file tree and purpose”, “Runbook from failure modes”, and “API notes from signatures”.
Example
Example input: A file tree, a paragraph of purpose, and two example error messages.
Expected output (illustrative): A README draft with setup, usage and a clearly marked “unknowns” section. Illustrative.
Illustrative example — not a captured run from your account.
Limitations
Documentation that does not match the running system will confuse users — always diff against reality.
30 prompts · Markdown file, delivered to your Telegram · Delivered to your Telegram
FAQ
How is the pack delivered?
We send the Markdown file to your Telegram username, usually within 24 hours of payment confirmation.
Which model is it for?
It is written for Claude. You can adapt prompts to similar models, with the limitations listed on this page.
Required so we can contact you about delivery. Use your @username.
Delivered to your Telegram — usually within 24 hours of payment confirmation.
Converted from GBP using a recent market rate. You always pay the server-quoted cryptocurrency amount.
Checkout creates a unique crypto quote. Your order moves to payment confirmed only after the exact amount arrives. We never mark work complete automatically.