skills.rest
udecode
udecodeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

plate-ui

Identify and codify Plate-specific shadcn-style UI components and registry wiring patterns.

16.5k|995|Updated Dec 2, 2019
Search Tags:#registry#shadcn#ui-components#open-code#component-authorship#plate
One-click install
npx skills add https://github.com/udecode/plate --skill plate-ui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plate-ui
Source: https://github.com/udecode/plate/tree/main/.agents/skills/plate-ui
Command: npx skills add https://github.com/udecode/plate --skill plate-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plate UI provides a disciplined approach to authoring and refactoring shadcn-style UI components for Plate, ensuring clear ownership, bundle boundaries, and registry wiring across surfaces.

Core Features & Use Cases

  • Aligns component authorship with Plate's registry rules to decide which UI artifacts belong in packages vs app-local code.
  • Guides base/live kit separation, registry wiring, and cross-surface collaboration for editor UI components.
  • Applies Plate-specific patterns to extract durable seams while preserving open-code and maintainability.

Quick Start

Identify and apply Plate UI patterns to scaffold or review a new or refactored registry UI component surface.

Frequently Asked Questions about plate-ui

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

FAQPage Schema
How do I structure Plate UI components to follow shadcn registry patterns?▼

Separate Plate UI components using a three-layer approach (semantic core, platform adapter, open UI) to decide what belongs in packages versus app-local files and how to wire registry surfaces, ensuring clear ownership and consistent boundaries.

What is the best way to separate base and live kits when authoring Plate editor components?▼

Apply Plate-specific patterns to guide base/live kit separation, registry wiring, and cross-surface collaboration for editor UI components, extracting durable seams while preserving open-code and maintainability across the component surface.

When should I extract shadcn-style UI components into packages instead of keeping them app-local?▼

Extract shadcn-style UI components into packages when governance signals and extraction criteria indicate durable, reusable seams, while keeping platform-specific or non-durable artifacts in app-local files to preserve open-code.

Can I use Plate UI patterns to refactor existing registry component surfaces?▼

Yes, Plate UI patterns support refactoring existing registry component surfaces by applying governance signals, open-code preservation rules, and extraction criteria to guide component work and ensure consistent ownership across surfaces.

Does Plate UI provide governance rules for component ownership and bundle boundaries?▼

Yes, Plate UI provides governance signals and open-code preservation rules that codify clear component ownership, bundle boundaries, and registry wiring patterns to ensure consistent and maintainable editor UI surfaces.

Why does my Plate registry wiring break when extracting components across different surfaces?▼

Registry wiring breaks when component ownership boundaries are unclear; Plate UI addresses this by applying a three-layer guidance model and extraction criteria to determine correct package versus app-local placement across surfaces.

Related Skills

Explore More Software Engineering Skills→
sahaja9707sahaja9707

shadcn-ui

Initialize and configure shadcn/ui projects with React components and Tailwind CSS.

Community
Intermediate
thehivegroup-aithehivegroup-ai

next-standards

Construct Next.js pages and layouts with Tailwind CSS conventions.

Official
Intermediate
mhintz1980mhintz1980

artifacts-builder

Scaffold React and TypeScript artifacts with Vite, Tailwind CSS, and shadcn/ui.

Community
Advanced
ever-worksever-works
21

shadcn

Manage shadcn UI components and generate source code from project configurations.

Official
Intermediate