Skill UI

Start or monitor an evolutionary loop that refines ontology and acceptance criteria across generations. Supports starting new loops, monitoring status, rewinding to previous generations, and managing AI agent workflows for iterative software development. It integrates with MCP tools for ontology refinement and acceptance criteria validation.

Provides IDA Pro reverse engineering capabilities for analyzing binaries, PE/ELF/APK/DLL/SO files, firmware, and malware. Supports decompilation, password discovery, vulnerability analysis, and software cracking workflows. Uses deterministic scripts for HTTP server management and file opening to avoid known MCP schema and lock issues.

This skill addresses the common problem of documentation decay in long-lived software projects. It establishes a canonical governance layer by assigning four non-overlapping roles—Constitution, Map, Status, and History—to existing documentation. By linking these roles to the active agent harness, it prevents documentation drift, ensuring that all project information remains accurate, authoritative, and contextually linked to the current codebase, making it ideal for the maintenance phase.

A comprehensive methodology covering advanced offensive techniques targeting the software supply chain. This includes exploiting dependency confusion across npm, PyPI, and NuGet, executing build system hooks, tampering with CI/CD pipelines, and compromising container images. It provides detailed PoC patterns and detection guidance for red team operations.

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.

This advanced skill initializes the Software Development Documentation (SDD) context within a project. It detects the entire technical stack, conventions, testing tools, and persistence mode across all discovered projects. It then structures and persists this comprehensive context, including building a skill registry and determining the strict TDD status, ensuring a robust starting point for development.

This sophisticated sub-agent takes comprehensive Software Design Documents (SDD), proposals, and specifications to generate a detailed, actionable task breakdown in the format of a tasks.md file. It structures the work into distinct phases (e.g., Foundation, Core Implementation, Testing, Cleanup), providing concrete, verifiable, and small units of work suitable for immediate engineering execution and managing complex feature delivery chains.

This skill enables applying John Ousterhout's design principles to reduce complexity in software systems. It guides decisions on module boundaries, API design, information hiding, and abstraction depth. Use it when refactoring shallow interfaces or managing cognitive load during development. Ideal for architects and senior engineers optimizing system structure and ensuring maintainable codebases through proper abstraction layers.

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 Robert C. Martin-inspired clean code rules to improve code readability, naming conventions, function design, and responsibilities. This skill ensures everyday implementation quality, readable control flow, and testable code by following established best practices for software development.

This skill applies Steve McConnell's construction rules to software development tasks. It covers routine design, variable usage, class design, control flow, defensive programming, coding standards, and testing. Use it for disciplined software construction to ensure high-quality code implementation.