Readme

Required Sections

• Title — Project name, one-line description, badges (CI, coverage, license, version).
• Overview — 2-3 sentences on what the project does and why it exists.
• Getting Started — Prerequisites, installation, and first-run instructions.
• Usage — Key commands, API examples, or configuration.

Optional Sections (include if relevant)

• Architecture — High-level diagram or description for larger projects.
• Configuration — Environment variables, config files.
• Development — How to set up a dev environment, run tests, lint, build.
• Deployment — How to deploy (if applicable).
• Contributing — Guidelines for contributors.
• License — License type and link.

4. If updating an existing README:
   • Preserve custom content the user has written.
   • Update auto-detectable sections (install steps, commands, env vars).
   • Flag sections that may be outdated.

Guidelines

• Write for a developer who has never seen the project before.
• Include copy-pasteable commands (with proper shell syntax).
• Use real values from the project, not placeholder text.
• Keep it concise — a README is a quick-start guide, not full documentation.
• Match the tone and style of the existing project documentation.