onboarding

Create developer onboarding documentation by standardizing project setup, environment configuration, and daily workflows. You need to include explicit prerequisites, repository cloning steps, local run instructions, testing commands, and architecture references to ensure reproducibility for .NET teams.

Developer environment setup guidelines should include clear prerequisites and version requirements for .NET, Docker, and CLI tools. They must also provide step-by-step repository cloning instructions, commands to run services locally, and procedures to execute unit and integration tests.

Yes, this onboarding documentation approach supports .NET architectures using CQRS and event sourcing. It generates a high-level architecture overview that explains key concepts and outlines the daily development workflow for adding features and creating pull requests.

The best way to standardize repository setup instructions is to centralize cloning steps, local dependency startup, and testing commands in a project-specific guide. This ensures new contributors become productive quickly by following reproducible configuration and workflow processes.

Link Architecture Decision Records in developer quickstart instructions by generating an onboarding guide that references architecture docs and ADRs. This provides developers with direct access to design rationale and architectural context alongside setup commands.