Skill UI

This skill acts as a rigorous, Socratic interviewer designed to stress-test a proposed plan against an established domain model and existing project documentation. It forces the user to sharpen terminology, resolve cross-cutting dependencies, and identify inconsistencies between stated requirements, code implementations, and documented decisions. It ensures the resulting architecture is precise, consistent, and well-documented by automatically updating the context and generating Architecture Decision Records (ADRs).

A comprehensive diagnostic guide for common ElevenLabs API errors, organized by HTTP status code. It provides detailed causes, fixes, and troubleshooting steps for issues such as invalid API keys (401), quota exhaustion, exceeding character limits (400), and rate limiting (429). Essential for developers debugging TTS, voice cloning, or streaming requests.

A comprehensive diagnostic bundle designed to troubleshoot Fathom API connectivity, meeting sync failures, transcript availability, and authentication issues. It collects key data points (such as API status codes, rate limit headers, and meeting metadata) into a single archive, simplifying the process of diagnosing integration failures for support teams.

This skill provides comprehensive guidance and solutions for diagnosing and fixing common technical errors and exceptions encountered when integrating with the Grammarly API. It covers specific HTTP error codes (400, 401, 413, 429), addressing issues such as invalid tokens, payload size limits, rate limit exhaustion, and text formatting requirements. Use it when debugging failed API requests or troubleshooting complex integration workflows.

A comprehensive guide for diagnosing and fixing common HubSpot API errors (e.g., 401, 403, 429, 400). It provides real error response bodies, root cause analysis, and actionable code solutions for debugging failed API requests, improving integration reliability, and managing complex CRM interactions.

This skill orchestrates the entire development lifecycle for approved software tasks. It operates in autonomous or manual modes, rigorously applying Test-Driven Development (TDD). It automatically gathers all necessary context (specs, requirements, design, and historical learnings), validates the repository state, and dispatches specialized sub-agents to implement tasks one by one, ensuring high code quality, adherence to design, and process traceability.

This utility analyzes a codebase (product, technology, and structure) to automatically extract core architectural patterns, guiding principles, and engineering standards. It manages a persistent 'Steering' repository, performing initial bootstrapping and continuous synchronization. It detects 'code drift' when the code deviates from established patterns and suggests additive updates, ensuring project documentation remains a comprehensive source of truth.

This comprehensive guide serves as a quick reference for diagnosing and fixing common Klaviyo API errors and SDK exceptions. It provides detailed root causes and solutions for standard HTTP status codes (400, 401, 403, 429, etc.) and common coding pitfalls. Ideal for developers integrating Klaviyo into their applications.

This guide details migrating outdated and unsafe `as` type assertions in TypeScript test files. It introduces `@total-typescript/shoehorn`, which provides type-safe functions like `fromPartial()` and `fromAny()`. Use this utility when unit tests need to mock large objects or pass only a subset of required data, thereby maintaining strict type checking and improving test robustness. Note: This is strictly for test code.

This comprehensive guide is designed for developers and system administrators to diagnose and resolve common integration errors encountered when interacting with the MindTickle API. It covers critical areas such as authentication failures (401, 403), rate limiting, SCIM provisioning conflicts, and content access issues. The document provides explicit error codes, underlying causes, and actionable fixes, ensuring stable and seamless platform integration.

A comprehensive technical guide for diagnosing and resolving common Miro REST API v2 errors. It details specific HTTP status codes (400, 401, 403, 404, 429, etc.), providing common causes, actionable fixes, and best practices for token refreshing, scope management, and achieving stable API integration.

A comprehensive guide for developers on installing and configuring the official @mirohq/miro-api Node.js client. This skill provides step-by-step instructions for setting up the full OAuth 2.0 authorization code flow, managing client credentials, and implementing token refresh patterns to ensure secure and reliable access to the Miro REST API v2. Use this when building automated applications or integrating Miro features into a custom backend service.