Skill UI

This guide adapts the Conventional Commits standard for Chinese development teams. It provides comprehensive rules for writing commit messages, including structured formats for subject, body, and footer. It also details the integration and configuration of automation tools like commitlint, conventional-changelog, and husky, ensuring a consistent, readable, and traceable version history.

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.

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

Implements automated policy enforcement and guardrails for Canva Connect API integrations. This system enforces best practices such as preventing hardcoded credentials, ensuring proper rate limit handling (429 responses), and validating robust OAuth configurations. It is essential for maintaining high code quality and security in CI/CD pipelines and pre-commit hooks.

A comprehensive guide to securing ClickUp API usage. Learn best practices for managing API tokens, implementing least-privilege access, and auditing usage patterns. This includes secure token rotation procedures, using environment variables, setting up pre-commit hooks to prevent leaks, and structuring calls for robust audit logging.

This skill helps users design robust and optimal software interfaces (APIs) for a module by applying the 'Design It Twice' philosophy. It generates multiple, radically different architectural designs using parallel agents, allowing for comprehensive comparison of trade-offs (e.g., simplicity vs. flexibility, specialized vs. general-purpose). Use this when you need to explore various structural options or compare module shapes before committing to a final design.

A comprehensive guide detailing security best practices for integrating with ElevenLabs. It covers secure API key management using environment variables, implementing Git pre-commit hooks, and demonstrating robust webhook signature verification using HMAC-SHA256. This ensures secure data handling, replay protection, and proper voice data governance.

A rigorous coding discipline tool derived from Andrej Karpathy’s principles. It helps developers, especially when working with LLMs, enforce four critical rules: surfacing assumptions, prioritizing simplicity, making surgical changes, and defining verifiable goals. It acts as a comprehensive pre-commit hook and review agent to prevent over-engineering, hidden assumptions, and unnecessary code bloat.

This internal agent skill automates the complex process of determining the most likely owner or team for a bug cluster. It follows a strict 6-level precedence model, starting with cached overrides, and sequentially querying sources like Service Owners, Oncall status, CODEOWNERS, recent assignees, and committers. The process includes staleness detection and confidence scoring, providing highly accurate and auditable routing recommendations for internal development triage.

This internal agent skill defines a systematic, multi-step procedure for scanning GitHub repositories to gather comprehensive evidence supporting or explaining bug clusters. The process covers searching open issues, inspecting recent commits, analyzing code paths, and checking deployment history. It assigns evidence confidence tiers (Exact, Strong, Moderate, Weak) to provide a deep, actionable understanding of potential software defects.

This skill guides developers through creating a comprehensive refactoring plan and serving as a Request for Comments (RFC). It orchestrates detailed interviews, codebase analysis, and scope definition. It ensures the refactor is broken down into tiny, safe, incremental commits, culminating in a structured GitHub issue that serves as a definitive architectural and technical decision document.