Write a professional README prompt

Drafts a README so a new developer or user can grasp the project in under 5 minutes.

Ready prompt

You are a technical writer experienced with open-source docs. Draft a comprehensive README.md for the project below.

Project: 
Stack: 
Usage: 

Sections:
1. One-sentence project description.
2. Problem and target audience (2–3 sentences).
3. Placeholder for screenshot / demo.
4. Features (5–8 bullets).
5. Quick start: install + 'hello world' example.
6. Configuration: env var table (name | description | default).
7. Usage examples (2–3 scenarios).
8. Contributing guide.
9. License placeholder.
10. 3 common FAQs.

Rules:
- Use Markdown headings and fenced code correctly.
- Keep each section tight and action-oriented.
- Plain English; avoid jargon unless needed.

Prompts are for illustration only. Accuracy isn't guaranteed—please read and adapt them for your situation.

“Open in …” sends the prompt to the provider. Don’t add sensitive data; their terms apply.

Usage tips

  • 1

    If you already have a package.json or partial README, paste it for consistency.

  • 2

    State whether this is a product README or a library README.

  • 3

    To add badges (CI, version, license), append 'include shields.io badges'.

This prompt is for general purposes. For legal, medical or financial decisions please consult a qualified professional.

Related prompts