Comprehensive guide for Medusa backend architecture, workflows, and critical implementation rules.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add medusajs/medusa-agent-skills --skill building-with-medusaCompatible with
Supported agents
Covers six rule categories (architecture, type safety, business logic placement, imports, data access, file organization) with specific anti-patterns and enforcement checks
Enforces strict layer separation: Module → Workflow → API Route → Frontend, with workflows required for all mutations and only GET/POST/DELETE HTTP methods allowed
Includes critical data handling rules: prices stored
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbuilding-with-medusaExecute the skills CLI command in your project's root directory to begin installation:
epx add medusajs/medusa-agent-skills --skill building-with-medusaFetches building-with-medusa from medusajs/medusa-agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/building-with-medusa
Restart Cursor to activate building-with-medusa. Access via /building-with-medusain your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
ui-animation
mblode/agent-skills · Frontend · same category
apple-ui-designer
heyman333/atelier-ui · Frontend · same category
frontend-ui-ux
code-yeongyu/oh-my-opencode · Frontend · same category
senior-frontend
alirezarezvani/claude-skills · Frontend · same category
frontend-security
schalkneethling/webdev-agent-skills · Frontend · same category
tailwind
pproenca/dot-skills · Frontend · same category
building-with-medusa fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for building-with-medusa matched our evaluation — installs cleanly and behaves as described in the markdown.
building-with-medusa is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: building-with-medusa is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend building-with-medusa for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: building-with-medusa is focused, and the summary matches what you get after install.
We added building-with-medusa from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend building-with-medusa for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: building-with-medusa is the kind of skill you can hand to a new teammate without a long onboarding doc.
building-with-medusa reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 25