菜单
Define foundational architecture principles and decision-making rules. Communicate guidelines across organization. Use when establishing architectural standards or updating strategy.
Identify and avoid common architectural mistakes. Recognize patterns of failure. Use when reviewing designs or learning from mistakes.
Practice architectural design with structured problems. Time-limited design challenges. Use for skill development, interviews, team exercises.
Reference catalog of proven architecture patterns. Know when to apply each pattern, tradeoffs, and examples. Use as reference when designing systems.
Lead effective architecture reviews. Manage discussions, surface disagreements, build consensus, document decisions. Use when conducting reviews or running architecture forums.
Prepare for architecture interview questions and scenarios. Practice system design, tradeoff discussions, communication. Use for career development and interview readiness.
Conduct comprehensive system architecture evaluation. Assess design quality, technical debt, operational readiness, scalability. Use when auditing existing systems.
| name | architecture-principles |
| description | Define foundational architecture principles and decision-making rules. Communicate guidelines across organization. Use when establishing architectural standards or updating strategy. |
Establish foundational principles that guide architectural decisions and align organization.
You are defining architecture principles for the organization. Create clear, memorable guidelines that inform decisions. Involve stakeholders from product, engineering, and operations.
Based on architecture governance frameworks (TOGAF, Gartner):
Identify Core Values: What matters to the organization? Speed of innovation? Cost efficiency? Security? Reliability? List top 3-5.
Derive Principles: Turn values into principles. "Speed of innovation" → "Ship independently without central coordination". "Cost efficiency" → "Use managed services to reduce operational overhead".
Make Principles Memorable: Use simple language. "Move fast with confidence" better than "Implement robust CI/CD pipelines". Acronyms help: KISS (Keep It Simple, Stupid).
Create Decision Rules: For each principle, what are concrete decisions? "Cloud-first" → "Use EC2 not on-prem", "Use Lambda for new services", "Data in S3 not shared NFS".
Communicate and Enforce: Share with teams. Use in architecture reviews. Celebrate adherence; discuss exceptions constructively. Update as organization evolves.
