What problem does it solve?
Downstream apps that copy and customize Plate UI registry components end up with mixed-ownership files, making it unsafe to blindly overwrite them with upstream updates. This Skill performs a three-way sync (base, upstream, local) that classifies every hunk as upstream-owned or target-owned, so Plate bugfixes land without destroying local product forks.
Core Features & Use Cases
- Three-Way Classification: Compares base, upstream Plate source, and local target files at hunk or symbol level, labeling each as upstream-only, local-only, same-change, conflict, or unknown-base.
- Plan, Review, Dashboard, Apply Modes: Generates reviewable sync plans and dashboards under the target repo's
.plate-ui-sync/ directory, then applies only user-accepted rows.
- Fork Ledger and Status Tracking: Records fork decisions, applied PRs, and source hashes in
status.json so sync state survives context loss and can be resumed.
- Use Case: A team maintaining a Notion-like app (e.g., Potion) that copied Plate UI components wants to pull the latest
code-block-node fixes from the Plate changelog while keeping its custom toolbar styling intact.
Quick Start
Ask the assistant to run sync-plate-ui plan for a target repo and component, for example: sync-plate-ui plan ../potion code-block-node.