ui-primitive-consolidation

Name: ui-primitive-consolidation
Availability: InStock
Author: aaron

Consolidate scattered UI patterns into reusable primitives across PANaCEa.

Updated Nov 16, 2025

Search Tags:#ui #consistency #accessibility #component #refactor #design-system #design-primitives

Ready to run

npx skills add https://github.com/aaronjullger-lgtm/PANaCEa --skill ui-primitive-consolidation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ui-primitive-consolidation
Source: https://github.com/aaronjullger-lgtm/PANaCEa/tree/main/.claude/skills/ui-primitive-consolidation
Command: npx skills add https://github.com/aaronjullger-lgtm/PANaCEa --skill ui-primitive-consolidation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scattered UI patterns across PANaCEa cause duplicated code, inconsistent visuals, and higher maintenance costs. This skill identifies and consolidates patterns into reusable primitives to improve consistency, reuse, and maintainability.

Core Features & Use Cases

Consolidates common UI elements (buttons, cards, modals, badges, loading states) into centralized primitives.
Audits components for duplication, eliminates ad-hoc implementations, and guides design-system expansion.
Use case: refactor drills and dashboards to consume consolidated primitives, ensuring uniform styling and behavior.

Quick Start

Audit the codebase for duplicate UI patterns and begin extracting primitives into components/ui, then migrate consumers to use them.

Frequently Asked Questions about ui-primitive-consolidation

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

FAQPage Schema

How do I consolidate scattered UI patterns into reusable primitives?▼

To consolidate UI patterns, audit the codebase for duplicate elements like buttons and modals, extract them into centralized primitives, and migrate consumers to use the updated exports while preserving accessibility and responsive behavior.

What is UI primitive consolidation and when do I need it?▼

UI primitive consolidation is the process of identifying duplicated, inconsistent UI elements across an application and refactoring them into a unified design system. You need it when scattered patterns cause inconsistent visuals and high maintenance costs.

Can I refactor ad-hoc modal implementations without breaking responsive behavior?▼

Yes, you can refactor ad-hoc modal implementations by replacing them with centralized primitives. This process preserves existing accessibility standards and responsive behavior while eliminating duplicated code and inconsistent styling.

What's the best way to audit a design system for duplicated UI components?▼

The best way to audit a design system for duplication is to scan multi-component applications for ad-hoc implementations and inconsistent styling, then establish a consistent primitive taxonomy to guide design-system expansion and code refactoring.

Does UI refactoring for design consistency require updating component exports?▼

Yes, UI refactoring for design consistency requires updating exports. You must extract centralized primitives into a shared directory and update all consumer imports to ensure uniform styling and behavior across the application.

Why does inconsistent UI styling happen in multi-component applications?▼

Inconsistent UI styling happens in multi-component applications when developers create ad-hoc implementations instead of using centralized primitives, leading to duplicated code, visual discrepancies, and higher maintenance costs.