Skill UI

This guide provides expert advice on positioning research papers for top-tier computer architecture conferences (e.g., ISCA, MICRO, ASPLOS). It teaches authors how to identify the 'center-of-gravity' of their novelty—whether it lies in the hardware organization, the hardware/software contract, or the software layer alone—to maximize review acceptance chances and successfully navigate the competitive academic publication landscape.

An advanced orchestrator that manages the entire software development lifecycle (SDLC) from initial concept vetting to final code deployment. It guides the process through distinct, sequential stages: Product Direction Review (CEO), Technical Architecture Review (Engineering), Detailed Planning, Validation, and final Execution (PR). This tool ensures all critical gates are passed before writing code, minimizing risks and ensuring alignment.

This specialized sub-agent is responsible for transforming high-level feature proposals and technical specifications into a formal, comprehensive 'design.md' document. It systematically captures all necessary technical details, including architectural decisions, data flow diagrams, detailed file changes, API contracts, and thorough testing strategies. Use this skill during the planning phase of any complex software change to ensure technical completeness and feasibility.

This agent is dedicated to systematically exploring technical ideas, such as new features, refactoring, or bug fixes, *before* committing to code changes. It investigates the existing codebase, analyzes current architecture, compares multiple potential approaches (including pros, cons, and effort), and generates a structured 'exploration' report with a clear recommendation and identified risks. It ensures thorough planning and risk mitigation during the design phase.

Apply Robert C. Martin-inspired rules to separate business policy from frameworks, databases, UI, and infrastructure. This skill helps define architectural boundaries, dependency direction, use cases, and interface adapters. Use it for software design decisions involving framework isolation or technology churn to ensure maintainability and clarity.

Apply lightweight Domain-Driven Design rules for bounded contexts, subdomains, and tactical modeling without unnecessary ceremony. Ideal for practical software architecture guidance and design decisions in complex systems.

Apply Vaughn Vernon-inspired rules for building aggregates, domain events, repositories, and application services. This skill helps structure code using bounded contexts and domain logic, ensuring clean architecture and maintainable software design during development.