slate-ar-stabilize

Stabilizes Slate editor behavior by running regression gates and routing repeated failures to fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Editor behavior regressions in Slate-based rich text editors—selection, typing, copy/paste, IME, focus, undo/redo, and navigation—are hard to eliminate because fixes often lack focused verification. This Skill runs existing behavior gates in a loop, routes repeated failures to patching, and keeps iterating until the behavior surface is stable.

Core Features & Use Cases

  • Behavior Gate Looping: Runs the narrowest existing behavior gate first, then broadens only after focused proof is green.
  • Failure Routing: Sends gates that fail twice to slate-patch for fixing, and creates missing test oracles via slate-patch or tdd.
  • Surface Inference: Infers the riskiest behavior surface from slate-ar-status and recent failing gates when none is named.
  • Use Case: A developer notices copy/paste regressions in a Plate editor. Invoke this Skill to run the paste behavior gate, patch repeated failures, and verify the fix with focused reruns before broadening coverage.

Quick Start

Ask the assistant to stabilize the copy/paste behavior surface in the Slate editor and keep iterating until the behavior gates pass.

Frequently Asked Questions about slate-ar-stabilize

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

FAQPage Schema
How do I fix Slate editor behavior regressions automatically?

Run the narrowest existing behavior gate for the affected surface, and if the same gate fails twice, route the failure to slate-patch for a fix. Rerun the focused gate after each fix and only broaden to the next gate once focused proof is green.

What editor behaviors does Slate stabilization cover?

It covers selection, typing, copy/paste, IME input, focus, undo/redo, navigation, browser route behavior, and native interaction parity. These are the behavior surfaces where regressions most commonly appear in Slate-based rich text editors.

When should I use slate-ar-stabilize instead of slate-ar-perfect?

Use slate-ar-stabilize as an expert override when you need behavior regressions gone quickly on a specific surface. The normal broad workflow is slate-ar-perfect, which stabilizes behavior before addressing performance.

What happens if no behavior gate exists for a regression?

If no oracle exists for the failing behavior, the workflow creates one using slate-patch or tdd before continuing. This ensures every known regression in scope ends up with a focused test.

When does the stabilization loop stop?

It stops when the named behavior gate is green repeatedly enough for the risk, known regressions have focused tests, and fixes are verified by focused commands. Performance work is not routed to until stabilization is green.