medusajs/writing-tutorials
Creates Medusa documentation tutorials in two phases: first builds the tutorial feature in an example project (with planning, coding, and tests), then writes the MDX documentation. Use when creating a new how-to tutorial or integration guide for the Medusa docs. Handles both feature implementation and documentation writing, but only one phase at a time.
npx skills add https://github.com/medusajs/medusa --skill writing-tutorials
Guides an agent through creating a complete Medusa tutorial: building the feature in an example project, then writing the documentation.
Phase 1 — Build: Gather requirements → plan with user → implement feature → add tests → confirm with user
Phase 2 — Write: Create step diagram → write per-step MD files → combine into final MDX → update sidebar → clean up
> CRITICAL: Never do both phases in one session. Complete Phase 1, get user confirmation, then reload this skill for Phase 2.
> Load at least one reference file before proceeding.
| Task | Load |
|------|------|
| Starting Phase 1 (building) | reference/building-phase.md |
| Starting Phase 2 (writing) | reference/writing-phase.md + reference/tutorial-conventions.md + reference/concept-definitions.md |
| MDX patterns and components | reference/tutorial-conventions.md |
| Concept definitions (module, workflow, etc.) | reference/concept-definitions.md |
| Type | Content Path | Sidebar File |
|------|-------------|--------------|
| How-to tutorial | www/apps/resources/app/how-to-tutorials/tutorials/{name}/page.mdx | www/apps/resources/sidebars/how-to-tutorials.mjs |
| Integration guide | www/apps/resources/app/integrations/guides/{name}/page.mdx | www/apps/resources/sidebars/integrations.mjs |
medusa-dev:building-with-medusamedusa-dev:building-admin-dashboard-customizationsmedusa-dev:building-storefrontscontext7 MCP or skillsmcp__medusa__ask_medusa_questiontutorial-conventions.md_step-*.md temp files after combining into final MDXTake medusajs/writing-tutorials from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.