Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.
Create a self-contained GPT Pro or external-review prompt with full repo context, current state, evidence, and pointed review questions because the reviewer has no local file access.
Work heavyweight framework or library tasks with planning-first research, selective deep analysis, and rigorous handoff
Work a task end-to-end with lean context gathering, implementation, and verification
Create or update Plate docs with conversational voice, lane-aware structure, explicit ownership, and code-backed accuracy. North star is `docs/solutions/style.md`. Use for plugin pages, guides, install docs, serialization docs, API docs, and specs — anywhere both humans and agents need a clear, readable source of truth.
Command: docs-plugin
| description | Command: changeset |
| name | changeset |
| metadata | {"skiller":{"source":".agents/rules/changeset.mdc"}} |
Changesets document package changes for release. Concise bullets, imperative voice, user impact only.
Core principle: one action verb + one impact statement = one bullet.
Use when:
.changeset/*.md filesdocs/components/changelog.mdx for registry workDo not use for:
minorForbidden: minor changesets for:
@platejs/slate@platejs/coreplatejsUse patch instead. minor on those explodes version bumps across dependents.
# Wrong
---
"@platejs/core": minor
---
# Correct
---
"@platejs/core": patch
---
Only real breaking changes get major.
Never combine packages in one changeset.
# Wrong
---
'@platejs/core': patch
'@platejs/utils': patch
---
# Correct
.changeset/core-fix-types.md
.changeset/utils-add-helper.md
main, not to your thought processWrite changesets for the user-visible delta from the current main branch.
That means:
main need to knowDo not write:
If a package changed internally on this branch but has no user-visible delta from
main, do not write a changeset for that package.
If changes are only under apps/www/src/registry/, do not write a package changeset.
Update docs/components/changelog.mdx instead.
Use imperative voice:
Add support for XFix Y behaviorRemove deprecated ZDo not use:
Added ...We fixed ...Keep simple changes to one line:
- Fix `asChild` TypeScript error
- Add `disabled` prop to Button
Use code examples only when needed:
// Before
editor.api.foo();
// After
editor.tf.foo();
Focus on user impact only. No implementation diary.
Prefer this shape:
**Migration:** blockIf a sentence would sound stupid in release notes, cut it.
Simple:
---
"@platejs/utils": patch
---
Fix `isEmpty` not handling void elements correctly
API change:
---
"@platejs/core": patch
---
Rename `editor.api.foo` to `editor.tf.foo`
```tsx
// Before
editor.api.foo();
// After
editor.tf.foo();
```
Breaking change:
---
'@platejs/basic-nodes': major
---
Remove `SkipMarkPlugin`; functionality is built into core
**Migration:** Remove `SkipMarkPlugin` from your plugin list. Configure marks directly:
```tsx
MyMarkPlugin.configure({
rules: { selection: { affinity: 'outward' } },
});
```
Before shipping:
minor for @platejs/slate, @platejs/core, or platejs? Change to patchmain? Rewrite itFor apps/www/src/registry changes:
### [Month Day] #[Version]
- **`component-name`**: Brief description
- Migration note if actually needed
Same style rules: concise, imperative, user impact only.