What problem does it solve?
Slate v2 editor bugs (selection, focus, history, clipboard, IME, rendering) often get fixed with narrow local patches that mask systemic issues. This Skill enforces a disciplined one-pass workflow that reproduces the bug, adds behavior-level regression tests, fixes the true owning layer, and challenges the patch with architecture pressure before handoff.
Core Features & Use Cases
- Structured Bug-Fix Workflow: Reproduce the bug in
.tmp/slate-v2, classify the bug class, write a failing behavior test (Playwright or package tests), then fix the correct owner in the package/runtime rather than patching examples.
- Architecture Pressure Review: After a green patch, a harsh maintainer-style checklist evaluates architecture, API/DX, performance, data model, and simplicity, with verdicts of keep, rework, or escalate to planning.
- Repair Command: Invoke
slate-patch repair <expectation> to update the workflow rules themselves when recurring proof or handoff standards are missed.
- Use Case: A user reports that Shift+Arrow selection breaks across hidden DOM boundaries in a Slate v2 editor. The Skill reproduces it on the real route, adds a selection-navigation matrix test, fixes the core selection owner, runs verification gates, and finishes with autoreview.
Quick Start
Ask the agent to run slate-patch on your Slate v2 bug report, including the route or failing test and the expected behavior.