Skill UI

Tracks every code change via structured JSON records, enforces a lifecycle state machine, and maintains session handoff context with scripts for init/create/update/status/resume/close/export workflows.

A comprehensive tool that analyzes complex codebases to generate detailed, structured architectural blueprints. It automatically detects and documents the entire technology stack, including primary languages (.NET, Java, Python, etc.), dependencies, versions, licensing, and implementation patterns. The output provides actionable documentation covering coding conventions, usage examples (API, data access), and visual architecture maps, ensuring consistency across guided software development projects.

A comprehensive guide covering best practices for Terraform and OpenTofu. It provides structured advice on module hierarchy, directory organization, naming conventions, and advanced testing strategies (including native testing and policy as code). Use this skill when designing, refactoring, or implementing robust Infrastructure as Code (IaC) pipelines and multi-environment deployments.

Automatically update implementation plan files to reflect new requirements, ensuring structured, machine-readable phases with explicit tasks and validation criteria for AI agents to execute deterministically.

This guide provides a comprehensive template and best practices for updating technical specification files. It ensures that the resulting documentation is structured, unambiguous, and highly optimized for consumption by Generative AI models. Use this process when refining system requirements, updating interfaces, or documenting architectural changes to maintain machine-readable standards.

This structured prompt guides an AI model to proactively analyze a user's question and systematically list all necessary files for accurate answering. It forces the AI to categorize required context into 'Must See' (critical), 'Should See' (helpful), 'Already Have,' and 'Uncertainties.' Ideal for complex coding tasks, debugging, or feature implementation that spans multiple codebase files.

This skill guides the systematic process of converting vague ideas or initial requirements into complete, detailed, and approved technical specifications. It enforces a structured workflow, including context exploration, iterative questioning, proposing multiple options with trade-offs, and creating documented blueprints. Critically, it ensures that no implementation or code writing occurs until the design has been fully vetted and formally approved by the user.

This skill guides the systematic execution of a detailed, written development plan. It mandates a critical review phase to identify dependencies, vague requirements, and environment assumptions before starting. The process involves tackling tasks sequentially, performing rigorous verification (testing/checking), committing changes after each milestone, and systematically handling common exceptions like test failures or dependency gaps. It ensures a disciplined, traceable, and reportable development cycle.

This skill guides developers through the final stages of a development branch workflow. It enforces critical best practices by requiring a test verification step before presenting structured options. Users can choose between local merging, creating a Pull Request (PR), retaining the branch state, or safely discarding the work, ensuring a clean and repeatable integration process.

This guide outlines the structured methodology for initiating code reviews using a dedicated sub-agent. It dictates when (after completing tasks, implementing critical features, or before merging) and how to provide the necessary context (SHA hashes, implemented code, requirements) to ensure the work product is thoroughly evaluated. By adopting this process, developers can catch architectural flaws and bugs early in the development lifecycle, improving code quality and maintainability.

This tool generates canonical, submit-ready FrontendIntegration YAML from a simplified, single-menu authoring model. It is ideal for converting preliminary configurations (like those derived from a CRD) into the full, structured YAML required for deploying frontend integrations, ensuring all fields and placements are correctly mapped.

This comprehensive tool guides the systematic creation of detailed technical specifications. It orchestrates the entire design lifecycle, including context loading, deep discovery and analysis (tailored for new features, extensions, or simple additions), synthesis using established design principles, and generating a boundary-first, structured design draft. Ensures all requirements are mapped to explicit technical components.