[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73DVKN82EVV2YPMDHF2Z7F4":3,"skill-same:01M73DVKN82EVV2YPMDHF2Z7F4":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M73DVKN82EVV2YPMDHF2Z7F4","storyline",null,"Designs lecture storyline and slide deck composition. Given research_notes.md (or direct topic input), produces storyline.md and slide_deck.md. Responds to \"make storyline\", \"compose slide deck\", \"structure chapters\" (Korean: \"make storyline\", \"compose slide deck\", \"restructure chapters\"). Stages 2-3 of the lecture workflow.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-deck\u002F.claude\u002Fskills\u002Fstoryline\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: storyline\nscope: co-deck\nversion: 1.2.0\ndescription: >\n  Designs lecture storyline and slide deck composition. Given research_notes.md\n  (or direct topic input), produces storyline.md and slide_deck.md. Responds\n  to \"make storyline\", \"compose slide deck\", \"structure chapters\" (Korean:\n  \"make storyline\", \"compose slide deck\", \"restructure chapters\"). Stages 2-3\n  of the lecture workflow.\nstatus: active\nowner: storyline\nlast_reviewed: 2026-06-19\nprerequisites: research\nrelates_to:\n  - skill: design\n    type: follows\ninputs: [research-notes]\noutputs: [storyline-outline, slide-deck-draft]\n---\n\n## Context\n\nDesigns the lecture narrative flow (`storyline.md`) and per-slide content (`slide_deck.md`). `slide_deck.md` is the direct input consumed by the Build Agent for HTML generation. Invoked at Stages 2-3, after research and optional source verification.\n\n## When to Use\n\n- PM Agent dispatches after Stage 1 (research)\n- User says \"make storyline\"\n- User says \"compose slide deck\"\n- User says \"restructure chapters\"\n\n---\n\n## Execution Steps\n\n### Step 1: Confirm Inputs\n\n- If `research_notes.md` exists, read it first\n- Confirm with the user:\n  - Total slide count (e.g., 40, 60)\n  - Chapter (part) count and rough proportions\n  - Whether to include cover \u002F speaker intro \u002F contact slides (default: include all)\n\n---\n\n### Step 2: Write storyline.md\n\nConstruct the lecture's high-level flow narratively. Not just a table of contents — encode the logic of \"why this order\" so the audience journey is clear.\n\n```markdown\n# Storyline: [Topic]\n\n## Lecture Overview\n- Total slide count:\n- Presentation time:\n- Core message:\n\n## Overall Narrative Flow\n[3-5 paragraphs describing where the audience starts, what journey they take, and what they leave with]\n\n## Chapter Structure\n| # | Type | Title | Slide count | Key role |\n|---|------|------|------------|---------|\n| - | Cover | | 1 | Topic and speaker intro |\n| - | Speaker intro | | 1 | Build credibility |\n| 1 | PART | | N | |\n| 2 | PART | | N | |\n| - | Contact | | 1 | Closing and follow-up |\n\n## Key Takeaways\nWhat the audience should remember after the lecture:\n1.\n2.\n3.\n```\n\n---\n\n### Step 3: Write slide_deck.md\n\nWrite per-slide content. This file becomes the direct input for HTML generation.\n\n```markdown\n# Slide Deck: [Topic]\n\n---\n## [Slide number]. [Slide type] — [Title]\n\n**Section**: [section name shown in header]\n**Type**: cover \u002F speaker intro \u002F divider \u002F standard \u002F contact\n**Script**: [Speaker narration text — 2-4 sentences, natural spoken style. Required for every slide. Write in `script_language` from lecture-profile.md (defaults to `language`).]\n\n### Content\n- Bullet 1\n- Bullet 2\n- Bullet 3\n\n### Right Panel\n- Type: image \u002F text box\n- Image: [search keyword or filename]\n- Text title: [if any]\n- Text body: [if any]\n\n---\n```\n\nRepeat this structure for every slide. Dividers include part number and description.\n\n> Korean example (actual slide content for a Korean lecture is written in Korean):\n>\n> ```markdown\n> ## 5. divider — The Arrival of the AX Era\n>\n> **Section**: PART 01\n> **Type**: divider\n>\n> ### Content\n> - Paradigm shift in the securities industry\n> - Definition of AX (AI Transformation)\n> ```\n\n> ⚠️ **Uniform Layout Principle**: All content slides within a single deck MUST use `standard` type. Special types (`punchline`, `divider`, `profile`) are reserved for their designated structural purpose only. `punchline` is allowed ONLY as the last content slide with a single-statement message (≤1 line, no bullets). Mixing slide types for content slides is prohibited — each type has a distinct CSS layout (2-column vs center-aligned), and mixing breaks visual consistency.\n\n---\n\n### Step 4: Balance Check\n\nSelf-review after writing both files:\n\n- Are slide counts balanced across chapters (within ±20%)?\n- Any slides with too many bullets? (4 max recommended, 5 is hard limit)\n- No more than 3 consecutive slides without visuals?\n- Does every slide have a `script` field with narration text?\n- If multi-language narration is requested, do translated script fields exist?\n- **Uniform Layout check**: Do ALL content slides (between cover and closing) use `type: standard`? If any content slide uses `punchline` or another non-standard type, convert it to `standard`.\n\n---\n\n## Output Format\n\n- `presentations\u002F\u003Cproject>\u002Fstoryline.md` — narrative flow with chapter structure table\n- `presentations\u002F\u003Cproject>\u002Fslide_deck.md` — per-slide content with type, content bullets, and right-panel spec\n\n## Related Skills\n\n- `research` — produces `research_notes.md` consumed by this skill\n- `design` — consumes `slide_deck.md` output from this skill\n","## Context\n\nDesigns the lecture narrative flow (`storyline.md`) and per-slide content (`slide_deck.md`). `slide_deck.md` is the direct input consumed by the Build Agent for HTML generation. Invoked at Stages 2-3, after research and optional source verification.\n\n## When to Use\n\n- PM Agent dispatches after Stage 1 (research)\n- User says \"make storyline\"\n- User says \"compose slide deck\"\n- User says \"restructure chapters\"\n\n---\n\n## Execution Steps\n\n### Step 1: Confirm Inputs\n\n- If `research_notes.md` exists, read it first\n- Confirm with the user:\n  - Total slide count (e.g., 40, 60)\n  - Chapter (part) count and rough proportions\n  - Whether to include cover \u002F speaker intro \u002F contact slides (default: include all)\n\n---\n\n### Step 2: Write storyline.md\n\nConstruct the lecture's high-level flow narratively. Not just a table of contents — encode the logic of \"why this order\" so the audience journey is clear.\n\n```markdown\n# Storyline: [Topic]\n\n## Lecture Overview\n- Total slide count:\n- Presentation time:\n- Core message:\n\n## Overall Narrative Flow\n[3-5 paragraphs describing where the audience starts, what journey they take, and what they leave with]\n\n## Chapter Structure\n| # | Type | Title | Slide count | Key role |\n|---|------|------|------------|---------|\n| - | Cover | | 1 | Topic and speaker intro |\n| - | Speaker intro | | 1 | Build credibility |\n| 1 | PART | | N | |\n| 2 | PART | | N | |\n| - | Contact | | 1 | Closing and follow-up |\n\n## Key Takeaways\nWhat the audience should remember after the lecture:\n1.\n2.\n3.\n```\n\n---\n\n### Step 3: Write slide_deck.md\n\nWrite per-slide content. This file becomes the direct input for HTML generation.\n\n```markdown\n# Slide Deck: [Topic]\n\n---\n## [Slide number]. [Slide type] — [Title]\n\n**Section**: [section name shown in header]\n**Type**: cover \u002F speaker intro \u002F divider \u002F standard \u002F contact\n**Script**: [Speaker narration text — 2-4 sentences, natural spoken style. Required for every slide. Write in `script_language` from lecture-profile.md (defaults to `language`).]\n\n### Content\n- Bullet 1\n- Bullet 2\n- Bullet 3\n\n### Right Panel\n- Type: image \u002F text box\n- Image: [search keyword or filename]\n- Text title: [if any]\n- Text body: [if any]\n\n---\n```\n\nRepeat this structure for every slide. Dividers include part number and description.\n\n> Korean example (actual slide content for a Korean lecture is written in Korean):\n>\n> ```markdown\n> ## 5. divider — The Arrival of the AX Era\n>\n> **Section**: PART 01\n> **Type**: divider\n>\n> ### Content\n> - Paradigm shift in the securities industry\n> - Definition of AX (AI Transformation)\n> ```\n\n> ⚠️ **Uniform Layout Principle**: All content slides within a single deck MUST use `standard` type. Special types (`punchline`, `divider`, `profile`) are reserved for their designated structural purpose only. `punchline` is allowed ONLY as the last content slide with a single-statement message (≤1 line, no bullets). Mixing slide types for content slides is prohibited — each type has a distinct CSS layout (2-column vs center-aligned), and mixing breaks visual consistency.\n\n---\n\n### Step 4: Balance Check\n\nSelf-review after writing both files:\n\n- Are slide counts balanced across chapters (within ±20%)?\n- Any slides with too many bullets? (4 max recommended, 5 is hard limit)\n- No more than 3 consecutive slides without visuals?\n- Does every slide have a `script` field with narration text?\n- If multi-language narration is requested, do translated script fields exist?\n- **Uniform Layout check**: Do ALL content slides (between cover and closing) use `type: standard`? If any content slide uses `punchline` or another non-standard type, convert it to `standard`.\n\n---\n\n## Output Format\n\n- `presentations\u002F\u003Cproject>\u002Fstoryline.md` — narrative flow with chapter structure table\n- `presentations\u002F\u003Cproject>\u002Fslide_deck.md` — per-slide content with type, content bullets, and right-panel spec\n\n## Related Skills\n\n- `research` — produces `research_notes.md` consumed by this skill\n- `design` — consumes `slide_deck.md` output from this skill\n",{"name":5,"owner":5,"scope":23,"inputs":24,"status":26,"outputs":27,"version":30,"relates_to":31,"description":35,"last_reviewed":36,"prerequisites":37},"co-deck",[25],"research-notes","active",[28,29],"storyline-outline","slide-deck-draft","1.2.0",[32],{"type":33,"skill":34},"follows","design","Designs lecture storyline and slide deck composition. Given research_notes.md (or direct topic input), produces storyline.md and slide_deck.md. Responds to \"make storyline\", \"compose slide deck\", \"structure chapters\" (Korean: \"make storyline\", \"compose slide deck\", \"restructure chapters\"). Stages 2-3 of the lecture workflow.\n",1781827200000,"research","main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fco-deck\u002F.claude\u002Fskills\u002Fstoryline",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill storyline",{"tool":52,"command":53},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill storyline",{"tool":55,"command":56},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill storyline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-deck\u002F.claude\u002Fskills\u002Fstoryline\u002FSKILL.md",true,[],[61,69,74,79,84,89],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":70,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":68},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":75,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":68},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":80,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":68},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":85,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":68},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":90,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":68},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]