Skill UI

This guide provides a comprehensive reference for diagnosing and fixing common errors and exceptions encountered when interacting with the Perplexity Sonar API. Use this when troubleshooting API integration issues, handling specific HTTP status codes (like 401, 429, 402), or debugging failed requests. It covers best practices for rate limiting, key validation, and implementing robust error handling logic.

This comprehensive guide serves as a quick reference for diagnosing and fixing the most common technical errors encountered in the Replit development environment. It covers critical infrastructure issues such as container lifecycle failures, port binding conflicts, Nix build failures, database limitations, and deployment timeouts, ensuring users can effectively troubleshoot and maintain continuous development workflows.

This skill simulates an autonomous, overnight development cycle by leveraging Git hooks to enforce Test-Driven Development (TDD). It ensures that all code changes, whether building new features, refactoring, or fixing bugs, are rigorously tested and meet high quality standards before commitment. Use this when high code reliability and comprehensive testing are critical requirements.

Guidance for Spring Boot TDD covering JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo and coverage enforcement, ideal for adding endpoints, fixing bugs, or refactoring with high confidence.

A comprehensive diagnostic guide for resolving common errors across the entire Supabase stack, including PostgREST, PostgreSQL, Authentication, and Storage. Use this tool when encountering specific error codes (e.g., PGRST301, 42501) or debugging complex API failures like RLS violations or session expiry. It provides step-by-step instructions for identifying the error layer and applying the correct fix.

This skill provides a systematic, multi-step approach to identify and resolve all failing unit tests within a codebase. It guides the user through smart error grouping (e.g., grouping by ImportError or AttributeError), prioritizing fixes from infrastructure to business logic, and ensuring thorough verification to prevent regressions. Ideal for use after major refactoring, debugging CI/CD failures, or when explicitly tasked with making the test suite pass.

A systematic protocol for repairing broken features by scoping the module, tracing every dependency, diagnosing issues, fixing them, and verifying results—ideal when a feature needs end-to-end debugging rather than a quick patch.

This skill manages comprehensive software development life cycle operations—including issue triage, PR reviews, version releases, bug fixing, and marketing content generation. It operates using a parallel "agent army" of dynamic agents (10-20 per task), requiring the user to adopt an Engineering Manager (EM) mindset. Key principles involve rigorous citation checking (anti-hallucination) and applying multiple roles (Product Owner, Open Source Contributor, Architect) simultaneously to ensure robust, safe, and user-centric outcomes across all platforms.

A comprehensive guide for systematically diagnosing and fixing bugs, crashes, deadlocks, and performance issues in Go code. It covers debugging methodology, utilizing tools like Delve and pprof, detecting race conditions, and following the Golden Rules to find the root cause, ensuring robust and reliable Go development practices.

Test-Driven Development (TDD) is a software development process where tests are written before the actual implementation code. The core cycle involves three steps: RED (write a failing test), GREEN (write minimal code to pass the test), and REFACTOR (clean up the code while ensuring tests remain passing). This methodology is crucial for building robust, maintainable, and bug-free codebases, making it ideal for implementing new features or fixing bugs.

This guide outlines a mandatory, evidence-based protocol for declaring any work complete, fixing a bug, or submitting a pull request. It strictly mandates that all claims of success must be supported by fresh, verifiable evidence, such as passing test outputs, successful build logs, or comprehensive checklist verification. It eliminates reliance on assumptions, gut feelings, or trusting proxy reports.

This guide provides a quick reference for diagnosing and fixing common errors encountered when using the Intercom API. It details specific HTTP status codes (e.g., 401, 404, 429), their root causes, and actionable solutions, including code snippets for secure API interaction and implementing backoff logic for rate limiting. Essential for developers troubleshooting integration failures.