plate

Check that deciding the authored review tree's pending changes one at a time, in any order, gives the document that deciding them all at once gives, and that no change adds a set of verdicts a reviewer can only decide together, for every document up to a bound. Use before and after changing packages/plitejs/src/authored/tree/resolve.ts or another file in its coverage record, when the authored-order step of pnpm check fails, when fixing a decision-order bug, or when recording gains a new kind of mark.

Check that every command the recording laws use, run at every place in Suggesting and in Editing on every small document with another author's pending change, records a document whose accept-everything result is what a plain editor gives, whose reject-everything result is the document before, whose undo and redo give back each side, and whose review ledger matches the kernel. Use before and after changing packages/plitejs/src/authored or packages/plitejs/src/history or another file in its coverage record, when the authored-recording step of pnpm check fails, or when fixing a recording bug a seed or a tester found.

Check that every shorthand the www autoformat and basic marks kits declare applies whole when typed key by key, that no typed sequence of up to three keys changes a paragraph it was not typed in, that one undo takes back each keystroke that fires a rule, and that a key an input method commits gives what typing it gives. Use before and after changing apps/www/src/registry/components/editor/autoformat.tsx, basic-marks.tsx or another file in its coverage record, when the autoformat-rules step of pnpm check fails, or when fixing an autoformat or input-rule bug.

Measure and repair Plate/Plite performance, or review a performance design before running its applicable benchmark lanes. Use before writing, reviewing, running, rerunning, checking, skipping or deferring a performance gate, including a plan's scale gate, before writing a benchmark script, before explaining a benchmark result or failure, and when a review or panel finds a latency or scaling cost.

Design, review or repair a Plate or Plite public call shape with the Plate API lens.

One-time setup for a persistent debug browser on `127.0.0.1:9222` for `dev-browser --connect`. Use when browser work is needed but no reusable debug browser is running yet.

One-time setup for a persistent debug browser on `127.0.0.1:9222` for `dev-browser --connect`. Use when browser work is needed but no reusable debug browser is running yet.

Write and verify package release changesets, registry changelog entries, and the PR’s managed auto-release choice. Use before deciding whether a package edit needs a changeset, including skipping one.

Run the project's suggested-task ledger, the chips. /chips alone brings this session's open tasks up to date: it applies what the ledger helper says, settles stale and split tasks, cards what can start and reports the board, and /chips all also takes the ship-list tasks and the ones no live session owns, and merges duplicate tasks across the board. Use for /chips, /chips offer, start or drop, "what chips are open", "suggest a task for X", "update the chips", "clean up the chips", "which chips are stale", "is this chip still worth doing", "merge duplicate chips", at the last hand-back of a run that offered a task, and whenever pstack would file a tracked issue, a follow-up, a reflect Backlog item or an out-of-band PR.

Free disk in a project by removing the git worktrees and Next.js cache folders nothing uses, keeping every worktree a session or process works in and every cache a running server holds. Use for /cleanup, "clean up worktrees", "free disk space", "what's using my disk", "delete unused worktrees or builds", or when a session-start hint counts old cleanup candidates.

React component architecture for creating composable, accessible components with data attributes. Use when creating/updating composable components, not for higher-level feature/page components.

React component architecture for creating composable, accessible components with data attributes. Use when creating/updating composable components, not for higher-level feature/page components.

Bring a branch that predates next's agent rules up to date once, then fix the bodies of your open PRs into next. Use when the PR body check fails or when an agent opened a PR into next by hand.

Check that Backspace, Delete, Return, typing, paste, cut and bold keep the text outside their range in order over every caret and range of every small document, with a link, a read-only inline, a required title and a one-text code block among them, that the result stays canonical and that one undo gives back the document. Use before and after changing packages/plitejs/src/transforms-text/delete-text.ts, merge-nodes.ts, slice landing or another file in its coverage record, when the delete-paste-ranges step of pnpm check fails, or when fixing a delete, join or paste bug a tester found.

Maintain exhaustive Slate/Plate issue-closure ledgers from current issue, PR, test and local proof evidence.

Handle public Plate/Slate GitHub work, such as issue drafts, Slate issues, PRs, security and the queue scan, and hold the public truth gate. Triage of udecode/plate and udecode/plate-private issues runs the Triage playbook.

Check that every small Markdown source parses, serializes and parses again to the same document, and that a streamed parse that continues its previous result equals a fresh parse at every chunking, over the plugins of the Markdown test editor. Use before and after changing packages/platejs/src/markdown/lib or another file in its coverage record, when the markdown-round-trip step of pnpm check fails, or when fixing a Markdown or streaming bug a seed or a tester found.

Send a Discord message as plate-bot to a teammate or the dev role in the team channel, in the team's house style. Use for /notify, for telling or pinging a teammate, for answering a teammate's pasted Discord message, and for every team message a playbook or rule has a session send, such as a retest notice.

Write, check, repair and publish a plan page: a project's plans and subject files under its plans directory, rendered by .agents/pstack/plan-page.mjs and rendered as one local HTML page per subject with a local index of every subject, and published to claude.ai at each hand-back for comments and feedback. The page is how planned work hands back to the user. Use before writing or changing a plan, a subject file in <plans>/topics or its page; at every stop that hands back work with a plan, such as a review verdict other than a review-only panel's, a next answer or a playbook's close; before writing or updating a PR body, which renders from the PR's plan, or a comment about your commits on someone else's PR; when a plan page or its claude.ai artifact looks wrong or refuses to render; to republish a page; or to change the page shape or a playbook's page sections.

Use before any edit under content/docs, including a one-line fix to existing advice, a Chinese twin or an embedded demo, and to write or audit Plate public documentation, page design, examples, installation, MDX and navigation.