Use this structure across repositories:
- Centered title + one-sentence purpose
- Badges that communicate repository type, status, primary stack, and license
- Documentation / Discussions / Issues links
PurposeBest foror repository-specific equivalentBaselineorStructureQuick startwhere applicable- Project contract or contribution rules
- License
status-active— actively maintained product/tooling repositorystatus-foundation— reusable runtime foundation
- Keep the README short and decision-oriented.
- Prefer 3-5 bullets per section.
- Keep framework detail in repository docs.
- Explain what the repository is, when to use it, and how to start.
- Do not duplicate architecture documentation in the README.