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": "warm handmade paper collage slide, tactile paper craft, gentle human-centered storytelling, cozy scrapbook composition",
"canvas": {
"aspect_ratio": "16:9",
"background": "warm cream paper #F5F1E8 or pale wood #E8DCC8 with subtle paper fibers",
"composition": "paper cutout title area, 3 paper note cards for key points, gentle illustration accents",
"density": "airy and comforting, generous breathing room"
},
"color_palette": {
"primary": "warm brown #A67C52 and deep cocoa #5C4033 for text",
"soft_colors": "dusty pink #F5C4B8, sage green #B8D4A8, sky blue #A8D8EA, sunset orange #FFA574, lavender #C9B1D0",
"surface": "cream, handmade paper, kraft paper, pastel sticky notes",
"rule": "all colors should feel soft, matte, and paper-like"
},
"typography": {
"title": "rounded handwritten or friendly display style",
"body": "clear friendly handwritten or rounded sans-serif Chinese text",
"emphasis": "paper labels, stitched tags, small handwritten captions",
"text_quality": "Chinese text must be accurate and legible"
},
"layout_patterns": [
"three torn-paper cards aligned naturally across the slide",
"scrapbook title ribbon with small illustrated stickers",
"central handmade diagram with taped labels",
"soft paper collage with one warm illustration and supporting notes"
],
"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": "paper note cards",
"sections": [
{"position": "top", "count": 1, "labels": ["torn-paper title ribbon"]},
{"position": "center", "count": 3, "labels": ["paper card 1", "paper card 2", "paper card 3"]},
{"position": "corners", "count": 4, "labels": ["small sticker", "tape strip", "plant doodle", "paper clip"]}
]
},
{
"name": "scrapbook story",
"sections": [
{"position": "left", "count": 1, "labels": ["warm illustration or paper collage scene"]},
{"position": "right", "count": 3, "labels": ["key point note", "example note", "takeaway note"]},
{"position": "bottom", "count": 1, "labels": ["handwritten closing line"]}
]
}
],
"visual_elements": {
"allowed": "paper texture, torn edges, tape, paper clips, buttons, watercolor blocks, simple doodles, plant stickers, soft shadows",
"avoid": "glossy plastic look, corporate sharp edges, harsh black text, neon colors, overly childish clutter"
},
"rendering_constraints": [
"The slide should feel handmade but still presentation-ready.",
"Paper shadows and textures should be subtle and not reduce text legibility.",
"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 |