Skip to content

ExpertGroup Development Guidance

Global coding standards, templates, and AI-assistant instructions for all ExpertGroup repositories (ExpertGroup core, ArtLift, Reporting, KIPS, Transfera, MCP.Minimax, Ametrics, and future projects).

Contents

Path Purpose
00-PLAN.md Master plan: scope, rollout, distribution, how Claude sessions consume this
standards/01-csharp-dotnet.md C# / .NET standards
standards/02-frontend-angular.md Angular standards
standards/03-frontend-react-nextjs.md React / Next.js standards (Transfera)
standards/04-api-graphql-rest.md GraphQL (HotChocolate/Apollo) + REST API design
standards/05-database-efcore-sql.md EF Core, migrations, SQL Server conventions
standards/06-git-workflow.md Branching, commits, PR policy
standards/07-testing.md Test strategy, naming, coverage
standards/08-security.md OWASP 2025, secrets, supply chain
standards/09-cicd-azure-pipelines.md Azure Pipelines YAML standards
standards/10-architecture.md ADRs, service boundaries, independent deployability
standards/11-resilience.md Timeouts, retries, circuit breakers, bulkheads
standards/12-observability.md OpenTelemetry tracing, wide events, health checks
adr/ADR-001-environment-branch-model.md First org-level ADR (branching deviation rationale)
REVIEW-expert-suggestions.md Scored review of 30 expert-derived additions (.html = wide view)
templates/CLAUDE.template.md Drop-in CLAUDE.md for every repo root
templates/.editorconfig Unified editorconfig (C# + TS)
templates/Directory.Build.props Shared MSBuild settings
templates/Directory.Packages.props Central Package Management starter
templates/PULL_REQUEST_TEMPLATE.md PR description + review checklist
templates/ADR-template.md Nygard-format ADR template
templates/azure-pipelines.template.yml Multi-stage pipeline skeleton

How to adopt in a repo (5 minutes)

  1. Copy templates/CLAUDE.template.md to the repo root as CLAUDE.md; fill in the repo-specific sections.
  2. Copy templates/.editorconfig, Directory.Build.props (and Directory.Packages.props for .NET solutions) to the repo root. Merge with existing files — do not blindly overwrite.
  3. Copy templates/PULL_REQUEST_TEMPLATE.md to .azuredevops/ (or .github/) in the repo.
  4. Commit. Every developer — and every new Claude session — picks it up automatically.

Maintaining

This folder is the single source of truth. Propose changes via PR to the repo that hosts it. Version and date every standard doc.