Skill UI

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 structured prompt guides an AI model to proactively analyze a user's question and systematically list all necessary files for accurate answering. It forces the AI to categorize required context into 'Must See' (critical), 'Should See' (helpful), 'Already Have,' and 'Uncertainties.' Ideal for complex coding tasks, debugging, or feature implementation that spans multiple codebase files.

This skill helps developers accurately find and explore the correct Windows API for specific platform capabilities, such as file access, camera usage, notifications, or UI controls. It searches a comprehensive local cache of WinMD metadata, providing full technical details including methods, properties, events, and enumeration values for APIs sourced from the Windows Platform SDK and WinAppSDK. It is indispensable when building complex features requiring deep integration with the Windows operating system.

This comprehensive guide serves as a technical reference for migrating applications from the Universal Windows Platform (UWP) framework to the modern WinUI 3 / Windows App SDK. It details crucial API changes, including namespace updates, window management (CoreWindow to AppWindow), threading models (CoreDispatcher to DispatcherQueue), and best practices for dialogs and background tasks. Essential for developers updating legacy UWP codebases.

Scans specified files or folders to infer existing syntax, writes a project coding standards or contribution doc using configurable templates, and optionally reports or fixes inconsistencies before saving to the first available standard filename.

This skill guides the systematic process of converting vague ideas or initial requirements into complete, detailed, and approved technical specifications. It enforces a structured workflow, including context exploration, iterative questioning, proposing multiple options with trade-offs, and creating documented blueprints. Critically, it ensures that no implementation or code writing occurs until the design has been fully vetted and formally approved by the user.

This comprehensive guide adapts the Conventional Commits specification for Chinese development teams. It outlines best practices for structuring commit messages, covering types (feat, fix, perf), subjects, detailed bodies, and handling breaking changes. By enforcing a uniform standard, this skill facilitates automated changelog generation and maintains a clean, readable, and traceable project history.

This comprehensive guide provides a complete set of Git workflow standards specifically adapted for Chinese development environments, covering Gitee, Coding, and Jihuo GitLab. It addresses common pain points like unstable foreign platform access, non-localized CI/CD, and inconsistent commit messages. The guide covers multiple workflow models (Trunk-Based, Git Flow), branch naming conventions, Chinese Conventional Commits, and CI/CD configurations for major domestic platforms.

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.

This skill guides developers through the final stages of a development branch workflow. It enforces critical best practices by requiring a test verification step before presenting structured options. Users can choose between local merging, creating a Pull Request (PR), retaining the branch state, or safely discarding the work, ensuring a clean and repeatable integration process.

A comprehensive, four-stage methodology for debugging complex software issues, ensuring that fixes target the root cause rather than merely masking symptoms. This guide mandates rigorous investigation (gathering evidence, tracing data flow), pattern analysis, controlled hypothesis testing, and disciplined implementation via test-driven development. Use this when facing production bugs, test failures, performance degradation, or unexplained system behavior, especially under time pressure.

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.