cleen-ui-layout

Build user interfaces with @cleen/ui layout components and Tailwind conventions.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/shawnlivermore/cleen-ui-skills --skill cleen-ui-layout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleen-ui-layout
Source: https://github.com/shawnlivermore/cleen-ui-skills/tree/main/skills/cleen-ui-layout
Command: npx skills add https://github.com/shawnlivermore/cleen-ui-skills --skill cleen-ui-layout

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents developers from building common UI layouts from scratch using raw divs, forgetting essential @cleen/ui conventions like the .cleen scope wrapper and cleen- Tailwind prefixes, or reinventing components like Card and Divider.

Core Features & Use Cases

  • Standardized Layouts: Provides pre-defined patterns for pages, dashboards, settings, and detail views.
  • Component Guidance: Details the usage of Card, Divider, PillBadge, Avatar, and AvatarRow for consistent UI construction.
  • Tailwind Convention Enforcement: Ensures all Tailwind classes use the cleen- prefix and the root element has the .cleen scope wrapper.
  • Use Case: When asked to "create a dashboard page with key metrics and a data table," this skill will guide the AI to use Card components for metrics, a DataGrid for the table, and ensure all necessary Tailwind prefixes and the root .cleen wrapper are applied.

Quick Start

Use the cleen-ui-layout skill to build a dashboard page with a KPI row and a data grid.

Frequently Asked Questions about cleen-ui-layout

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

FAQPage Schema
How do I build a dashboard UI with Tailwind CSS and @cleen/ui components?

To build a dashboard UI with @cleen/ui, use Card components for key metrics and a DataGrid for tables. Ensure the root element includes the .cleen scope wrapper and all Tailwind classes use the cleen- prefix for consistent styling conventions.

Why do my @cleen/ui layout components lose their styling conventions?

@cleen/ui layout components lose styling when the root element lacks the .cleen scope wrapper or Tailwind classes omit the cleen- prefix. Apply these standardized conventions to ensure components like Card and Divider render correctly.

What is the correct way to structure a settings page using @cleen/ui?

Structure a settings page using @cleen/ui by utilizing pre-defined layout patterns for detail views. Implement core components like Card, Divider, and Avatar within the .cleen scoped root element to maintain consistent UI composition.

Can I use @cleen/ui layout components without the Tailwind cleen- prefix?

No, @cleen/ui layout components require the Tailwind cleen- prefix. The skill enforces Tailwind convention adherence, ensuring all utility classes are properly prefixed and the root element utilizes the .cleen scope wrapper for correct rendering.

What components are available for UI composition in @cleen/ui?

Available @cleen/ui components for UI composition include Card, Divider, PillBadge, Avatar, and AvatarRow. These core layout components provide standardized patterns for building pages, dashboards, and settings views.

What is the best way to prevent building UI layouts from scratch in frontend development?

The best way to prevent building UI layouts from scratch is using standardized component guidance. This approach provides pre-defined patterns for pages and dashboards while enforcing essential Tailwind CSS prefixing and root element scoping conventions.