Skill UI

This skill reviews code differences (diffs) to identify opportunities for improvement in clarity, reusability, efficiency, and overall quality. It employs multiple specialized sub-agents (e.g., Code Reuse, Efficiency, Quality) to audit changes. It can provide high-confidence, behavior-preserving fixes when requested, ensuring the code adheres to best practices without introducing regressions. Best used when refactoring, cleaning up, or auditing a specific code scope.

This skill enforces a high standard for all generated code, prioritizing correctness, clarity, and idiomatic patterns across all languages. It helps minimize code bloat by removing unnecessary abstractions and verbose patterns, while also optimizing the agent's output by using targeted diffs and eliminating excessive conversational overhead. Use this for all code generation, refactoring, or review tasks.

A comprehensive guide detailing how to refactor large, complex SwiftUI views into smaller, more stable, and explicit components. It emphasizes adopting a lightweight state approach (favoring local state and environment variables over excessive view model layers) to improve data flow, readability, and overall code maintainability in modern iOS development.

Safely refactor code with a comprehensive TDD safety net: establish a green baseline, detect code smells, apply design patterns and SOLID principles, optimize performance, and verify all tests remain green.

This skill provides a systematic, multi-step approach to identify and resolve all failing unit tests within a codebase. It guides the user through smart error grouping (e.g., grouping by ImportError or AttributeError), prioritizing fixes from infrastructure to business logic, and ensuring thorough verification to prevent regressions. Ideal for use after major refactoring, debugging CI/CD failures, or when explicitly tasked with making the test suite pass.

This guide provides a systematic, safe workflow for refactoring rapidly developed or AI-generated fullstack applications. It focuses on identifying and removing dead code, fixing broken imports, and consolidating repetitive logic while strictly maintaining existing API contracts, routes, and core functionality. Use this before launch to ensure a stable, maintainable production baseline, following a 'surgery, not demolition' philosophy.