Skill UI

This skill helps refine vague, raw ideas into sharp, actionable concepts. It guides users through structured divergent thinking (expanding options, generating variations) and convergent thinking (stress-testing assumptions, clustering directions). The process culminates in a detailed one-pager including Problem Statements, MVP Scope, and key assumptions to validate, ensuring focus and clarity before development.

A structured methodology for initiating complex software projects or features. Instead of writing code immediately, this process mandates creating a detailed, shared specification (Spec) first. It guides users through four phases (Specify, Plan, Tasks, Implement) to clarify ambiguous requirements, define system boundaries, and establish measurable success criteria before any implementation begins.

A comprehensive methodology guiding technical professionals through the design process before coding. It helps structure complex features by producing detailed design documents, including system overviews, data models, API specifications, multiple trade-off analyses, and implementation plans, ensuring robustness and clarity from the start.

An advanced technical writer specializing in creating structured, high-quality software documentation. This skill strictly adheres to the Diátaxis Framework, ensuring content is categorized into Tutorials (learning), How-to Guides (problem-solving), Reference (technical details), and Explanations (concept understanding). It follows a rigorous workflow: clarification, structure proposal, and content generation, guaranteeing clarity, accuracy, and user-centricity.

This guide implements the Red-Green-Refactor cycle, the core methodology of Test-Driven Development (TDD). It teaches developers to first write a failing test (RED), then implement the minimum required code to make the test pass (GREEN), and finally improve the structure and clarity of the code without changing its behavior (REFACTOR). Use this guide when mastering TDD, ensuring robust unit test coverage, or following best practices for writing resilient software.

Refines prompt files by analyzing prior successful patterns, improving structure, wording, and clarity while preserving the original intent and markdown front matter.

Interactive workflow that uses the joyride_request_human_input tool to probe scope, deliverables, and constraints before executing any task, ensuring thorough clarification and structured planning.

This guide outlines a rigorous, technical framework for receiving and responding to code review feedback. It emphasizes that code review is a technical assessment, not an emotional exchange. Users learn how to verify assumptions, ask clarifying questions, professionally refute incorrect suggestions, and implement changes iteratively, ensuring code quality and architectural integrity.

This guide outlines a mandatory, evidence-based protocol for declaring any work complete, fixing a bug, or submitting a pull request. It strictly mandates that all claims of success must be supported by fresh, verifiable evidence, such as passing test outputs, successful build logs, or comprehensive checklist verification. It eliminates reliance on assumptions, gut feelings, or trusting proxy reports.

This skill generates highly focused, evidence-based medical treatment plans in LaTeX/PDF format, suitable for all clinical specialties. It emphasizes brevity (3-4 pages), regulatory compliance (HIPAA), and actionable steps. Ideal for managing chronic diseases, physical rehabilitation, and mental health care, ensuring structured care pathways and incorporating AI-generated scientific schematics for visual clarity.

This skill generates comprehensive and structured requirements documents for a new specification. It systematically aggregates context from project files, business rules, and technical constraints, ensuring all generated requirements focus on user-observable behavior (WHAT) rather than implementation details (HOW). It follows established standards like EARS format and includes a rigorous review gate to ensure scope clarity and completeness.

This skill rigorously verifies all claims of completion, whether for a task, a bug fix, or a feature rollout. It prevents false assurances by demanding fresh, multi-faceted evidence, including full test suite results, comprehensive coverage reports, integration status, and validation commands. Use it before declaring a component ready for GO or accepting a sub-agent's success report.