Skill UI

This guide provides comprehensive best practices for writing, structuring, and reviewing tests for Flutter and Dart applications. It covers unit tests, widget tests, golden tests, ensuring test validity, best practices for mocking, and file organization, helping developers write robust and meaningful tests that catch real regressions.

This skill systematically reviews test code to identify and correct common anti-patterns. It detects issues such as flaky tests, overly mocked dependencies (over-mocking), brittle assertions, excessive test size (The Giant), and structural dependencies. It explains the flaw, provides best practices, and suggests refactored, reliable implementations, helping maintain high test quality and stability.

Enforces modern TypeScript patterns during development and reviews, guiding const usage, explicit return types, interface-driven shapes, and avoiding any/var or ignored errors.

A comprehensive guide for writing and reviewing robust, behavior-first unit tests for Vue 3, TypeScript, and Pinia stores. This skill covers advanced patterns for testing components, composables, and state management using Vitest and Vue Test Utils, emphasizing black-box assertions and minimizing implementation coupling.

This tool reviews user interface (UI) code files to ensure compliance with established Web Interface Guidelines and best practices. Use it when auditing design, checking accessibility, or performing general code reviews to meet industry standards and improve overall product quality. It fetches the latest rules and outputs detailed findings.

This skill guides the systematic execution of a detailed, written development plan. It mandates a critical review phase to identify dependencies, vague requirements, and environment assumptions before starting. The process involves tackling tasks sequentially, performing rigorous verification (testing/checking), committing changes after each milestone, and systematically handling common exceptions like test failures or dependency gaps. It ensures a disciplined, traceable, and reportable development cycle.

A comprehensive guide on conducting effective and professional code reviews, tailored for domestic team cultures. It teaches techniques like using suggestions instead of commands, framing feedback as questions, implementing clear severity levels, and maintaining proper mixed Chinese/English annotation standards. Essential for improving code quality while preserving team harmony.

A comprehensive guide for software developers on how to respond to code review feedback with technical rigor. It emphasizes questioning, verification, and evidence-based rebuttal, moving beyond superficial agreement. Learn how to handle ambiguous feedback, apply the YAGNI principle, and maintain technical integrity in collaborative development environments.

This guide outlines the structured methodology for initiating code reviews using a dedicated sub-agent. It dictates when (after completing tasks, implementing critical features, or before merging) and how to provide the necessary context (SHA hashes, implemented code, requirements) to ensure the work product is thoroughly evaluated. By adopting this process, developers can catch architectural flaws and bugs early in the development lifecycle, improving code quality and maintainability.

This guide teaches advanced search techniques for identifying specific video games. It emphasizes using highly discriminative technical details such as specific platforms (e.g., DOS, NES, PS4), distribution methods (shareware), game engines, era, and detailed review scores from niche sites. By combining multiple constraints (Platform + Era + Detail), users can dramatically narrow down search results, even locating specific developers or artists involved in the game's creation.