architecture-principles
Architecture Principles
Establish foundational principles that guide architectural decisions and align organization.
Context
You are defining architecture principles for the organization. Create clear, memorable guidelines that inform decisions. Involve stakeholders from product, engineering, and operations.
Domain Context
Based on architecture governance frameworks (TOGAF, Gartner):
- Guiding Principles: High-level philosophy (e.g., "Cloud-first", "Stateless services", "API-driven")
- Decision Rules: Specific rules derived from principles (e.g., "Use managed databases not self-hosted" from "Minimize operational burden")
- Trade-off Hierarchy: When principles conflict, which takes priority? Performance vs Cost? Consistency vs Availability?
- Exemptions: Clear process to override principles; document why and remediation plan
- Communication: Memorability matters; short, actionable, memorable
Instructions
More from sethdford/claude-skills
api-test-automation
Expert approach to api-test-automation in test automation. Use when working with .
2developer-experience-audit
Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
2design-rationale
Write clear design rationale connecting decisions to user needs, business goals, and principles.
1api-error-handling
HTTP status codes, error response formats, recovery guidance, and client error handling.
1interface-design
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
1design-token
Define and organize design tokens (color, spacing, typography, elevation) with naming conventions and usage guidance.
1