shadcn-ui

I've been digging through component libraries lately, and shadcn-ui's approach to composition caught my attention—especially how it handles the abstraction layer between your design system and actual usage patterns, though the 67/100 suggests there might be some friction in how that story gets communicated.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 67/100, which puts you in D territory. This is based on Anthropic's best practices for agentic skills. Your Writing Style is solid at 8/10—the technical voice is clean and you've got good imperative structure. But Progressive Disclosure Architecture is dragging you down at 15/30. That's the real bottleneck here.

What's Working Well

• Clear triggers in your description - "forms, dialogs, tables, sidebars" gives agents concrete activation points
• Comprehensive component coverage - You're hitting the real problems developers face: forms with validation, dark mode, tables, dialogs
• Good imperative tone - Section headers and code comments are directive and clear; this is how skills should sound
• Practical examples - You're showing multiple variants and component composition patterns, not just theory

The Big One: Split That 853-Line File

This is killing your PDA score. Right now you've got everything in one massive SKILL.md file—all 10 core patterns with full boilerplate, imports repeated endlessly, and zero layered references. That's not scalable, and it tanks your token economy.

Here's the fix: Create a references/ directory and split your patterns:

• references/forms.md - Form patterns with validation (extract lines ~200-300)
• references/tables.md - Table patterns (extract ~50-100 lines)
• references/dialogs.md - Dialog pat...