Reproduce user symptoms with a failing test before fixing UI state bugs.
npx skills add https://github.com/panamini/pi-tooling --skill debug-red-first
Please help me install this Agent Skill. Skill: debug-red-first Source: https://github.com/panamini/pi-tooling/tree/main/skills/debug-red-first Command: npx skills add https://github.com/panamini/pi-tooling --skill debug-red-first
It prevents teams from “guess-fixing” unstable UI and state issues by requiring a concrete failing reproduction that matches the exact user symptom before any product change.
Run the debug pass by defining the exact user symptom and its user invariant, writing one RED failing test that reproduces it on current code, then applying only a minimal fix and re-running guard-rail tests plus a short manual smoke check.
High-intent search queries and answers about installing and using this skill.
Fix inconsistent UI bugs by first defining the exact user symptom and one user-facing invariant, then writing a single RED failing test that reproduces the symptom on current code before applying any product change. This prevents guess-fixing unstable state issues.
Reproduce flickering UI state jumps by locking the debug pass to one exact user symptom and writing a failing test that triggers the state jump on current code. You must verify the test truly fails before proceeding with a minimal fix along the shared path.
Stop guess-fixing unstable UI state issues by requiring a concrete RED reproduction test that matches the exact reordering symptom. Apply only a minimal fix along the smallest responsible shared source-of-truth path, then re-run guard-rail tests and a short smoke check.
You should not apply local UI tweaks before writing a failing test. The workflow requires prioritizing shared source-of-truth and shared load/switch paths for minimal fixes only after a RED test reproduces the exact user symptom on current code.
UI tests pass while real user behavior fails when tests do not cover the exact user symptom or invariant. The workflow solves this by requiring one RED failing test that precisely reproduces the user-facing symptom before any fix is applied.
Yes, this debugging workflow explicitly applies to scenarios with flicker, reordering under cursor, and state jumps across multiple surfaces. It requires symptom definition, a RED reproduction test, a minimal shared-path fix, and verification with adjacent guard rails.
sQVeDiagnose bugs by tracing evidence and generating a BR issue template.
jmaglyValidate phase-gate criteria and generate pass/fail gate reports.
GambitnlSorry, I can't answer that.
mwayEnforces test-first discipline for production code changes.
