Menu
Supplementary debugging methodology injected into stabilization feedback
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Planner skill — turn a user task into a precise, atomic, verifiable ShipCodePlan
Expert in application security, OWASP Top 10, authentication, authorization, data protection, and security best practices for React, Next.js, and NestJS applications. Use when implementing authentication or authorization, reviewing code for vulnerabilities, handling sensitive data, or implementing encryption or hashing.
Validate Biome 2.3+ configuration and detect outdated patterns. Ensures proper schema version, domains, assists, and recommended rules. Use before any linting work or when auditing existing projects.
Validate Bun workspace configuration and detect common monorepo issues. Ensures proper workspace setup, dependency catalogs, isolated installs, and Bun 1.3+ best practices. Use when setting up a Bun monorepo, before adding workspace dependencies, auditing an existing Bun workspace, or validating package.json in CI.
Expert React/Next.js component architect specializing in creating consistent, reusable, and maintainable components for monorepo projects. Use when creating or refactoring UI components, reviewing component architecture, or setting up shared component patterns in a monorepo.
Expert guide on prompt engineering patterns, best practices, and optimization techniques. Use when user wants to improve prompts, learn prompting strategies, debug agent behavior, or design content generation prompts.
| name | execution-debugging |
| description | Supplementary debugging methodology injected into stabilization feedback |
<debugging_methodology> <scope_constraint> These steps apply ONLY to diagnosing the failing check. Do not expand beyond the files touched in the original execution. Do not redesign, refactor, or improve code outside the failure path. </scope_constraint>
When a test or build fails during stabilization, follow this sequence:
READ the full error output — not just the last line. Stack traces, assertion messages, and build logs contain the diagnosis.
REPRODUCE the failure in isolation before changing anything.
HYPOTHESIZE explicitly before each change.
LOCALIZE — narrow the failure to the smallest possible scope.
FIX the root cause, not the symptom.
GUARD — write or update a test that fails without the fix and passes with it.
