Loading...
Loading...
Found 22 Skills
Run Patrol E2E integration tests on macOS, iOS, Android, or Chrome. Use when writing, running, or debugging Patrol tests.
This skill should be used when encountering bugs, errors, failing tests, or unexpected behavior. Provides systematic debugging with evidence-based root cause investigation using a four-stage framework.
Scientific method expert for systematic bug investigation and root cause analysis. Use when users report bugs, crashes, unexpected behavior, or debugging requests. Applies hypothesis-driven investigation, controlled experiments, and rigorous validation across any programming language or platform.
Resolves React hook violations (rules of hooks, useEffect dependencies, hook ordering).
Interactive debugging mode that generates hypotheses, instruments code with runtime logs, and iteratively fixes bugs with human-in-the-loop verification. Only for hard-to-diagnose bugs; in those cases, remind the user that debug-mode is available, and never proactively activate this skill.
Use when working with debugging toolkit smart debug
Executes browser workflows while monitoring JavaScript console for errors, warnings, and messages. Use when you need error-free validation, debugging context during automation, or proactive error detection in web applications. Triggers on "check for console errors", "monitor JavaScript errors", "validate error-free execution", or "debug browser workflow". Works with Playwright MCP browser automation tools.
ALWAYS LOAD THIS SKILL when: something doesn't work as expected, documentation is unclear, need to understand library internals, debugging integration issues, or before making assumptions about how a library works. Contains opensrc repo paths, debugging workflows, and examples for Effect, TanStack, TRPC, Drizzle, Better Auth, OpenCode.
Search Sourcegraph-indexed codebases for patterns, examples, and system understanding. Triggers on implementation questions, debugging, or "how does X work" queries.
The orchestrator and entry point for the engineering skills suite. Use this skill whenever the task involves doing engineering work to a high bar — reviewing code or a design, designing a new system or component, debugging a hard problem or running an incident, implementing a substantive change, writing documentation, or sanity-checking an approach. Use it when the user phrases things casually ("rip into this", "be brutal", "is this approach right", "what am I missing", "what would you change", "look at this") or formally ("review this PR", "audit this design"). Use it proactively for any non-trivial engineering work, before declaring something done. The skill triages the work, dispatches to the right specialty skill(s), enforces verification, and produces an evidence-backed result. The goal is to ensure no AI shortcut, sycophantic agreement, or stylistic distraction gets in the way of work that holds up to senior-engineer scrutiny.