Skill UI

Automates architecture decision record (ADR) generation and guidance within technical documentation workflows, offering best-practice patterns, production-ready snippets, and validation for API docs, user guides, and automation needs.

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.

Provides structured ADR patterns, templates, and practices for capturing significant architectural decisions, rationale, tradeoffs, and lifecycle status to onboard teams and review historical choices.

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.

Automates Codereadr tasks via Composio’s Rube MCP by guiding tool discovery, connection checks, and multi-tool execution while enforcing schema compliance and session reuse.

Guides CTOs and tech leaders through strategy, architecture governance, team scaling, and crisis response, with workflows for technical debt assessment, ADR creation, and vendor evaluation to keep engineering healthy.

This guide provides comprehensive templates and best practices for structuring all types of technical documentation. It covers essential formats including README files, REST API endpoints, code comments (JSDoc), Changelogs, Architecture Decision Records (ADR), and AI-optimized documentation. Use these templates to ensure your project documentation is standardized, scannable, and easily consumable by both human developers and AI agents.

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.

Provides architecture design support including ADR templates, system design checklists, scalability assessment prompts, architecture patterns, and API guidance so engineers can document decisions and ensure reliability during technical design phases.

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.

This skill helps developers structure and record critical architectural decisions (ADRs) made during coding sessions. It automatically detects moments of decision, capturing the context, alternatives considered, and the rationale (trade-offs and consequences). This maintains a living log that explains 'why' the code base was built the way it is, preventing knowledge loss and improving project maintainability.

This guide provides best practices for technical documentation, emphasizing the capture of context (the *why*) rather than just code (the *what*). It details how to write Architecture Decision Records (ADRs) for significant architectural choices, such as database selection, API design, and framework choice. Utilizing ADRs ensures that future engineers and teams understand the original reasoning, constraints, and trade-offs made during development.