Development
π€ Generated with Claude Code
β οΈ Not yet reviewed
Co-Authored-By: Claude (noreply@anthropic.com)
How we work: standards, conventions and tooling that apply across repositories.
Contentsβ
| Document | Description |
|---|---|
| repository-conventions.md | Namespace prefixes and project types |
| git/ | Repositories, branches, commits and pull requests |
| secrets.md | Reading a secret in a service, local development, requesting a new one |
| api-services/ | API service development and project structure |
| ci-cd/ | Build and release pipelines in Azure DevOps |
| onboarding/ | Material for new joiners |
| brand-guide/ | Technical brand guide: colours, logos, D2 diagrams |
| templates/ | Templates for technical documentation |
| pdf/ | PDF generation from Markdown |
| docusaurus/ | Writing pages and components for the documentation site |
| ai-skills/ | Skill definitions for AI agents |
Writing Documentationβ
Where a document belongs, and how it is written, is defined in
DOCUMENTATION-GUIDELINES.md in the repository root. Read it before creating or moving
documentation β it is the authoritative source for both questions.
Relatedβ
Infrastructure topics β monitoring, secrets, servers, environments β live under Infrastructure.