1. Confirm the target framework, SDK, and current app model.
2. Open [references/stack-selection.md](references/stack-selection.md) first for new apps or major refactors.
3. Open [references/program-and-pipeline.md](references/program-and-pipeline.md) next for `Program.cs`, DI, configuration, middleware, routing, logging, and static assets.
4. Open exactly one primary app-model reference:
[references/ui-blazor.md](references/ui-blazor.md)
[references/ui-razor-pages.md](references/ui-razor-pages.md)
[references/ui-mvc.md](references/ui-mvc.md)
[references/apis-minimal-and-controllers.md](references/apis-minimal-and-controllers.md)
5. Add cross-cutting references only as needed:
[references/data-state-and-services.md](references/data-state-and-services.md)
[references/security-and-identity.md](references/security-and-identity.md)
[references/realtime-grpc-and-background-work.md](references/realtime-grpc-and-background-work.md)
[references/testing-performance-and-operations.md](references/testing-performance-and-operations.md)
6. Open [references/versioning-and-upgrades.md](references/versioning-and-upgrades.md) before introducing new platform APIs into an older solution or when migrating between major versions.
7. Use [references/source-map.md](references/source-map.md) when you need the Microsoft Learn section that corresponds to a task not already covered by the focused references.