원클릭으로
designing-classes
Design individual class sessions that serve course outcomes and work for mixed-level audiences. Use after planning-courses.
메뉴
Design individual class sessions that serve course outcomes and work for mixed-level audiences. Use after planning-courses.
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 | designing-classes |
| description | Design individual class sessions that serve course outcomes and work for mixed-level audiences. Use after planning-courses. |
Every session must answer: "What can students DO after this class that they couldn't before?" If you can't answer this, the session needs redesigning.
Before designing, establish:
## Session Context
- **Session #:** [N] of [Total]
- **Module:** [Which module this belongs to]
- **Course outcomes served:** [Which outcomes this session advances]
- **Prerequisites:** [What students should know from previous sessions]
- **What comes next:** [What the next session expects them to know]
Write ONE primary outcome for this session:
Optional: 1-2 secondary outcomes.
Design content in three layers to handle mixed audiences:
### 🟢 Core Layer (Everyone Must Get This)
- The essential concept/skill
- Simplified explanations
- One clear example
- Time: ~50% of session
### 🟡 Extension Layer (Intermediate Students)
- Deeper nuance, edge cases
- "Why" behind the "what"
- Additional examples with variation
- Time: ~30% of session
### 🔴 Challenge Layer (Advanced Students)
- Real-world complexity
- "What if..." scenarios
- Connection to advanced topics
- Optional homework/exploration
- Time: ~20% of session
Key rule: Core must stand alone. A beginner who only gets the Core layer should still meet the session outcome.
Choose and sequence activities:
| Format | Best For | Time Guideline |
|---|---|---|
| Lecture | New concepts, theory, context | 15-20 min blocks max |
| Demo | Showing how to do something | 10-15 min |
| Workshop | Hands-on practice with guidance | 20-40 min |
| Discussion | Processing ideas, different perspectives | 10-20 min |
| Individual work | Applying concepts independently | 15-30 min |
| Group activity | Collaborative problem-solving | 20-30 min |
| Assessment | Checking understanding | 10-20 min |
Rules:
## Session [N]: [Title]
**Duration:** [X minutes/hours]
**Outcome:** [Session outcome]
**Outcomes served:** [Course outcomes]
### Opening (5-10 min)
- Hook: [Attention-grabbing question, story, or demo]
- Connection: [How this relates to previous session]
- Roadmap: [What we'll cover today]
### Block 1: [Topic] (XX min)
- **Format:** [Lecture/Demo/Workshop]
- **Core:** [What everyone learns]
- **Extension:** [Additional depth]
- **Activity:** [What students do]
### Block 2: [Topic] (XX min)
- **Format:** [...]
- **Core:** [...]
- **Extension:** [...]
- **Activity:** [...]
### Application (XX min)
- **Format:** [Workshop/Individual/Group]
- **Task:** [What students practice]
- **Challenge variant:** [Harder version for advanced]
### Closing (5-10 min)
- **Key takeaway:** [One sentence summary]
- **Connection forward:** [Preview of next session]
- **Action item:** [What to do before next class]
For each major content block, verify:
| Content Block | Beginner | Intermediate | Advanced |
|---|---|---|---|
| Block 1 | ✅ Core covers it | ✅ Extension adds depth | ✅ Challenge available |
| Block 2 | ⚠️ Might need scaffolding | ✅ Good | ✅ Already knows this |
| Activity | ✅ Simplified version | ✅ Standard | ✅ Extended version |
Flag if any persona is neglected for too long.
planning-courses blueprint for session contextaligning-curriculum for consistency check