Documentation prompts

Handler code, routes, and models:
"""
[PASTE THE ROUTE DEFINITIONS, HANDLERS, REQUEST AND RESPONSE TYPES, VALIDATION SCHEMAS, AND MIDDLEWARE]
"""

Generate an OpenAPI 3.1 specification from the code above.

API name, version, and base URL: [DETAILS]
Auth scheme: [BEARER JWT / API KEY / OAUTH / SESSION COOKIE, and where it is enforced]
Con

Write a README for this project.

Audience: [WHO LANDS HERE: e.g. "developers evaluating whether to use this library" / "new team members" / "users installing the CLI"]
Project code (or explore the repo if you're an agent):
"""
[PASTE package.json/pyproject.toml, entry points, main modules, CLI/arg definitions]
"""

Rules before structure

Give me a guided tour of this codebase. I'm [NEW TO THE TEAM / EVALUATING THIS PROJECT / INHERITING THIS CODE], and my first real task will be: [THE TASK, e.g. "add a field to the billing flow", or "unknown, general orientation"].

[IF AGENT: explore the repo yourself, start with the manifest, entry points, and folder structure. IF CHAT: 

Write a blameless postmortem from my raw incident material.

Raw material (Slack threads, alerts, PR links, notes: messy is fine):
"""
[PASTE EVERYTHING: when things fired, who did what, what was tried, what worked]
"""
Impact facts: [DURATION / USERS OR CUSTOMERS AFFECTED / REVENUE OR SLA IMPACT / DATA LOSS Y/N: what's known]
The system: