medusa-ui-conformance

Guide developers in implementing accessible UI components for Medusa admin and vendor dashboards.

Updated May 2, 2026
One-click install
npx skills add https://github.com/nathangalea/plants-direct --skill medusa-ui-conformance-nathangalea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: medusa-ui-conformance
Source: https://github.com/nathangalea/plants-direct/tree/main/.claude/skills/medusa-ui-conformance
Command: npx skills add https://github.com/nathangalea/plants-direct --skill medusa-ui-conformance-nathangalea

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers maintain consistency and usability in admin and vendor interfaces by guiding the alignment with shared UI patterns and libraries.

Core Features & Use Cases

  • UI Consistency Enforcement: Guides the reuse of existing shared components like @mercurjs/dashboard-shared and @medusajs/ui.
  • Interactive Pattern Selection: Aids in choosing appropriate primitives and layout components for admin dashboards and pages.
  • Use Case: When building a new admin page, leverage this Skill to select predefined, accessible, and keyboard-navigable UI elements that fit the existing dashboard style.

Quick Start

Use this Skill to identify best practices for composing and deploying uniform, accessible, and scalable admin and vendor interfaces.

Frequently Asked Questions about medusa-ui-conformance

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

FAQPage Schema
How do I ensure my custom admin dashboard UI aligns with Medusa design standards?

To ensure your custom admin dashboard UI aligns with Medusa design standards, you should reuse existing shared components like @medusajs/ui. This enforces interface consistency and adheres to predefined interaction patterns.

What is the best way to build accessible vendor dashboard components?

The best way to build accessible vendor dashboard components is to leverage predefined UI primitives that support keyboard navigation. This ensures adherence to interaction and accessibility best practices.

Can I use shared UI libraries for creating overlays and menus in Medusa admin pages?

Yes, you can use shared UI libraries like @mercurjs/dashboard-shared for creating overlays and menus in Medusa admin pages. This maintains visual consistency and reusability across your interface.

Does this UI conformance approach work for building scalable vendor interfaces?

Yes, this UI conformance approach works for building scalable vendor interfaces by guiding the selection of appropriate layout components. It ensures your pages remain uniform and accessible as the application grows.

Why should I reuse existing components instead of building custom Medusa admin layouts?

You should reuse existing components instead of building custom Medusa admin layouts to maintain usability and design consistency. Relying on shared libraries prevents fragmentation and ensures accessibility compliance.

How do I select the right UI primitives for my Medusa admin forms?

To select the right UI primitives for your Medusa admin forms, identify existing shared components that match your layout requirements. This guarantees your forms fit the established dashboard style and accessibility standards.