菜单
Best practices for Azure DevOps Pipeline YAML files in the Enigmatry Entry Blueprint project. Use this when creating, editing, or reviewing Azure DevOps CI/CD pipeline YAML.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Best practices for Angular unit testing with Jest in the blueprint frontend. Use this when writing or reviewing Angular/TypeScript spec files.
Enigmatry Entry Blueprint .NET 9 Web API patterns covering MediatR, Autofac, FluentValidation, and vertical slice architecture. Use this when adding or modifying .NET API features, handlers, validators, or controllers.
Enigmatry Entry Blueprint code review checklist covering .NET 9 and Angular/TypeScript. Use this when reviewing or performing a code review on blueprint changes.
C# 13 coding standards for the YOS project — naming, formatting, nullability, and testing conventions. Use this when writing, reviewing, or refactoring any C# (.cs) file.
Best practices for C# unit and integration testing with NUnit, FluentAssertions and NSubstitute. Use this when writing or reviewing C# tests.
TypeScript 5.x / ES2022 coding standards for the YOS Angular project — naming, formatting, type system, async patterns, and architecture conventions. Use this when writing, reviewing, or refactoring any TypeScript (.ts) file.
| name | azure-devops-pipelines |
| description | Best practices for Azure DevOps Pipeline YAML files in the Enigmatry Entry Blueprint project. Use this when creating, editing, or reviewing Azure DevOps CI/CD pipeline YAML. |
All pipeline YAML lives in Pipelines/:
| File | Purpose |
|---|---|
azure-pipelines.yml | Main CI/CD pipeline — build → deploy |
run-all-tests.yml | Runs all test suites |
code-analysis.yml | Static analysis |
build-publish-nuget.yml | NuGet package publishing |
deploy-to-stage.yml | Reusable deployment job template |
variables/ | Per-environment variable files |
Shared pipeline templates are consumed from the enigmatry-azure-pipelines-templates repository via a resources.repositories reference — do not inline template logic that already exists there.
variables:
artifactName: 'enigmatry-entry-blueprint-template'
dbContextName: 'AppDbContext'
nodeVersion: '22.17.1' # keep in sync with .github/workflows/copilot-setup-steps.yml
projectNameAngularApp: enigmatry-entry-blueprint-app
projectNamePrefix: Enigmatry.Entry.Blueprint
majorMinorVersion: 1.0
The build uses the shared build-angular-app-and-dotnet-api.yml template:
- template: build-angular-app-and-dotnet-api.yml@templates
parameters:
artifactName: $(artifactName)
nodeVersion: $(nodeVersion)
projectNameAngularApp: $(projectNameAngularApp)
projectNamePrefix: $(projectNamePrefix)
runAngularTests: true
useSlnx: true
dbContextNames:
- $(dbContextName)
Deployments use the deploy-to-stage.yml template and are gated on branch conditions:
- stage: Deploy_Test
dependsOn: ci_build
condition: and(succeeded(), eq(variables['Build.SourceBranch'], 'refs/heads/master'))
variables:
- template: variables/variables.test.yml
jobs:
- template: deploy-to-stage.yml
parameters:
environment: test
serviceConnection: 'Enigmatry - Entry Template (Test)'
variables/variables.<env>.yml files for environment-specific config — never inline environment values.nodeVersion in sync with package.json engines and copilot-setup-steps.yml.dbContext, add it to the dbContextNames list in the build template call.batch: true on triggers to avoid redundant builds for rapid pushes.