plaited-ui
Build and test Plaited's server-driven UI stack. Use when working on `src/ui`, the controller protocol, custom elements, dynamic behavioral loading, SSR, or the UI test strategy.
What this skill does
# Plaited UI ## Purpose This skill is the unified entrypoint for Plaited's UI stack. Use it when you need to: - build or change `src/ui/` - work on server-driven rendering through the controller protocol - design `controlDocument` or `decorateElements` flows - add dynamic client behavior through `update_behavioral` - test UI behavior from schema-level checks up through real browser flows **Prerequisite:** use `behavioral-core` when the change depends on BP semantics rather than the UI surface itself. ## Structural Overview `src/ui/` is split into four subsystems: | Subsystem | Key APIs | Primary Reference | |---|---|---| | Rendering pipeline | `createTemplate` / `h`, `Fragment`, `createSSR` | `references/server-pipeline.md` | | CSS system | `createStyles`, `createTokens`, `createHostStyles`, `createKeyframes`, `joinStyles` | `references/css-system.md` | | DOM/custom elements | `controlDocument`, `decorateElements`, `DelegatedListener` | This skill + `references/server-pipeline.md` | | Controller protocol | `render`, `attrs`, `update_behavioral`, `disconnect`, `user_action`, `snapshot` | `references/update-behavioral.md`, `references/websocket-decisions.md` | Public UI exports are re-exported through `src/ui.ts`. ## Quick Start 1. Start from the protocol and rendering shape, not ad hoc DOM mutation. 2. Use `p-target` for server-addressable update points. 3. Use `p-trigger` for browser-to-server event wiring. 4. Use `update_behavioral` for post-load client logic. 5. Pick the smallest test layer that matches the change. ## Rendering Model Plaited UI is server-driven: - the server/agent produces JSX templates - `createSSR()` turns templates into HTML strings - the browser controller applies `render` and `attrs` messages - BP coordinates client behavior and snapshot reporting Important rules: - JSX produces template objects, not DOM nodes - styles are collected at template creation time and deduplicated per connection - inline event handlers are not the pattern here; use `p-trigger` - dynamically rendered `<script>` tags do not execute - `update_behavioral` is the supported path for loading new client logic ## Dynamic Behavioral Loading `update_behavioral` is the UI system's runtime code-loading boundary. The flow is: 1. server sends a module URL 2. client `import(url)` loads it 3. module exports one or more `useExtension(...)` values 4. client installs each exported extension where `isExtension(value) === true` 5. unknown server-originated event types are dropped and reported (allowlist inbound wire events only) Loaded modules participate in local coordination through the scoped UI core event lane (for example `ui_core:user_action`) without direct server-triggered local handler bypass. See: - `references/update-behavioral.md` - `references/websocket-decisions.md` ## Testing Strategy Use three layers: | Layer | Use For | Runner | |---|---|---| | Pure function | schemas, constants, transforms, CSS utilities | `bun test` | | DOM unit | custom element registration, module return shape, template structure | `bun test` with happy-dom | | Real browser | WebSocket roundtrips, swap behavior, dynamic imports, real DOM mutation | `@playwright/cli` | Rules: - do not append control islands to happy-dom DOM trees - use real browser tests for WebSocket and dynamic import behavior - prefer fixture servers over brittle mock-WebSocket stacks - keep protocol/schema checks in pure tests when possible See `references/testing.md` for the detailed testing patterns. ## When To Open References - `references/server-pipeline.md` Use when changing SSR output, template behavior, style injection, or light/shadow DOM handoff. - `references/css-system.md` Use when changing styling helpers or token behavior. - `references/update-behavioral.md` Use when changing dynamic behavioral loading or its validation/security model. - `references/websocket-decisions.md` Use when changing protocol transport, session, replay, CSP, or origin rules. - `references/testing.md` Use when adding or revising UI tests. ## Related Skills - `behavioral-core` for BP semantics and thread design - `code-documentation` for TSDoc work in `src/ui`
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.