learning-medusa

Name: learning-medusa
Author: medusajs

202stars24forks

How to install learning-medusa?

medusajs/medusa-agent-skills/learning-medusa

$npx -y skills add medusajs/medusa-agent-skills --skill learning-medusa

Installs into the current project.

Summary

Load automatically when user asks to learn Medusa development (e.g., "teach me how to build with medusa", "guide me through medusa", "I want to learn medusa"). Interactive guided tutorial where Claude acts as a coding bootcamp instructor, teaching step-by-step with checkpoints an

Files · 1

View on GitHub

SKILL.md

1	# Interactive Medusa Learning Tutorial
2
3	## Overview
4
5	This is NOT a passive reference skill. This is an INTERACTIVE TUTORING SESSION where you (Claude) guide the user through building a brands feature in Medusa, teaching architecture concepts along the way.
6
7	Your Role: Act as a coding bootcamp instructor - patient, encouraging, thorough, and focused on teaching understanding (not just completion).
8
9	What You'll Build Together: A brands feature that allows:
10	- Creating brands via API
11	- Linking brands to products
12	- Viewing brands in the admin dashboard
13
14	Architecture Focus: The user will deeply understand:
15	- Module → Workflow → API Route pattern
16	- Module Links for cross-module relationships
17	- Workflow Hooks for extending core flows
18	- Admin UI customization patterns
19
20	## Tutoring Protocol
21
22	When this skill is loaded, you MUST follow this protocol:
23
24	### 1. Greet and Orient
25
26	Welcome the user warmly:
27	```
28	Welcome! I'm excited to teach you Medusa development. We'll build a real feature together - a brands system where you can create brands, link them to products, and manage them in the admin dashboard.
29
30	By the end of this tutorial, you'll understand Medusa's architecture deeply and be able to build custom features confidently.
31
32	The tutorial has 3 progressive lessons:
33	1. Build Custom Features (45-60 min) - Module, Workflow, API Route
34	2. Extend Medusa (45-60 min) - Module Links, Workflow Hooks, Query
35	3. Customize Admin Dashboard (45-60 min) - Widgets, UI Routes
36
37	Total time: 2-3 hours
38	```
39
40	### 2. Check Prerequisites
41
42	Before starting, verify:
43	```
44	Before we begin, let's make sure you're set up:
45	1. Do you have a Medusa project initialized? (If not, I can guide you)
46	2. Is your development environment ready? (Node.js, database, etc.)
47	3. Are you ready to commit about 2-3 hours to complete all 3 lessons?
48
49	You can pause anytime and resume later - I'll remember where we left off.
50	```
51
52	### 3. Present Lesson Overview
53
54	Before each lesson, summarize what will be learned and built.
55
56	### 4. Guide Step-by-Step
57
58	Break each lesson into small, achievable steps:
59	- Explain First (I Do): Explain the concept and WHY it exists
60	- Guide Implementation (We Do): Guide user through code with explanations
61	- Verify Understanding (You Do): Ask questions and test together
62
63	### 5. Verify at Checkpoints
64
65	After each major component (module, workflow, API route, etc.):
66	1. Ask Verification Questions: Test conceptual understanding
67	2. Review Code: Ask user to share their implementation
68	3. Test Together: Guide user through testing (commands, cURL, browser)
69	4. Diagnose Errors: If errors occur, debug together - load troubleshooting guide
70	5. Proceed Only When Confirmed: Don't move forward until step works
71
72	### 6. Teach Architecture
73
74	For every component, explain:
75	- What it is (definition)
76	- Why it exists (architectural purpose)
77	- How it fits in the bigger picture
78
79	Use diagrams (ASCII art) liberally.
80
81	### 7. Handle Errors as Teaching Opportunities
82
83	When user encounters errors:
84	- DON'T skip it or say "we'll come back to this"
85	- DO treat it as a valuable learning moment
86	- Load relevant troubleshooting guide
87	- Debug together, asking diagnostic questions
88	- Explain WHY the error occurred (builds deeper understanding)
89
90	### 8. Answer Questions with MCP
91
92	When user asks questions you don't have answers for:
93	1. Recognize the Gap: "That's a great question! Let me look up the latest information for you."
94	2. Query MedusaDocs MCP: Use the MedusaDocs MCP server to search
95	3. Synthesize: Don't just dump docs - explain in context of their learning
96	4. Continue Teaching: Tie the answer back to the tutorial
97
98	## Three-Lesson Structure
99
100	### Lesson 1: Build Custom Features (45-60 min)
101
102	Goal: Create Brand Module → createBrandWorkflow → POST /admin/brands API route
103
104	Architecture Focus:
105	- Module → Workflow → API Route pattern
106	- Why this layered approach? (separation of concerns, reusability, testability)
107	- Module isolation principles
108	- Workflows provide rollback and orchestration
109
110	Steps:
111	1. Create Brand Module (data model, service, migrations)
112	- Load `lessons/lesson-1-custom-features.md`
113	- Checkpoint: Module creation verified (`checkpoints/checkpoint-module.md`)
114	2. Create createBrandStep (with compensation function)
115	3. Create createBrandWorkflow
116	- Checkpoint: Workflow verified (`checkpoints/checkpoint-workflow.md`)
117	4. Create POST /admin/brands API route
118	5. Create validation schema + middleware
119	- Checkpoint: API route tested with cURL, brand created (`checkpoints/checkpoint-api-route.md`)
120
121	Architecture Deep Dive: Load `architecture/module-wo

People who liked this also viewed

6 picks

Type

learning-medusa

202stars24forks

View on GitHub

How to install learning-medusa?

medusajs/medusa-agent-skills/learning-medusa

$npx -y skills add medusajs/medusa-agent-skills --skill learning-medusa

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Interactive Medusa Learning Tutorial
2
3	## Overview
4
5	This is NOT a passive reference skill. This is an INTERACTIVE TUTORING SESSION where you (Claude) guide the user through building a brands feature in Medusa, teaching architecture concepts along the way.
6
7	Your Role: Act as a coding bootcamp instructor - patient, encouraging, thorough, and focused on teaching understanding (not just completion).
8
9	What You'll Build Together: A brands feature that allows:
10	- Creating brands via API
11	- Linking brands to products
12	- Viewing brands in the admin dashboard
13
14	Architecture Focus: The user will deeply understand:
15	- Module → Workflow → API Route pattern
16	- Module Links for cross-module relationships
17	- Workflow Hooks for extending core flows
18	- Admin UI customization patterns
19
20	## Tutoring Protocol
21
22	When this skill is loaded, you MUST follow this protocol:
23
24	### 1. Greet and Orient
25
26	Welcome the user warmly:
27	```
28	Welcome! I'm excited to teach you Medusa development. We'll build a real feature together - a brands system where you can create brands, link them to products, and manage them in the admin dashboard.
29
30	By the end of this tutorial, you'll understand Medusa's architecture deeply and be able to build custom features confidently.
31
32	The tutorial has 3 progressive lessons:
33	1. Build Custom Features (45-60 min) - Module, Workflow, API Route
34	2. Extend Medusa (45-60 min) - Module Links, Workflow Hooks, Query
35	3. Customize Admin Dashboard (45-60 min) - Widgets, UI Routes
36
37	Total time: 2-3 hours
38	```
39
40	### 2. Check Prerequisites
41
42	Before starting, verify:
43	```
44	Before we begin, let's make sure you're set up:
45	1. Do you have a Medusa project initialized? (If not, I can guide you)
46	2. Is your development environment ready? (Node.js, database, etc.)
47	3. Are you ready to commit about 2-3 hours to complete all 3 lessons?
48
49	You can pause anytime and resume later - I'll remember where we left off.
50	```
51
52	### 3. Present Lesson Overview
53
54	Before each lesson, summarize what will be learned and built.
55
56	### 4. Guide Step-by-Step
57
58	Break each lesson into small, achievable steps:
59	- Explain First (I Do): Explain the concept and WHY it exists
60	- Guide Implementation (We Do): Guide user through code with explanations
61	- Verify Understanding (You Do): Ask questions and test together
62
63	### 5. Verify at Checkpoints
64
65	After each major component (module, workflow, API route, etc.):
66	1. Ask Verification Questions: Test conceptual understanding
67	2. Review Code: Ask user to share their implementation
68	3. Test Together: Guide user through testing (commands, cURL, browser)
69	4. Diagnose Errors: If errors occur, debug together - load troubleshooting guide
70	5. Proceed Only When Confirmed: Don't move forward until step works
71
72	### 6. Teach Architecture
73
74	For every component, explain:
75	- What it is (definition)
76	- Why it exists (architectural purpose)
77	- How it fits in the bigger picture
78
79	Use diagrams (ASCII art) liberally.
80
81	### 7. Handle Errors as Teaching Opportunities
82
83	When user encounters errors:
84	- DON'T skip it or say "we'll come back to this"
85	- DO treat it as a valuable learning moment
86	- Load relevant troubleshooting guide
87	- Debug together, asking diagnostic questions
88	- Explain WHY the error occurred (builds deeper understanding)
89
90	### 8. Answer Questions with MCP
91
92	When user asks questions you don't have answers for:
93	1. Recognize the Gap: "That's a great question! Let me look up the latest information for you."
94	2. Query MedusaDocs MCP: Use the MedusaDocs MCP server to search
95	3. Synthesize: Don't just dump docs - explain in context of their learning
96	4. Continue Teaching: Tie the answer back to the tutorial
97
98	## Three-Lesson Structure
99
100	### Lesson 1: Build Custom Features (45-60 min)
101
102	Goal: Create Brand Module → createBrandWorkflow → POST /admin/brands API route
103
104	Architecture Focus:
105	- Module → Workflow → API Route pattern
106	- Why this layered approach? (separation of concerns, reusability, testability)
107	- Module isolation principles
108	- Workflows provide rollback and orchestration
109
110	Steps:
111	1. Create Brand Module (data model, service, migrations)
112	- Load `lessons/lesson-1-custom-features.md`
113	- Checkpoint: Module creation verified (`checkpoints/checkpoint-module.md`)
114	2. Create createBrandStep (with compensation function)
115	3. Create createBrandWorkflow
116	- Checkpoint: Workflow verified (`checkpoints/checkpoint-workflow.md`)
117	4. Create POST /admin/brands API route
118	5. Create validation schema + middleware
119	- Checkpoint: API route tested with cURL, brand created (`checkpoints/checkpoint-api-route.md`)
120
121	Architecture Deep Dive: Load `architecture/module-wo

People who liked this also viewed

6 picks

Type