skills.rest
OZVE
OZVECOMMUNITY
Explore all skills by this author →
GitHub

cc-alignment

Align Compound Component exports and slot naming for vendor-standard registry consumption.

Updated Apr 3, 2026
Search Tags:#refactor#registry#types#exports#cc-alignment#vendor-standard
One-click install
npx skills add https://github.com/OZVE/cuarta-avenida --skill cc-alignment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cc-alignment
Source: https://github.com/OZVE/cuarta-avenida/tree/main/.claude/skills/cc-alignment
Command: npx skills add https://github.com/OZVE/cuarta-avenida --skill cc-alignment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Align existing Compound Component pages to vendor standard naming and structure, enabling consistent exports, route maps, and registry consumption across a dashboard ecosystem.

Core Features & Use Cases

  • Rename CC exports to vendor-compliant names (e.g., XxxDetail → XxxDetailPage).
  • Prefix Main/Sidebar slot components and add missing slots while removing obsolete ones.
  • Update barrel exports and route maps, and align testing-registry usage for CC pages.
  • Validate architecture constraints: no React context usage within CCs, no Layout wrappers, and DTS/build pipeline integrity.

Quick Start

Migrate a CC by renaming exports, updating slot prefixes, and refreshing barrel exports, then validate DTS build and testing-registry integration.

Frequently Asked Questions about cc-alignment

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

FAQPage Schema
How do I rename compound component exports to match vendor naming standards?▼

To align compound component exports to vendor naming standards, you update identifiers like XxxDetail to XxxDetailPage and synchronize these changes across barrel exports and route maps to ensure consistent imports across your codebase.

How do I update slot prefixes when migrating compound component pages?▼

Updating slot prefixes when migrating compound component pages involves prefixing Main and Sidebar slot components, adding missing slots, and removing obsolete ones to conform to the expected vendor component structure.

Why do my compound components fail DTS build validation after a refactor?▼

Compound components fail DTS build validation after a refactor if architecture constraints are violated, such as using React context within components, wrapping them in Layout components, or leaving barrel exports misaligned with the TSup build pipeline.

Can I use a testing registry to validate compound component route composition?▼

Yes, you can use a testing registry to validate compound component route composition by applying a registry consumer pattern to verify that the standardized vendor naming and barrel exports integrate correctly during the TSup build workflow.

What is the best way to align barrel exports for a compound component dashboard ecosystem?▼

The best way to align barrel exports for a compound component dashboard ecosystem is to standardize vendor naming conventions across all pages, update slot prefixes, and refresh route maps to enable consistent registry consumption.

Related Skills

Explore More Software Engineering Skills→
mercurjsmercurjs
1.7k

cc-alignment

Rename Compound Component exports and refactor directory structures to vendor standards.

Official
Advanced
kevinxo328kevinxo328
5

vercel-composition-patterns

Apply React composition patterns to reduce boolean props and build scalable component libraries.

Community
Intermediate
fysoul17fysoul17
4

vercel-composition-patterns

Guide React component refactoring using compound components and context providers.

Community
Advanced
rauell1rauell1
3

next-upgrade

Upgrade Next.js projects to the latest release with codemods and dependency updates.

Community
Advanced