architecture-governance

name	architecture-governance
description	Use when defining, reviewing, or verifying repository architecture contracts, ADR ownership, bounded-context boundaries, or architecture-check rollout policy.
allowed-tools	Read, Edit, Write, Glob, Grep, Bash
metadata	{"author":"profiletailors","version":"1.0"}

Architecture Governance Skill

Use this skill as the shared vocabulary for architecture decisions in the Profile Tailors monorepo. It owns the ARCH-001..005 contract matrix and routes implementation work to the language-specific backend and frontend skills. It does not replace executable enforcement or pretend that Kotlin, Vue/TypeScript, and Astro have identical boundary semantics.

When to Use

• Reviewing or proposing a change to a bounded-context or layer boundary.
• Mapping a new or existing architecture rule to an ADR and its executable owner.
• Deciding whether a violation is an approved exception, a warning, or a blocking failure.
• Planning a future just architecture-check gate.
• Choosing between ddd-architecture, hexagonal-architecture, and frontend architecture guidance.

Contract Matrix

The repository has exactly five shared architecture contracts. The ARCH identifier is the stable governance label; the ADR and executable test remain authoritative for the rule.