Skill UI

This framework provides a comprehensive, structured approach for making critical architectural decisions. It guides users through requirements analysis, detailed trade-off evaluation, and documenting decisions using Architecture Decision Records (ADRs). It is essential when analyzing or designing complex system architectures to ensure simplicity, robustness, and maintainability.

This skill simulates a Principal Software Architect, specializing in designing, reviewing, and documenting high-level system architectures. It guides users through defining core system structures, evaluating complex technology trade-offs (e.g., ACID vs. eventual consistency), and planning for extreme scalability. Key outputs include comprehensive architecture diagrams (Mermaid) and formal Architecture Decision Records (ADRs), ensuring every major technical choice is documented with rationale and consequences.

This skill generates comprehensive Technical Design Documents (TDDs), guiding users through structuring architectural decisions, implementation plans, and risk assessments. It follows industry best practices from standards like Google Design Docs, RFC patterns, and ADRs. It focuses on high-level contracts and architectural 'what' and 'why', rather than specific, low-level implementation code.

Creates concise Architecture Decision Records (ADRs) that capture context, decision, and consequences whenever a significant technical choice has been finalized so future engineers understand why the architecture looks the way it does.

Automatically capture architecture decisions during Claude Code sessions as structured ADRs, tracking context, alternatives, and consequences so future developers understand why the codebase looks the way it does.

Guides writing documentation and ADRs to capture why architectural or API choices were made, when to comment, and how to structure README/API info so future engineers and agents understand the rationale and trade-offs.

This skill acts as a rigorous, Socratic interviewer designed to stress-test a proposed plan against an established domain model and existing project documentation. It forces the user to sharpen terminology, resolve cross-cutting dependencies, and identify inconsistencies between stated requirements, code implementations, and documented decisions. It ensures the resulting architecture is precise, consistent, and well-documented by automatically updating the context and generating Architecture Decision Records (ADRs).

A deep-dive session designed to stress-test a technical plan against an existing domain model. This process forces the user to resolve ambiguities, sharpen terminology, and validate decisions by cross-referencing code and existing documentation (CONTEXT.md, ADRs). It ensures architectural rigor and completeness before implementation.