What problem does it solve?
Improving a Slate v2 editor surface such as pagination, huge-document performance, or editor behavior requires coordinating many sub-workflows, and doing them in the wrong order risks shipping faster but broken behavior. This Skill provides a single high-level routing loop so the user does not need to manually pick and sequence sub-skills.
Core Features & Use Cases
- Goal Contract via Autogoal: Defines a durable goal naming the surface, measurable completion thresholds, acceptance rows, behavior and perf gates, boundaries, and a blocked stop condition.
- Ordered Skill Routing: Starts with slate-ar-status, then routes through slate-ar-quality, slate-plan, slate-patch, slate-ar-gate, and slate-ar-perf in a defined order, ending with a broad no-regression gate.
- Correctness-First Perf Policy: Blocks perf wins that regress native editor behavior and reroutes exposed correctness bugs to slate-patch before resuming perf work.
- Use Case: Ask to make huge-document performance genuinely good; the Skill audits current gaps, fixes known bugs, proves behavior with gates, runs benchmark-backed perf targets, and finishes with a no-regression check and a structured handoff report.
Quick Start
Ask the agent to use the slate-ar-perfect skill to make Slate v2 pagination genuinely good across quality, behavior, and performance.