coss
Helps implement coss UI components correctly. Use when building UIs with coss primitives (buttons, dialogs, selects, forms, menus, tabs, inputs, toasts, etc.), migrating from shadcn/Radix to coss/Base UI, composing trigger-based overlays, or troubleshooting coss component behavior. Covers imports, accessibility, Tailwind styling, and common pitfalls.
What this skill does
# coss ui coss ui is a component library built on Base UI with a shadcn-like developer experience plus a large particle catalog. ## What this skill is for Use this skill to: - pick the right coss primitive(s) for a UI task - write correct coss usage code (imports, composition, props) - avoid common migration mistakes from shadcn/Radix assumptions - reference particle examples to produce practical, production-like patterns ## Source of truth - coss components docs: `apps/ui/content/docs/components/*.mdx` - `https://github.com/cosscom/coss/tree/main/apps/ui/content/docs/components` - coss particle examples: `apps/ui/registry/default/particles/p-*.tsx` - `https://github.com/cosscom/coss/tree/main/apps/ui/registry/default/particles` - coss particles catalog: `https://coss.com/ui/particles` - docs map for agents: `https://coss.com/ui/llms.txt` ## Out of scope - Maintaining coss monorepo internals/build pipelines. - Editing registry internals unless explicitly requested. ## Principles for agent output 1. Use existing primitives and particles first before inventing custom markup. 2. Prefer composition over custom behavior reimplementation. 3. Follow coss naming and APIs from docs exactly. 4. Keep examples accessible and production-realistic. 5. Prefer concise code that mirrors coss docs/particles conventions. 6. Assume Tailwind CSS v4 conventions in coss examples and setup guidance. ## Critical usage rules Always apply before returning coss code: - Do not invent coss APIs. Verify against component docs first. - For trigger-based primitives (Dialog, Menu, Select, Popover, Tooltip), follow each primitive's documented trigger/content hierarchy and composition API; do not mix patterns across components. - Preserve accessibility labels and error semantics. - Consult primitive-specific guides for component invariants and edge cases. - For manual install guidance, include all required dependencies and local component files referenced by imports. - Prefer styled coss exports first; use `*Primitive` exports only when custom composition/styling requires it. Rule references (read on demand when the task touches these areas): - `./references/rules/styling.md` — Tailwind tokens, icon conventions, data-slot selectors - `./references/rules/forms.md` — Field composition, validation, input patterns - `./references/rules/composition.md` — Trigger/popup hierarchies, grouped controls - `./references/rules/migration.md` — shadcn/Radix to coss/Base UI migration patterns - `./references/portal-props.md` — optional `portalProps` on composed popups and toast providers (`keepMounted`, `container`, which surfaces support it) ## Component discovery All 53 primitives have dedicated reference guides at `./references/primitives/<name>.md`. To find the right one for a task, consult the component registry index: - `./references/component-registry.md` ## Usage workflow 1. Identify user intent (single primitive, composed flow, form flow, overlay flow, feedback flow). 2. Consult `references/component-registry.md` to identify candidate primitives. 3. Select primitives from coss docs first; avoid custom fallback unless needed. 4. Check at least one particle example for practical composition patterns. Particle files live at `apps/ui/registry/default/particles/p-<name>-<N>.tsx` (e.g. `p-dialog-1.tsx`). 5. Write minimal code using documented imports/props. 6. Self-check accessibility and composition invariants. ## Installation reference See `./references/cli.md` for full install/discovery workflow. Quick CLI pattern: ```bash npx shadcn@latest add @coss/<component> ``` Quick manual pattern: - install dependencies listed in the component docs page - copy required component file(s) - update imports to match the target app alias setup ## Primitive Guidance Every primitive has a reference guide at `./references/primitives/<name>.md` with imports, minimal patterns, inline code examples, pitfalls, and particle references. Use the component registry to find the right file. High-risk primitives (read these guides first -- they have the most composition gotchas): - `./references/primitives/dialog.md` — modal overlays, form-in-dialog, responsive dialog/drawer - `./references/primitives/menu.md` — dropdown actions, checkbox/radio items, submenus - `./references/primitives/select.md` — items-first pattern, multiple, object values, groups - `./references/primitives/form.md` — Field composition, validation, submission - `./references/primitives/input-group.md` — addons, DOM order invariant, textarea layouts - `./references/primitives/toast.md` — toastManager (not Sonner), anchored toasts, providers ## Output Checklist Before returning code: - imports and props match coss docs - composition structure is valid for selected primitive(s) - accessibility and explicit control types (`button`, `input`, etc.) are present - migration-sensitive flows are verified (type/lint, keyboard/a11y behavior, and SSR-sensitive primitives like Select/Command)
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.