Skill UI

A systematic, non-mutating investigation designed for complex software failures, including bugs, regressions, crashes, and flaky behavior. This skill launches four specialized, read-only sub-agents in parallel to perform deep root-cause analysis, trace code paths, pinpoint the smallest failing seam, and predict the quickest path to confirming or fixing the issue. It is designed purely for diagnosis and hypothesis generation.

This powerful skill provides an interactive debugger interface, allowing developers to set breakpoints, step through source code line by line, inspect live variable states, and trace the entire call stack. It is essential for diagnosing complex bugs, understanding unexpected program flow, or determining the root cause when standard logging fails. It supports various languages via the DAP protocol.

This guide details advanced strategies for publishing technical content across major developer platforms like Dev.to and Hashnode. It covers cross-posting best practices, canonical URL management for optimal SEO, and platform-specific optimization (e.g., tagging, content performance) to maximize reach and build authority.

This skill guides the implementation of advanced SEO strategies tailored specifically for technical audiences and developers. It covers specialized techniques such as optimizing for error messages, researching high-intent technical long-tail keywords, creating structured how-to guides, and developing objective tool comparison content. Use this when targeting developers who search with precise technical intent, needing solutions that go beyond standard documentation.

A comprehensive guide for developers on creating and writing native modules and views using the Expo Modules API. It covers platform-specific implementation details for Swift (iOS), Kotlin (Android), and TypeScript. Use this when integrating system APIs, wrapping platform SDKs, or building complex native functionality that goes beyond standard React Native components.

Use @expo/ui to build high-fidelity, native user interfaces across iOS and Android from a single React codebase. This library renders real native UI components, such as SwiftUI on iOS and Jetpack Compose on Android. It promotes a universal component layer for cross-platform consistency, while also providing controlled access to platform-specific optimizations and drop-in replacements for existing community libraries.

This discipline establishes a portable, framework-agnostic layer for ensuring type safety at the network edge of any React or React Native application. It mandates a single, typed API client to wrap all network fetching, guaranteeing that raw wire JSON is immediately parsed into trusted, domain-specific types or standardized error objects before entering the application state. This pattern drastically reduces runtime errors and enhances code robustness.

A comprehensive guide for developers building AI demos and GPU compute tasks on Hugging Face Spaces using ZeroGPU hardware. It covers best practices for writing and reviewing code that utilizes the `@spaces.GPU` decorator, managing runtime duration and quota, and understanding the specific CUDA availability model and process isolation rules required for reliable ML deployment.

This skill is designed to accurately convert complex, Hugo-managed documentation sites and content into standard Markdown format. It goes beyond generic knowledge by inspecting the entire local Hugo repository structure, including `hugo.toml`, custom shortcodes, layouts, and content files. It preserves the original content's semantic meaning while materializing Hugo-specific constructs into clean Markdown.

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 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.