Skill UI

This comprehensive skill demonstrates advanced usage patterns for Formik, a popular React form handling library. It covers basic form setup, complex validation schema creation using Yup (including conditional logic), field helper utilities, and integrating form submissions with GraphQL mutations for both creation and editing scenarios.

This skill generates comprehensive unit and integration tests using Jest for JavaScript and TypeScript. It supports advanced testing patterns, including deep mocking, asynchronous handling, snapshot testing, and testing React components with Testing Library. Use it when the user needs to thoroughly validate application logic and behavior.

This skill performs a deep comparison of two code versions to verify semantic equivalence, going beyond simple syntax diffing. It uses semi-formal tracing techniques to trace both versions against shared specifications and boundary conditions (e.g., null, zero, max/min). Ideal for confirming if a refactor, rewrite, or migration has unintentionally altered the code's behavior, answering the question: "Did I break anything?"

This skill generates a detailed, step-by-step, interprocedural execution trace for a given piece of code and specific input scenario. It resolves name ambiguities, tracks type transitions, and highlights non-obvious behaviors (like implicit coercions or side effects). Use it when a user is confused about how code behaves, allowing for a deep dive into the actual execution path to clarify assumptions versus reality.

This skill provides an autonomous, repository-wide pipeline for auditing and fixing complex logical inconsistencies. It systematically executes stages including health checks, deep review, locating divergences, generating fixes, and performing diff-verification until the codebase is deemed clean. Ideal for maintaining high code quality and resolving deep, systemic bugs across entire projects.

This sophisticated skill is designed to locate the root cause of a confirmed software failure. It performs a systematic, semi-formal tracing process: first tracing backward from the observed failure point (using provided stack traces, assertions, or error messages) to identify the original premise, and then tracing forward to confirm the symptom. It outputs a highly structured report detailing the divergence, premises, and remedy.

This skill is designed to identify subtle and complex logic bugs within a single code file or function. It employs a semi-formal execution tracing methodology, systematically breaking down the suspected bug into five stages: Premises (expected state), Trace (execution path), Divergence (actual deviation), Trigger (reproduction case), and Remedy (fix). It is ideal for scenarios where users suspect code is wrong but cannot specify a concrete failure point.

A constraint-based protocol designed to professionalize existing code by normalizing comments and performing safe, non-semantic cleanup. This skill converts informal, outdated, or missing documentation into clear, concise, and professional standards without altering the core logic or behavior. Ideal for preparing code for code review, open-sourcing, or formal documentation.

A cinematic template designed for creating high-impact title screens and video transitions. Perfect for cyberpunk, sci-fi, or technological narratives, it simulates digital data corruption, chromatic aberration, and CRT noise to give a powerful, vintage-digital aesthetic.

Implements a robust caching strategy by using the SHA-256 hash of file content as the primary key, instead of the file path. This pattern is essential for high-cost file processing pipelines (like OCR, PDF parsing) because it ensures cache hits survive file renaming or moving, while still automatically invalidating entries when the content changes. It adheres to the Single Responsibility Principle (SRP) by isolating caching logic into a service layer wrapper.

A comprehensive pattern for building robust and cost-efficient LLM application pipelines. This guide details combining model routing based on task complexity, immutable cost tracking, limited retry logic, and prompt caching to manage API expenditures while maintaining high quality. Essential for production systems handling variable-complexity, high-volume tasks.

This skill acts as an expert guide, transforming a complex, natural language workflow description (e.g., "build an MVP") into a structured, multi-step execution blueprint using ECC command groups. It identifies the necessary command sequence, the logical run-order, and crucial stop conditions (e.g., max iterations, review passes). It is advisory and designed for planning, filling the gap between flat documentation and single-prompt output.