Loading...
Loading...
Found 1,733 Skills
Apply when something fails: a bug, a red check, a flaky test, or an agent that goes in circles.
For executable behavior, including a bug fix with a known cause, run a test that fails for the missing behavior before changing production code; preserve scope. Low-impact copy, styling, or config-value edits need existing checks, not new tests. Load for non-trivial implementation, test-boundary choices, or refactoring risks, not mechanical edits or settled red/green loops. Diagnose unknown causes first.
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
Debug Rails issues systematically. Use when encountering ActiveRecord errors like RecordNotFound, routing issues, N+1 query problems detected by Bullet, asset pipeline issues, migration failures, gem conflicts, ActionController errors, CSRF token problems, or any Ruby on Rails application errors requiring diagnosis.
Provide comprehensive context in prompts—files, errors, Laravel version, dependencies, and monorepo details—for accurate AI responses