원클릭으로
planning-courses
Top-down course architecture from outcomes to modules. Use when designing a new course or restructuring an existing one.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Top-down course architecture from outcomes to modules. Use when designing a new course or restructuring an existing one.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
Create interface designs, wireframes, and design systems. Masters user research, accessibility standards, and modern design tools. Specializes in design tokens, component libraries, and inclusive design. Use PROACTIVELY for design systems, user flows, or interface optimization.
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
Acts as a brainstorming partner and story director to create a TED-style presentation blueprint. Use when the user asks to brainstorm a presentation, outline a talk, or structure ideas for a slide deck.
Generates a flawless Marp Markdown presentation or custom HTML deck from a presentation blueprint. Use when the user wants to convert an outline or blueprint into actual presentation slides (Marp, HTML, PDF, PPTX).
| name | planning-courses |
| description | Top-down course architecture from outcomes to modules. Use when designing a new course or restructuring an existing one. |
Outcomes first, topics second. Never start with "what should we teach?" Always start with "what should students be able to DO?"
Ask for and document:
## Course Identity
- **Course Name:**
- **Duration:** (weeks, total hours, # sessions)
- **Format:** (lecture / workshop / hybrid / online / project-based)
- **Domain:** (e.g., investing, Bitcoin, programming)
- **One-line promise:** "After this course, students will be able to ____"
Outcomes must be observable and measurable, not vague.
| ❌ Vague | ✅ Observable |
|---|---|
| "Understand technical analysis" | "Build a complete trading system using 3+ indicators" |
| "Learn about Bitcoin" | "Explain Bitcoin's monetary properties to a skeptic" |
| "Know risk management" | "Calculate position size given account size and stop loss" |
Rule: Use action verbs. Build, Calculate, Design, Evaluate, Compare, Demonstrate, Explain, Create.
Ask the user to define 3-5 core outcomes. Fewer is better.
Define 2-3 student profiles that represent the audience:
### Persona: [Name]
- **Background:** What they already know
- **Goal:** Why they're taking this course
- **Challenge:** What will be hardest for them
- **Success looks like:** What makes the course worth it for them
Why this matters: Every design decision should be checked against these personas. "Would Beginner Ben understand this? Would Advanced Amy be bored?"
Create a module-outcome matrix:
| Module | Outcome 1 | Outcome 2 | Outcome 3 | Outcome 4 |
|---|---|---|---|---|
| Module 1: Foundations | ✅ Intro | ✅ Intro | ||
| Module 2: Core Skills | ✅ Build | ✅ Intro | ||
| Module 3: Application | ✅ Build | ✅ Build | ✅ Intro | |
| Module 4: Mastery | ✅ Assess | ✅ Assess | ✅ Build | ✅ Assess |
Every outcome must appear at least twice: once for learning, once for assessment. Every module must serve at least one outcome. Modules with no outcomes get cut.
Check the sequence with these questions:
Map assessments to outcomes:
| Outcome | Assessment Type | When |
|---|---|---|
| "Build a trading system" | Project | Module 4 |
| "Calculate position size" | Quiz / Exercise | Module 2 |
| "Explain to a skeptic" | Presentation | Module 3 |
Rule: Every outcome must have at least one assessment. If you can't assess it, it's not a real outcome.
The final deliverable is a course-blueprint.md:
# [Course Name] Blueprint
## Course Identity
[From Step 1]
## Outcomes
1. [Observable outcome]
2. [Observable outcome]
3. [Observable outcome]
## Student Personas
[From Step 3]
## Module Structure
[Module-outcome matrix from Step 4]
### Module 1: [Name]
- **Sessions:** [N]
- **Outcomes served:** [list]
- **Key topics:** [brief]
- **Format mix:** [lecture %, workshop %, project %]
### Module 2: [Name]
...
## Assessment Map
[From Step 6]
## Prerequisite Chain
[Which modules depend on which]
designing-classes for each sessionaligning-curriculum to check consistency