Skill UI

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.

Generates an AI-ready Architectural Decision Record template with precise sections, coded bullet conventions, front-matter metadata, and sequential storage under /docs/adr to keep decision documentation structured for both machines and people.

A comprehensive guide to optimizing CAST AI's core performance metrics, including node provisioning speed, autoscaler responsiveness, and API call efficiency. This skill covers techniques like configuring headroom, selecting optimal instance families, tuning evictors, and implementing caching for multi-cluster dashboards to ensure high availability and cost efficiency in cloud environments.

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.

This skill facilitates a rigorous, documentation-anchored design review session. It challenges a proposed plan by cross-referencing it against the project's established domain glossary (CONTEXT.md), historical architectural decisions (ADRs), and the current codebase. It forces the user to resolve ambiguities, define precise terminology, and validate design trade-offs using concrete scenarios, ensuring all decisions are captured and documented inline.

This skill generates a formal Architecture Decision Record (ADR) following industry-standard formats. It guides users through documenting the full rationale behind significant technical choices, ensuring that the context, alternatives considered, chosen option, and resulting trade-offs are all captured. Ideal for maintaining architectural integrity and knowledge transfer within engineering teams.

This skill generates a comprehensive capacity plan document for any service. It assists technical teams in proactively managing infrastructure by modeling traffic growth, forecasting resource utilization (CPU, memory, connections), projecting costs, and defining clear scaling strategies. Use this when assessing current resource headroom, planning for seasonal peaks, or defining a long-term infrastructure action roadmap.

This skill generates a sophisticated prioritization matrix by combining quantitative RICE (Reach, Impact, Confidence, Effort) scoring with qualitative Strategic Alignment ratings. Use this when multiple features compete for resources, requiring a balanced decision between sheer user impact and adherence to core business OKRs. The output provides a scored priority matrix, quadrant placement (Now, Next, Later, Drop), and explicit sequencing recommendations.

This skill generates a comprehensive Technology Radar document following the ThoughtWorks format. It provides a structured framework for an engineering team to evaluate and categorize all significant technologies (tools, languages, platforms, techniques) into four quadrants (Adopt, Trial, Assess, Hold). It helps establish a shared, explicit technology strategy, detailing adoption rationales, decision trails, and maintenance processes for consistent engineering choices.

A comprehensive skill for systematically building, refining, and documenting a project's domain model. It helps define core terminology, establish a ubiquitous language, and record critical architectural decisions (ADRs). Use this when you need to challenge ambiguous language, invent edge-case scenarios, or maintain architectural consistency throughout the development lifecycle.