editor-spec
Editor Spec
Handle $ARGUMENTS. This is the repo workflow for turning editor-behavior ideas or changes into real Plate law instead of chat sludge.
#$ARGUMENTS
Core Rules
- Evidence first. Vibes are not authority.
docs/researchfeedsdocs/editor-behavior. Do not collapse those jobs.- Treat silence as a gap, not fake agreement.
- Lock node model and affinity before UX chrome.
- Any UI/editor-chrome spec should follow $build-web-apps:shadcn patterns for popovers, commands, menus, triggers, truncation, composition, and semantic styling. Do not invent one-off overlay markup when the shadcn path already exists.
- Update the smallest number of docs that keeps the stack honest. Do not let
More from udecode/plate
code-simplicity-reviewer
Final review pass to ensure code is as simple and minimal as possible. Use after implementation is complete to identify YAGNI violations and simplification opportunities.
59vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
45grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
36frontend-design
Build web interfaces with genuine design quality, not AI slop. Use for any frontend work - landing pages, web apps, dashboards, admin panels, components, interactive experiences. Activates for both greenfield builds and modifications to existing applications. Detects existing design systems and respects them. Covers composition, typography, color, motion, and copy. Verifies results via screenshots before declaring done.
33git-history-analyzer
Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist. Use when you need historical context for code changes.
32best-practices-researcher
Researches and synthesizes external best practices, documentation, and examples for any technology or framework. Use when you need industry standards, community conventions, or implementation guidance.
32