pixsaur

Build a NEW vertical slice (use-case + ports + pure core) OUTSIDE-IN — start from the consumer's need (a use-case / acceptance test), let it pull the domain into existence, then wire the adapter. Use when adding a genuinely new feature capability. For carving an EXISTING component/atom into a use-case, use extract-use-case instead.

Run the pixsaur quality guardrails (typecheck + comprehensive typecheck + biome & custom guards + tests with coverage + knip dead-code + jscpd duplication + Stryker on the pure core) and report. Use before declaring any change done, before a commit, or before opening a PR. Unlike a greenfield gate, pixsaur is a mature codebase mid-refactor — some detectors are ratcheted (report-only baseline), not zero-tolerance. Know which is which before you act.

Use when finishing a feature, fixing a bug, before committing React code, or when the user types `/doctor`, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.

React component and hook testing idiom for pixsaur (Testing Library + Vitest + happy-dom). Use when writing or reviewing any *.spec.tsx — component rendering, user interaction, async assertions, renderHook. Complements tdd-cycle (which owns red-green-refactor); this skill owns HOW the React tests are written in this repo.

Close a refactor step with a resumable session report. Use at the end of every step/PR of the clean-archi refactor so a fresh session can pick up exactly where this one left off. Updates the canonical docs/refactor/STATUS.md and appends a dated report under docs/refactor/sessions/.

Drive a change through strict red-green-refactor TDD. Use for ANY change to the pure core (src/libs/** and src/domain/**) or any pure logic — write the failing test first, the minimal code to pass, then refactor under green. Enforces one-assertion-per-test and triangulation.

Strangler-fig recipe to extract business orchestration out of a React component or Jotai atom into a pure, testable use-case with light ports. Use when refactoring a feature toward the use-cases + ports architecture (see docs in src/<feature>/application/README.md). Forces reuse of existing ports and deletion of the old code path — no parallel duplicates.

Run the refactor guardrails (typecheck + knip dead-code + jscpd duplication) and report before opening a refactor PR. Use after extracting a use-case or before pushing any strangler-fig refactor branch, to confirm no dead code lingers and no copy-paste was introduced.