slate-ar-perfect

Orchestrates multi-stage improvement of Slate v2 editor surfaces across quality, behavior, and performance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about slate-ar-perfect

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

FAQPage Schema
How do I improve a Slate v2 editor surface end to end?

Invoke this Skill with a surface name such as pagination or huge document. It creates an autogoal contract, audits current gaps, fixes known bugs, proves behavior with gates, runs perf targets, and finishes with a broad no-regression check.

What is the routing order for Slate editor improvement work?

Start with slate-ar-status, then slate-ar-quality for gap analysis, slate-plan for public API design, slate-patch for known bugs, slate-ar-gate for behavior proof, slate-ar-perf for benchmarks, and slate-ar-gate again for final no-regression proof.

Can performance work proceed before editor behavior is stable?

No. Perf waits for behavior stability unless the benchmark is the only way to reproduce a behavior failure. If perf work exposes a correctness bug, it routes to slate-patch, the bug is fixed, and only then does the perf target resume.

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

Use it when a whole surface must be made genuinely good rather than one isolated packet fixed. The fast and stabilize lanes are internal or expert overrides and should not need manual invocation after this Skill runs.

Does this workflow create review branches automatically?

No. Work stays on the source branch, normally v2, and uses slate-ar-ship readiness previews. Review branches under autoresearch-review are only created when the user explicitly asks for them.