Optional starter configuration for common API tooling #114
Description
Problem
The starter is intentionally minimal, but real-world API projects usually require adding common setup (e.g., documentation, typed validation, middleware structure) right after project creation.
This leads to repetitive manual configuration and inconsistent project structure.
Proposed solution
Provide an optional starter variant or configuration that includes common API tooling while keeping the default starter minimal and unchanged.
Example use case
Developers often add automatic API documentation, typed request/response validation, and reusable middleware immediately after setup.
An official optional pattern would remove repeated manual work.
Why this fits the philosophy
- Keeps default starter minimal
- Fully optional and opt-in
- Improves developer experience
- Reduces duplicate setup