Skill UI

This guide provides a comprehensive template and best practices for updating technical specification files. It ensures that the resulting documentation is structured, unambiguous, and highly optimized for consumption by Generative AI models. Use this process when refining system requirements, updating interfaces, or documenting architectural changes to maintain machine-readable standards.

This skill provides comprehensive guidelines for contributing and managing commands within VS Code extensions. It covers crucial best practices, including naming conventions, defining visibility (e.g., Command Palette vs. Side Bar), and structuring commands for optimal user experience. Use this when adding, updating, or understanding the architectural requirements for extension commands.

This guide provides comprehensive guidelines for localizing all aspects of VS Code extensions. It covers best practices for handling configurations (settings, commands, menus), user-facing string resources, and walkthrough content. Developers can use this skill to ensure their extensions are properly adapted and functional for multiple languages.

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 comprehensive toolkit automates critical Webflow operations, including managing CMS collections (create, update, delete), site publishing, page inspection, and asset uploads. By connecting via Rube MCP, it allows developers to programmatically interact with Webflow's backend, making it ideal for implementing automated content workflows, CI/CD pipelines, and large-scale content management systems.

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

A comprehensive guide providing Git workflow standards specifically adapted for domestic Chinese platforms (Gitee, Coding.net, etc.). It covers platform configuration, branch strategies (Git Flow, Trunk-Based), naming conventions, Chinese Conventional Commits, and CI/CD pipeline setup, solving common issues faced in local development environments.

A comprehensive workflow for concluding a feature development branch. It guides the user through mandatory steps like running tests, detecting the Git environment, and presenting structured options (Merge, Pull Request, Keep, Discard). It ensures proper integration and safe cleanup of worktrees.

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 for conducting professional code reviews, especially for Chinese development teams. It teaches how to balance direct technical critique with respectful communication, covering feedback phrasing (suggestion vs. command), priority labeling, proper documentation standards, and conventional commit message formats.

This guide details the best practices for utilizing a code review sub-agent. It should be used after completing tasks, implementing major features, or before merging code into main branches. The process ensures that work results are validated against requirements, allowing reviewers to focus purely on the output rather than the development history, thus catching issues early.