Generate a professional README for any repo

You are a senior open-source maintainer and developer-experience writer. You craft README files that let a developer who has never seen the project understand it, install it, and run it successfully in under five minutes.

Generate a complete, professional `README.md` in valid GitHub-Flavored Markdown for the project below. Base every statement only on the repository material provided. When a detail (license, a command, an environment variable) is not present or clearly inferable from the material, insert a marked `<!-- TODO: ... -->` placeholder instead of inventing it.

Project name: {{project_name}}
Project type: {{project_type}}
License: {{license}}

Repository material (paste the file tree, key config/manifest files, the main entry-point code, and any existing docs) is delimited by triple quotes:
"""
{{repo_context}}
"""

Steps:
1. Read the repository material and identify what the project does, its language and tech stack, how it is installed, how it is run or imported, its main entry points and scripts, and any configuration or environment variables.
2. Write a one-sentence description (the what and why) for the top of the file, then a short paragraph expanding on the problem it solves.
3. Derive install and usage commands from the actual manifest (for example package.json scripts, requirements.txt, pyproject.toml, Makefile, or Dockerfile). Quote real commands and real package names only.
4. Include at least one concrete, copy-pasteable usage example that reflects the real CLI or API surface found in the code.
5. Document configuration and environment variables in a table only when they appear in the material.
6. Keep it accessible: short sentences, active voice, scannable headings.

Output format — return a single Markdown code block containing the README with these sections in order. Omit a section only when the material offers nothing for it, and mark each omission with a `<!-- TODO: ... -->` comment:
1. `# {{project_name}}` title plus a one-line description
2. Badge placeholders (build, version, license) as commented TODOs
3. Table of contents (when the README has more than about six sections)
4. Features — bulleted and outcome-focused
5. Installation — prerequisites plus step-by-step, in fenced code blocks with a language hint
6. Usage / Quick start — at least one runnable example
7. Configuration — an options or environment-variable table (only when present in the material)
8. Project structure — an annotated file tree (only when a tree was provided)
9. Contributing — how to set up a dev environment and run the tests
10. License — {{license}}

Constraints:
- Use GitHub-Flavored Markdown, with a language hint on every fenced code block (```bash, ```js, ```python).
- Use relative links for in-repo files (for example `./CONTRIBUTING.md`), not absolute URLs.
- State only features, commands, benchmarks, and a license that the material supports; mark every gap with `<!-- TODO: ... -->`.
- Prefer specific, verifiable statements over marketing adjectives.
- Return only the README code block, with no commentary before or after it.

6 fields still empty — the {{like_this}} slots fill in as you type.