Skill UI

Applies Anthropic’s official color palette, typographic hierarchy, and accent system to any artifact that needs the company’s visual identity, ensuring consistent styling across materials with smart fallbacks for system fonts.

Helps designers explore trending Coolors palettes, capture hex codes, and map selections into Tailwind configs or curated fallbacks when the browser is unavailable, ensuring contrast and role guidance for frontend themes.

This guide provides technical patterns for building fault-tolerant integrations with Customer.io. Learn to implement critical resilience techniques, including Circuit Breakers to prevent cascading failures, Retry with Jitter for handling transient errors, and Fallback Queues (using Redis) to ensure data continuity during service outages. Essential for robust, production-grade applications.

A comprehensive runbook for standardizing incident response to Deepgram production issues. It guides users through automated triage (checking status, API connectivity, and model performance), severity classification (SEV1-SEV4), and implementing mitigation strategies, including building fallback services and replaying failed requests to ensure business continuity during outages or degradation.

This guide details the implementation of real-time synchronization for Evernote notes. It utilizes Evernote webhooks to detect changes (creation, updates, deletions) and pairs this with the Sync API to reliably fetch the actual data chunks. The process covers setting up webhook endpoints, managing sync state (USN), ensuring idempotency, and establishing a robust polling fallback mechanism for continuous data synchronization.

This skill provides robust, production-grade patterns for building fault-tolerant search service integrations, specifically targeting Exa. It covers implementing query fallback chains, circuit breakers to prevent cascading failures, exponential backoff for retries, and graceful degradation levels. Use this when designing mission-critical search features that must remain available and functional even if underlying services fail, rate limit, or suffer performance degradation.

A comprehensive runbook providing systematic procedures for responding to Firecrawl API outages and integration failures. It guides technical teams through triage, diagnosis, and mitigation for common issues (e.g., 401, 429, 5xx errors). Includes steps for fallback implementation, evidence collection, and postmortem documentation to ensure rapid service recovery.

A comprehensive guide to implementing production-grade reliability patterns for web scraping pipelines using Firecrawl. Learn techniques such as circuit breakers, crawl fallbacks, content quality validation, and robust backoff strategies to handle timeouts, API failures, and inconsistent data quality, ensuring maximum uptime and data integrity.

This comprehensive runbook guides incident response for Groq API failures. It covers triage steps, severity classification (P1-P4), troubleshooting decision trees (e.g., handling 429 errors or 5xx outages), and implementing immediate mitigations like model fallback or key rotation. Use this when responding to Groq outages to restore service stability.

A comprehensive checklist for deploying Groq-powered applications to production. It covers critical areas including secure API key management, model fallback strategies, rate limit planning, implementing robust error handling (e.g., circuit breakers), setting up health endpoints, and configuring detailed monitoring and spending controls necessary for a successful, stable go-live.

This guide details a production-ready reference architecture for applications built on Groq's LPU inference API. It covers sophisticated model routing based on latency, quality, or cost needs, implementing streaming pipelines, and establishing robust multi-provider fallback chains (e.g., Groq primary to OpenAI backup). Ideal for designing and reviewing complex, resilient LLM systems.

A comprehensive runbook for rapid incident response concerning Ideogram API outages, authentication failures, and performance degradation. It provides detailed triage scripts, decision flows based on HTTP status codes (401, 429, 5xx), immediate mitigation actions (e.g., enabling fallback mode), and structured templates for communication and postmortems.