Skill UI

Structured incident handling runbook that walks on-call engineers through CodeRabbit outage triage, mitigation commands, communication templates, and postmortem evidence gathering for integration failures.

Guided Documenso production deployment checklist covering pre-deploy checks, deployment steps, rollback actions, post-verification, and resource links to support go-live readiness and failure handling.

This skill guides the implementation of robust and resilient error handling strategies across applications. It covers techniques like implementing retry mechanisms, circuit breakers, and managing asynchronous errors. Use this when designing fault-tolerant APIs, improving application reliability, and guiding debugging processes in production environments to ensure graceful failure.

Guides developers through identifying, diagnosing, and fixing the most frequent Langfuse SDK errors—from auth failures to missing traces—by offering command snippets, trace handling tips, and environment checks for reliable integrations.

Guides responders through diagnosing, resolving, and reviewing Langfuse platform incidents, covering quick triage, incident-type lookup tables, resolution steps, post-mortems, escalation contacts, and error handling for outages, auth failures, and missing traces.

Implement graceful handling of Lokalise API rate limits by queuing requests, applying exponential backoff and monitoring headers so retry logic, throughput optimization, and failure recovery can coexist without overwhelming the service.

Guides you through diagnosing Next.js getServerSideProps, getStaticProps, and API route failures by checking terminal logs, adding explicit try-catch handling, and reviewing hosting logs or common causes like env vars, DB, or serialization issues.

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.