Skill UI

This guide details the principles of observability, teaching developers how to instrument code by implementing structured logging, metrics, and distributed tracing. It ensures that production features emit sufficient telemetry to answer complex operational questions, transforming unknown failures into diagnosable events. Essential for any service running in production.

An adversarial Quality Assurance (QA) pass designed to deep-dive into any codebase for logic errors, security flaws, and functional bugs. Instead of confirming that code 'looks right,' this skill actively attempts to break the code by simulating hostile inputs, tracing critical data paths, and checking for subtle, real-world correctness issues. Essential for high-stakes, critical code reviews.

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