architecture-principles

Define architecture guardrails and decision criteria for design reviews.

7|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill architecture-principles-kentoshimizu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-principles
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/architecture-principles
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill architecture-principles-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Define architecture guardrails and decision criteria to prevent ambiguity during technology choices and design reviews.

Core Features & Use Cases

  • Principle catalog that translates business goals into concrete design constraints for monolith, microservices, serverless, or event-driven patterns.
  • Guardrail guidance with measurable checks, rationale, and escalation paths to resolve conflicts.
  • Delivery-ready governance artifacts, including review checklists and re-decision triggers.

Quick Start

Define architecture guardrails and decision criteria for your next design review.

Frequently Asked Questions about architecture-principles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are architecture guardrails and how do they guide system design?▼

Architecture guardrails are measurable criteria that translate business goals into concrete design constraints, preventing ambiguity during technology choices and design reviews across monolith, microservices, serverless, or event-driven patterns.

How do I define architecture principles for a design review?▼

Define architecture principles by establishing a catalog with explicit criteria, rationale, and trade-offs, then generate governance artifacts like review checklists and re-decision triggers to evaluate projects with varying maturity.

When do I need architecture decision criteria for choosing microservices or serverless?▼

You need architecture decision criteria when selecting monolith, microservices, serverless, or event-driven patterns, applying explicit guardrails at decision points to ensure technology choices align with business goals and project maturity.

Can I use these architecture guardrails for projects with varying maturity levels?▼

Yes, architecture guardrails apply to projects with varying maturity, as the decision criteria and review checklists provide scalable governance across different stages of system design and technology pattern adoption.

What is the best way to resolve conflicts during architecture governance reviews?▼

Resolve conflicts during architecture governance reviews by using guardrail guidance with measurable checks and defined escalation paths, ensuring decisions follow explicit criteria rather than subjective preferences.

Why do I need re-decision triggers in system design governance?▼

Re-decision triggers are needed in system design governance to signal when existing architecture decisions must be re-evaluated, ensuring guardrails and principles adapt to changing project maturity, business goals, or technology constraints.