building-admin-dashboard-customizations — Claude Code skill
Guides AI agents in building Medusa Admin dashboard extensions, widgets, and custom UI routes. Essential when customizing store management panels.
npx skills add medusajs/medusa-agent-skills --skill building-admin-dashboard-customizations -a claude-codeWhat building-admin-dashboard-customizations does
This skill provides architecture patterns for extending the Medusa Admin interface. It covers creating UI widgets for orders and products, custom management pages, and modal flows. The instructions require using the official Medusa JS SDK for every request, because standard fetch calls strip session authentication headers.
Reference files in references/ supply component details for forms, tables, and typography. If you run pnpm, you must manually install matching versions of @tanstack/react-query and react-router-dom before writing UI code. Medusa stores currency amounts directly as standard decimals rather than cents, so dividing prices by 100 corrupts your dashboard data. Catching this early saves hours of debugging catalog pricing.
What it helps with
- Build custom widgets for Medusa order and product detail views
- Configure admin data queries with cache invalidation
- Create modal workflows using FocusModal and Drawer components
- Set up tables with search filters for large datasets
Example prompts for the agent
- Build an admin widget that displays custom metadata on the order details page
- Create a custom admin UI route with a paginated product table
- Add a Drawer form to edit customer tags using the Medusa JS SDK
How to install building-admin-dashboard-customizations
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill building-admin-dashboard-customizations -a claude-code2Manually: put the files in place
~/.claude/skills/building-admin-dashboard-customizations/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/building-admin-dashboard-customizations/
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill building-admin-dashboard-customizations -a codex2Manually: put the files in place
.agents/skills/building-admin-dashboard-customizations/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill building-admin-dashboard-customizations -a cursor2Manually: put the files in place
.cursor/skills/building-admin-dashboard-customizations/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install medusajs/medusa-agent-skills building-admin-dashboard-customizations2Manually: put the files in place
.github/skills/building-admin-dashboard-customizations/SKILL.md1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill building-admin-dashboard-customizations -a gemini-cli2Platform CLI
gemini skills install https://github.com/medusajs/medusa-agent-skills --path plugins/medusa-dev/skills/building-admin-dashboard-customizationsManually: put the files in place
.devin/skills/building-admin-dashboard-customizations/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill building-admin-dashboard-customizations -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about building-admin-dashboard-customizations
How to install building-admin-dashboard-customizations in Claude Code?
Run npx skills add medusajs/medusa-agent-skills --skill building-admin-dashboard-customizations -a claude-code.
What does the building-admin-dashboard-customizations skill do?
It teaches the agent how to build Medusa Admin UI extensions, enforcing component standards from @medusajs/ui and correct SDK query patterns.
Why do pnpm users need manual peer dependency installs?
Because pnpm isolates transitive dependencies strictly, @tanstack/react-query and react-router-dom must be added directly matching the dashboard package version. Projects on npm or yarn do not need this extra step.