Skill UI

A comprehensive guide for professional code review in Chinese development teams. It addresses common communication pitfalls, offering structured methods to give critical feedback that is both rigorous and constructive. Learn how to use suggestion-based language, structured severity levels, mixed Chinese/English commenting, and optimal review processes to elevate code quality and team collaboration.

This skill deploys a containerized integration service to programmatically manage and manipulate Lucidchart diagram documents. It handles sophisticated tasks like manipulating shapes, updating connectors, and synchronizing visual collaboration data using the Lucid API. Ideal for integrating automated diagram generation and maintenance into CI/CD pipelines and enterprise workflows.

This skill provides comprehensive knowledge on setting up and handling real-time webhook events from Lucidchart. It details how to receive notifications—such as document creation, updates, sharing, and shape additions—via signed JSON payloads over HTTPS. Users can implement robust integrations for compliance auditing, triggering CI/CD pipelines, or notifying external collaboration tools like Slack.

This guide provides comprehensive strategies and code examples for managing and reducing API costs associated with large-scale usage of Lucidchart. It covers optimizing document exports through caching, batching operations, reducing excessive real-time collaboration events, and efficiently managing user seats to ensure cost-effective diagramming workflows.

This comprehensive checklist ensures that your Lucidchart integration is robust and resilient for production use. It covers critical areas such as OAuth2 token lifecycle management, handling document-level collaboration locks, managing rate limits, and ensuring correct API version pinning. By following these steps, developers can mitigate risks associated with concurrent edits, large diagram exports, and schema drift, guaranteeing a stable user experience.

Designs a scalable, version-controlled integration layer for the Lucidchart platform. This architecture tracks every shape mutation for diffing and rollback, implements real-time collaboration event consumption, and manages asynchronous export pipelines (PNG/SVG/PDF) using dedicated worker pools and caching strategies. Ideal for developing robust SaaS integrations requiring rigorous data synchronization.

This comprehensive workflow provides full Create, Read, Update, and Delete (CRUD) capabilities for managing Miro boards and all embedded items. Users can programmatically manage entire boards, sticky notes, shapes, cards, frames, and tags using the official REST API v2. Ideal for integrating Miro into automated workflows, automating retrospective reports, or building complex collaboration tools that require structured board content manipulation.

Configure comprehensive, enterprise-grade access control for Miro via REST API v2. This module manages organization structure, team membership, and granular board permissions (RBAC). It supports advanced features like automated user provisioning using SCIM 2.0 and SSO integration, making it essential for implementing secure, scalable collaboration platforms in large corporate environments.

This tool allows users to execute complex, multi-agent workflows defined in YAML format directly within the AI environment. It functions as an orchestration engine, sequentially invoking various specialized roles (agents) without requiring manual API key configuration. Ideal for structured tasks requiring collaboration between multiple personas.

This guide provides the reference architecture for integrating Workhuman's Social Recognition and rewards APIs. It details key concepts like OAuth 2.0, peer-to-peer recognition, and configurable awards. Use this skill when building complex employee recognition workflows, syncing data bi-directionally with HRIS systems (e.g., Workday, SAP), or integrating with collaboration tools like Slack and Microsoft Teams.

This skill analyzes raw git diffs or change descriptions to generate clear, story-driven commit messages. It strictly adheres to the Conventional Commits specification, ensuring that messages thoroughly explain *why* a change was made, not just *what* changed. It is ideal for writing meaningful commit history, preparing pull requests, or summarizing complex code changes for team collaboration.

This guide establishes the Conventional Branch specification for naming Git branches. It defines standardized prefixes (e.g., feature/, bugfix/, hotfix/) and enforces strict rules (lowercase, kebab-case, no underscores) to ensure consistency across development teams. Use it to validate, create, or understand the correct naming structure for any new branch, improving project traceability and collaboration.