slate-patch

Fixes Slate v2 editor bugs with reproduction, regression tests, architecture review, and autoreview.

16.5k|997|Updated Dec 2, 2019
One-click install
npx skills add https://github.com/udecode/plate --skill slate-patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slate-patch
Source: https://github.com/udecode/plate/tree/main/.agents/skills/slate-patch
Command: npx skills add https://github.com/udecode/plate --skill slate-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about slate-patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a Slate v2 editor bug with regression tests?

Invoke slate-patch with the bug report, route, or failing test. It reproduces the issue in .tmp/slate-v2, adds a failing behavior-level test using Playwright or package tests, fixes the owning package layer, and verifies with focused gates.

What is the difference between slate-patch and slate-plan?

slate-patch is the implementation lane that fixes bugs now with tests and review. slate-plan handles architecture proposals and multi-pass public API decisions; slate-patch escalates to it when the clean fix requires a broader design decision.

Does slate-patch cover selection and keyboard navigation bugs?

Yes. It uses a selection-navigation coverage matrix spanning command family, direction, topology, and starting state, including hidden DOM, multi-root, void roots, and materialize selection policies, before writing the regression test.

When should I not use slate-patch?

Avoid it for pure architecture planning (use slate-plan), normal diff reviews (use autoreview), non-Slate-v2 targets, or performance-only loops with an existing correctness oracle (use slate-ar-perf).

What does the slate-patch repair command do?

Running slate-patch repair <expectation> updates the workflow rules in .agents/rules/slate-patch.mdc so future runs meet a missed recurring standard, then regenerates the skill with pnpm install and proves the change with rg searches.