What problem does it solve? When building custom admin or vendor dashboards in the Mercur Medusa starter, developers often reinvent UI patterns that already exist, creating inconsistent interfaces and duplicated effort. This Skill enforces a clear component reuse hierarchy so every new UI element aligns with the existing design system. ## Core Features & Use Cases - Component Selection Hierarchy: Enforces a strict order of preference: @mercurjs/dashboard-shared wrappers first, then @medusajs/ui primitives, then composition, and only lastly new low-level primitives. - Usage Rules for Key Components: Defines when to use StatusBadge vs Badge vs plain text, TabbedForm for multi-step forms, _DataTable for data grids, and ActionMenu for contextual actions. - Hard Rules and Review Checklist: Provides explicit prohibitions (no custom dropdowns, dialogs, or tables when wrappers exist) plus a review checklist covering accessibility, i18n, and keyboard behavior. - Use Case: When adding a new vendor dashboard page with a filterable order list and a multi-step creation form, use this Skill to correctly compose _DataTable and TabbedForm instead of building custom tables and tab navigation. ## Quick Start Ask the assistant to review your new admin dashboard component for conformance with the Medusa UI component hierarchy and usage rules.