architecture-principles
Architecture Principles
Overview
Use this skill to produce principle-level guardrails that help agents and humans make consistent architecture decisions. The output must be concrete enough to guide design reviews and implementation planning.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Inputs To Gather
- Business outcomes and failure impact.
- Quality priorities (latency, reliability, security, consistency, cost, delivery speed).
- Hard constraints (regulatory, legal, platform, security).
- Team ownership model and operational maturity.
Deliverables
- Principle catalog with rationale.
- Review guardrail checklist.
- Tradeoff policy for conflicting principles.
- Re-decision triggers when assumptions change.
Quality Standard
- Each principle states:
- Why it exists.
- What decision it constrains.
- How to verify pass/fail in review.
- Who approves exceptions.
- Hard constraints are separated from optimization preferences.
- Tradeoffs are explicit: what is intentionally worse and why.
- Re-decision triggers are observable and testable.
Workflow
- Convert business goals into ranked architecture drivers.
- Draft principles that constrain real decisions, not slogans.
- Add measurable review checks and exception handling.
- Resolve conflicts between principles with explicit priority rules.
- Publish the principle set and review cadence.
Failure Conditions
- Stop when priorities are contradictory or missing.
- Stop when principles cannot be evaluated objectively.
- Escalate when legal or security constraints conflict with product goals.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9