apex-accelerator: Instructions file for GitHub Copilot

SKU Manifest Authoring Rules

agent-output/{project}/sku-manifest.{json,md} is the single source of truth for creative SKU decisions across environments and regions. The JSON is canonical; the markdown is a rendering for human review.

Schema: tools/schemas/sku-manifest.schema.json Validators: npm run validate:sku-manifest + npm run validate:sku-iac-coverage Templates: .github/skills/azure-artifacts/templates/sku-manifest.template.{md,json}

Scope — what belongs in services[]

In scope (creative SKU decisions only):

• App Service Plans / Web Apps / Function Apps
• Virtual Machines / VM Scale Sets (VMSS)
• SQL Database / Managed Instance
• Cosmos DB accounts and containers (where throughput is a SKU)
• AKS node pools (per-pool VM SKU)
• Redis Cache
• API Management
• Application Gateway
• Storage Account replication tier (LRS/ZRS/GRS/RA-GRS)

Out of scope — never add to services[] (the explicit exclude list):

• Bandwidth / egress
• Log Analytics workspaces
• Virtual networks, subnets, NSGs, route tables
• Public IP addresses
• Diagnostic settings
• Resource groups, management groups, subscriptions
• Action Groups, Budgets, Policy assignments

These remain documented in 02-architecture-assessment.md prose or in the implementation plan narrative. The coverage validator (validate:sku-iac-coverage) treats SKU literals in these resource categories as legitimate non-manifest entries.

Revision Rules

revisions[] is append-only metadata about git commits / apex-recall checkpoints — not a free-form changelog.

• rev starts at 1 and increases monotonically.
• current_revision always equals the max revisions[].rev.
• Each service's last_modified_rev must reference an existing revision.
• commit_sha is stamped post-commit by tools/scripts/stamp-sku-manifest-commit.mjs (wired via lefthook.yml post-commit).
• apex_recall_checkpoint is set by the writer before commit. Pattern: {project}:{step}:{sub_step}.

Source Provenance