editor-spec

Define or update editor behavior specs using the research-to-law workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define or update editor behavior specs using the full Plate research-to-law pipeline. Use for both new and existing editor behavior work: adding behavior rules, changing locked law, introducing new interaction families, revising winner maps, shifting authority lanes, updating protocol rows, or changing parity-gate coverage.

Core Features & Use Cases

  • Guide end-to-end spec development from research to law across standards, readable law, protocol rows, parity, and audit.
  • Enforce disciplined collaboration by locking node models and declaring ownership rules before UX changes.
  • Provide a repeatable workflow for updating or introducing editor surfaces, lanes, and governance.

Quick Start

Provide a topic or spec path and the skill will translate it into formal editor-behavior law using the research-to-law workflow.

Frequently Asked Questions about editor-spec

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

FAQPage Schema
How do I define editor behavior specs using a formal pipeline?

To define editor behavior specs, apply the research-to-law workflow to translate topics into formal law across standards, readable law, and protocol layers, enforcing node-model locking and governance updates.

What is the research-to-law workflow for updating editor behavior rules?

The research-to-law workflow is a formal pipeline for updating editor behavior rules, ensuring disciplined collaboration by locking node models and declaring ownership rules before introducing new interaction families or changing locked law.

How do I update parity coverage and protocol rows for editor behavior?

Update parity coverage and protocol rows by applying the research-to-law workflow to shift authority lanes and update the protocol matrix, using the research-wiki as the authoritative source for editor behavior specs.

Can I change locked law and winner maps for existing editor surfaces?

Yes, you can change locked law and revise winner maps for existing editor surfaces by routing updates through the research-to-law pipeline to enforce reading lists and governance protocol updates.

Do I need to declare ownership rules before changing editor behavior specs?

Yes, declaring ownership rules and locking node models is required before changing editor behavior specs to enforce disciplined collaboration across standards, readable law, and protocol layers.

When should I use a formal spec pipeline for editor behavior changes?

Use a formal spec pipeline when adding behavior rules, introducing new interaction families, or updating parity-gate coverage to ensure governance, node-model locking, and protocol-matrix updates across editor surfaces.