coss

Implement coss UI components using Base UI primitives with Tailwind CSS v4.

1.6k|107|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/MapleTechLabs/maple --skill coss-mapletechlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coss
Source: https://github.com/MapleTechLabs/maple/tree/main/.agents/skills/coss
Command: npx skills add https://github.com/MapleTechLabs/maple --skill coss-mapletechlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the difficulty of correctly implementing coss UI components, which are built on Base UI with a shadcn-like developer experience. It eliminates common migration mistakes from shadcn/Radix and ensures proper composition, accessibility, and Tailwind styling without guesswork.

Core Features & Use Cases

  • Component Discovery: Quickly identify the right coss primitive for any UI task using the component registry index.
  • Implementation Guidance: Get correct imports, composition patterns, and prop usage for 53+ primitives including dialogs, menus, forms, and overlays.
  • Migration Support: Safely migrate from shadcn/Radix to coss/Base UI with documented pattern translations and pitfall avoidance.
  • Particle Examples: Reference production-like particle examples for practical composition patterns.

Quick Start

Use the coss skill to implement a dialog component with correct trigger and popup composition by consulting the dialog primitive reference guide.

Frequently Asked Questions about coss

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

FAQPage Schema
How do I implement accessible React UI components with Tailwind CSS v4 and Base UI primitives?

To implement accessible React UI components with Tailwind CSS v4 and Base UI primitives, use the coss component registry to discover 53+ primitives like dialogs and menus, ensuring correct imports, composition patterns, and prop usage for production-ready interfaces without guesswork.

What is the best way to migrate from shadcn or Radix UI to Base UI primitives?

The best way to migrate from shadcn or Radix UI to Base UI primitives involves using documented pattern translations and pitfall avoidance provided by coss, which ensures proper composition, accessibility, and Tailwind styling while eliminating common migration mistakes.

Can I use coss UI components for complex forms, selects, and overlays in React?

Yes, you can use coss UI components for complex forms, selects, and overlays in React. The skill provides implementation guidance and production-like particle examples for 53+ component primitives built on Base UI with a shadcn-like developer experience.

How do I find the correct Base UI primitive for a specific frontend interface task?

To find the correct Base UI primitive for a specific frontend interface task, consult the coss component discovery registry index, which helps quickly identify the right primitive for any UI requirement using the component registry.

Why does my shadcn to Base UI component migration break composition and accessibility rules?

shadcn to Base UI component migration often breaks composition and accessibility rules due to undocumented pattern differences. coss eliminates these common migration mistakes by providing documented pattern translations and correct composition rules for accessible production-ready interfaces.