insightflo/edu-deck-skills / edu-deck
edu-deck
FlaggedEntry skill for education deck requests. Use FIRST when the user wants 교육자료, 강의 자료, 교육용 슬라이드, 직원 교육 덱, or a training series (예: "○○ 교육자료 만들어줘", "사내 교육 시리즈 만들어", "여러 편으로 나눠 교육 자료"). 판별 후 단일 발행(주제 하나, 파일 하나)이면 edu-deck-solo 경로를, 여러 편 시리즈·진도 관리·허브가 필요하면 edu-deck-series 경로를 탄다. 애매하면 사용자에게 한 번 묻는다. 덱 제작 절차는 이 스킬에 없고 각 하위 스킬에 있다.
shared/assets/style-sheets/手绘白板风.md
View on GitHub# 手绘白板风
**适用场景:**
- 教学讲解
- 培训课程
- 头脑风暴
- 概念说明
- 技术分享
- 内部研讨
**GPT-Image-2 风格 Brief:**
```json
{
"type": "16:9 full-slide PowerPoint image",
"style_name": "手绘白板风",
"best_for": "概念解释、技术分享、培训课程和需要亲和力的思路拆解",
"visual_direction": "realistic whiteboard explanation slide, marker handwriting, sketched diagrams, friendly teaching atmosphere, authentic whiteboard details",
"canvas": {
"aspect_ratio": "16:9",
"background": "warm off-white whiteboard surface #FAFAF5 with subtle marker smudges",
"composition": "freeform but organized whiteboard layout with title, three concept blocks, arrows, and small doodle illustrations",
"density": "moderate, readable, brainstorming feel without chaos"
},
"color_palette": {
"primary": "black marker for main text",
"accent": "red #E74C3C, blue #3498DB, orange #F39C12 marker annotations",
"support": "green #27AE60, purple #9B59B6, yellow sticky note #FFF9C4",
"rule": "colors should look like real marker ink, not digital neon"
},
"typography": {
"title": "large neat handwritten Chinese marker style",
"body": "clear handwritten marker text, slightly irregular but readable",
"emphasis": "circle, underline, boxed words, sticky-note comments",
"text_quality": "Chinese handwriting must remain accurate and legible"
},
"layout_patterns": [
"three hand-drawn boxes connected by arrows",
"central concept bubble with surrounding notes",
"simple process diagram with sketches and annotations",
"left explanation list plus right hand-drawn diagram"
],
"layout_usage_rule": "Use layout_blueprints as candidate starting points only. Choose and adapt the composition according to each slide's semantic role; avoid repeating the same blueprint on adjacent slides unless it is a deliberate repeated sequence.",
"layout_blueprints": [
{
"name": "whiteboard process diagram",
"sections": [
{"position": "top-left", "count": 1, "labels": ["handwritten title"]},
{"position": "center", "count": 3, "labels": ["step 1 box", "step 2 box", "step 3 box"]},
{"position": "between boxes", "count": 2, "labels": ["hand-drawn arrow", "hand-drawn arrow"]},
{"position": "right edge", "count": 1, "labels": ["sticky-note takeaway"]}
]
},
{
"name": "concept map",
"sections": [
{"position": "center", "count": 1, "labels": ["main concept bubble"]},
{"position": "around center", "count": 4, "labels": ["supporting idea", "risk note", "example sketch", "action item"]},
{"position": "bottom", "count": 1, "labels": ["underlined summary"]}
]
}
],
"visual_elements": {
"allowed": "whiteboard frame, marker tray, colored markers, arrows, boxes, clouds, sticky notes, doodle icons, underlines, circled keywords",
"avoid": "messy illegible handwriting, childish clutter, photoreal people, digital UI cards"
},
"rendering_constraints": [
"The slide should look like a real whiteboard captured cleanly for a presentation.",
"Keep all Chinese text readable despite handwritten style.",
"No watermark, no unrelated logo, no slide number unless explicitly requested."
]
}
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |