{"schemaVersion":"drillso.agent.session.v1","scope":"node","resource":{"type":"shared-session","shareId":"C6j7J1Pqk2dm","title":"独立开发增长营销流量综合阅读书单推荐","canonicalUrl":"https://drillso.com/en/share/sessions/C6j7J1Pqk2dm/%E4%B8%BA%E4%BB%80%E4%B9%88%E4%BA%BA%E4%BA%BA%E9%83%BD%E6%98%AF%E4%BA%A7%E5%93%81%E7%BB%8F%E7%90%86%EF%BC%9F-417a35cd","agentUrl":"https://drillso.com/en/share/sessions/C6j7J1Pqk2dm/agent.json?node=%E4%B8%BA%E4%BB%80%E4%B9%88%E4%BA%BA%E4%BA%BA%E9%83%BD%E6%98%AF%E4%BA%A7%E5%93%81%E7%BB%8F%E7%90%86%EF%BC%9F-417a35cd","ownerName":"pyth0nb3st","updatedAt":"2026-05-23T12:00:09.819Z"},"currentNode":{"id":"417a35cd-a0de-4c55-9a22-be71034c7eb8","slug":"为什么人人都是产品经理？-417a35cd","title":"为什么“人人都是产品经理”？","type":"deck","url":"https://drillso.com/en/share/sessions/C6j7J1Pqk2dm/%E4%B8%BA%E4%BB%80%E4%B9%88%E4%BA%BA%E4%BA%BA%E9%83%BD%E6%98%AF%E4%BA%A7%E5%93%81%E7%BB%8F%E7%90%86%EF%BC%9F-417a35cd","agentUrl":"https://drillso.com/en/share/sessions/C6j7J1Pqk2dm/agent.json?node=%E4%B8%BA%E4%BB%80%E4%B9%88%E4%BA%BA%E4%BA%BA%E9%83%BD%E6%98%AF%E4%BA%A7%E5%93%81%E7%BB%8F%E7%90%86%EF%BC%9F-417a35cd","text":"{\n  \"style\": \"Neo-Retro Dev Deck / Pixel-Infographic Editorial\",\n  \"title\": \"为什么“人人都是产品经理”\",\n  \"format\": \"presenter_slides\",\n  \"slides\": [\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"不是转岗建议\",\n      \"layout\": \"封面式单页。左上大标题，中央一个像素风系统框图，把“用户需求、商业目标、实现路径”连成三节点结构，右下角放一句短结论。\",\n      \"status\": \"completed\",\n      \"message\": \"“人人都是产品经理”讲的是一种思维，不是一个职位\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/eh7kog0ffadmd17ymjqohay7-54539c9d19802eef22884ac2d4154dda.png\",\n      \"storageKey\": \"generated/drill/eh7kog0ffadmd17ymjqohay7-54539c9d19802eef22884ac2d4154dda.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 1: 不是转岗建议\\nMain message: “人人都是产品经理”讲的是一种思维，不是一个职位\\n\\nVisible text must be exactly these lines, with no extra words:\\n不是人人去做 PM\\n而是人人都在影响产品\\n产品 = 用户需求 × 商业目标 × 实现路径\\n\\nLayout:\\n封面式单页。左上大标题，中央一个像素风系统框图，把“用户需求、商业目标、实现路径”连成三节点结构，右下角放一句短结论。\\n\\nVisual style:\\n复古开发者社论风，轻网格背景，黑色线框，少量高对比强调色，像产品手册首页。\\n\\nAdditional image direction:\\nA Chinese presentation cover slide with a retro developer editorial feel. Show a clean off-white grid-paper background, sharp black typography, and a central pixel-infographic system diagram with three connected modules labeled 用户需求, 商业目标, 实现路径. The composition should feel like a smart developer manual cover, with strong hierarchy, minimal text, and one bold statement that this is not a job-title book but a way of thinking.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 1,\n      \"visibleText\": [\n        \"不是人人去做 PM\",\n        \"而是人人都在影响产品\",\n        \"产品 = 用户需求 × 商业目标 × 实现路径\"\n      ],\n      \"visualStyle\": \"复古开发者社论风，轻网格背景，黑色线框，少量高对比强调色，像产品手册首页。\",\n      \"speakerNotes\": \"开场先纠正书名带来的误解。源文明确指出，这本书的核心不是教你如何成为某个岗位上的产品经理，而是在传递更底层的观念：产品不是一个职位的工作，而是围绕用户需求、商业目标和实现路径的系统协作。这一页只讲一个点：它讲的是思维方式，而不是岗位名称。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in a Neo-Retro Dev Deck / Pixel-Infographic Editorial style.\\n\\nStrict content rule: the ONLY visible text on the slide must be exactly these three lines, and nothing else anywhere:\\n不是人人去做 PM\\n而是人人都在影响产品\\n产品 = 用户需求 × 商业目标 × 实现路径\\n\\nDesign direction:\\n- Chinese presentation cover slide, retro developer editorial feel.\\n- Light cream/off-white engineering notebook background with subtle square grid lines.\\n- Sharp black typography, bold geometric sans-serif, heavy condensed headline style.\\n- Strong hierarchy, minimal text, presentation-ready.\\n- Use thick black borders, modular rectangles, slight overlaps, pixel-infographic assembly.\\n- Style feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n\\nLayout:\\n- Top-left large headline block for the first two lines.\\n- Center a pixel-art system diagram with three connected modules arranged in a smart triangular or left-to-right flow, each module as a bold colored block with thick black border and simple pixel iconography. The modules should visually represent 用户需求, 商业目标, 实现路径, but DO NOT add any extra labels or captions beyond the exact required text lines.\\n- Use hot pink, bright yellow, cyan/light blue as the dominant accent colors, with black outlines and cream background.\\n- Bottom-right place the third line as a short conclusion block, integrated into the composition, using the exact text only.\\n- Add small motion arrows, pixel sparks, tiny gears, and editorial annotation marks as graphics only, not text.\\n- Make it feel like a polished manifesto-style developer manual cover, not sparse or placeholder.\\n\\nTypography and rendering:\\n- Ensure the three required lines are highly readable and accurately rendered in Chinese.\\n- No extra words, no subtitles, no logos, no UI chrome, no watermark, no signatures, no markdown symbols.\\n- No other visible text anywhere on the slide.\\n- Keep the composition cohesive, finished, and visually balanced.\\n\\nVisual vibe:\\n- Clean off-white grid-paper background.\\n- Black borders and typography.\\n- Hot pink/yellow/cyan modular blocks.\\n- Retro pixel-infographic editorial composition, strong and smart, like a product thinking handbook cover.\",\n      \"storageFileId\": \"eh7kog0ffadmd17ymjqohay7-54539c9d19802eef22884ac2d4154dda\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"为什么是“人人”\",\n      \"layout\": \"人物职能地图。中间一个像素风独立开发者角色，周围环绕六个职责卡片，用连线形成星状结构。\",\n      \"status\": \"completed\",\n      \"message\": \"因为每个岗位都在影响价值交付\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/t21udsfpuxu88de9tcbj5ed4-531d26ae4c81f5b7be339239fc1ba1b8.png\",\n      \"storageKey\": \"generated/drill/t21udsfpuxu88de9tcbj5ed4-531d26ae4c81f5b7be339239fc1ba1b8.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 2: 为什么是“人人”\\nMain message: 因为每个岗位都在影响价值交付\\n\\nVisible text must be exactly these lines, with no extra words:\\n独立开发者常常一人多职\\n产品经理\\n用户研究\\n文案策划\\n运营 数据分析 客服销售\\n\\nLayout:\\n人物职能地图。中间一个像素风独立开发者角色，周围环绕六个职责卡片，用连线形成星状结构。\\n\\nVisual style:\\n像素人物 + 信息卡片，轻量注释感，强调多角色切换。\\n\\nAdditional image direction:\\nCreate a Chinese slide showing a solo indie developer in the center as a pixel-art or simplified illustrated figure, surrounded by six connected role cards: 产品经理, 用户研究, 文案策划, 运营, 数据分析, 客服与销售. Use a clean grid background and black UI-like connector lines. The slide should communicate that one person often covers many roles in early-stage products.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 2,\n      \"visibleText\": [\n        \"独立开发者常常一人多职\",\n        \"产品经理\",\n        \"用户研究\",\n        \"文案策划\",\n        \"运营 数据分析 客服销售\"\n      ],\n      \"visualStyle\": \"像素人物 + 信息卡片，轻量注释感，强调多角色切换。\",\n      \"speakerNotes\": \"这一页承接上一页。源文给出的具体背景是：这本书会出现在增长营销书单中，是因为独立开发者经常同时扮演产品经理、用户研究员、文案策划、运营、数据分析师、客服与销售等多个角色。所以“人人”不是抽象口号，而是现实分工。每个动作都会影响产品最终如何被理解、被使用、被付费。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, landscape 1536x864, Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Light cream off-white background with subtle square engineering grid. Thick black borders, modular collage layout, retro-futuristic editorial infographic, pixel-art accents, clean but rebellious. Chinese slide, high presentation quality, no extra text anywhere except the required visible text lines below. Make all text large, readable, bold black geometric sans serif. Use hot pink, bright yellow, cyan blocks with black outlines. Strong centered composition.\\n\\nLayout: A central pixel-art solo indie developer character, simplified illustrated figure, standing on a yellow-pink platform in the middle. Around the character, connect six role cards with black UI-like connector lines in a star map. The cards should be visually distinct and finished, with one dominant color block each, slight overlap, and small pixel icons. The center figure should look like one person wearing dev hoodie/laptop vibe, suggesting one person covers many jobs. Add small pixel arrows and sparks to emphasize multi-role switching. Use editorial annotation feel, not corporate.\\n\\nIMPORTANT TEXT RULE: The only visible text on the slide must be exactly these five lines, placed as the role labels / headline text, with no additional words, captions, numbers, logos, or watermarks:\\n独立开发者常常一人多职\\n产品经理\\n用户研究\\n文案策划\\n运营 数据分析 客服销售\\n\\nDo not add any other text. Ensure the last line appears exactly as written, with spaces between 运营 数据分析 客服销售. Use the same Chinese text as the only labels. Make the slide cohesive and visually finished, not sparse. Avoid gradients, photos, realistic rendering, soft shadows, browser chrome, or template placeholders.\",\n      \"storageFileId\": \"t21udsfpuxu88de9tcbj5ed4-531d26ae4c81f5b7be339239fc1ba1b8\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"产品思维的起点\",\n      \"layout\": \"左右对比。左侧是“功能导向”清单，右侧是“任务导向”问题卡，中央用箭头表示思维切换。\",\n      \"status\": \"completed\",\n      \"message\": \"先问用户想完成什么，而不是先想自己能做什么\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/dsf58cc2l8f75bszthqcamwi-0bd5f444762c8f1f423f61ba5f7a8445.png\",\n      \"storageKey\": \"generated/drill/dsf58cc2l8f75bszthqcamwi-0bd5f444762c8f1f423f61ba5f7a8445.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 3: 产品思维的起点\\nMain message: 先问用户想完成什么，而不是先想自己能做什么\\n\\nVisible text must be exactly these lines, with no extra words:\\n不是\\n我要加更多模型\\n我要做更炫功能\\n而是\\n用户真正想完成什么任务\\n为什么会放弃现有方案\\n\\nLayout:\\n左右对比。左侧是“功能导向”清单，右侧是“任务导向”问题卡，中央用箭头表示思维切换。\\n\\nVisual style:\\n终端式对照板，左红右绿式逻辑反差，但整体保持纸面像素信息图风格。\\n\\nAdditional image direction:\\nA Chinese comparison slide with two columns. Left column labeled with a function-first mindset, listing ideas like 更多模型, 更快响应, 更炫功能. Right column labeled with a product-thinking mindset, showing questions like 用户真正想完成什么任务 and 为什么会放弃现有方案. Use a retro UI comparison board aesthetic, with black divider lines, subtle grid, and a strong center arrow showing the shift.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 3,\n      \"visibleText\": [\n        \"不是\",\n        \"我要加更多模型\",\n        \"我要做更炫功能\",\n        \"而是\",\n        \"用户真正想完成什么任务\",\n        \"为什么会放弃现有方案\"\n      ],\n      \"visualStyle\": \"终端式对照板，左红右绿式逻辑反差，但整体保持纸面像素信息图风格。\",\n      \"speakerNotes\": \"这里使用源文里的 AI 写作工具例子。只会写代码时，可能首先想到更多模型、更快响应、更炫功能。但产品思维会逼你先问：用户真正想完成什么任务，他们为什么放弃现有方案，第一次使用卡在哪里，他们愿意为什么付费。核心转折是从“我能做什么”切换到“用户需要什么、业务需要什么、我该如何平衡”。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Light cream off-white engineering notebook grid background, subtle square grid lines, thick black borders, retro computer manual meets modern AI dev deck, pixel-art UI, slightly rebellious editorial layout.\\n\\nSlide content in Chinese only, with NO extra words anywhere else. Visible text must be exactly these lines and nothing else:\\n不是\\n我要加更多模型\\n我要做更炫功能\\n而是\\n用户真正想完成什么任务\\n为什么会放弃现有方案\\n\\nComposition: a strong left-right comparison board. Left side is function-first mindset with a terminal-like card stack in warm red / hot pink / red-orange tones, thick black border, simple pixel icons of gears, code brackets, sparkles, and small blocky UI chips, arranged like a checklist of feature thoughts. Right side is product-thinking mindset with a task-oriented question card in green / mint / cyan tones, thick black border, pixel icons of user, target, chat bubble, browser window, and a bigger more confident card. Center has a large bold arrow showing the shift from left to right, black outline, retro UI style, slightly overlapping the two columns.\\n\\nTypography: huge bold geometric sans serif Chinese text, black, slightly condensed, highly readable. Make the six provided lines the only readable text, each line large and clear in stacked blocks. No other labels, no title, no footer, no watermark, no browser chrome.\\n\\nVisual style: terminal-style contrast board, left warm/red and right green/teal logic contrast, paper-like pixel information graphic, controlled imperfect collage, black divider lines, subtle motion lines and pixel sparks, presentation-ready, cohesive, finished, not sparse, not minimalist, no gradients, no realistic photos, no soft shadows, no extra captions, no fake logos.\",\n      \"storageFileId\": \"dsf58cc2l8f75bszthqcamwi-0bd5f444762c8f1f423f61ba5f7a8445\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"需求有层次\",\n      \"layout\": \"三层向下钻取图。顶部是用户原话气泡，中间是问题理解层，底部是潜在目标与更优方案卡片。\",\n      \"status\": \"completed\",\n      \"message\": \"功能请求不等于真实问题\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/b24zwjh5ibcv7q6lgavdg9u8-ddb553aaf2ffd2011e6dcf8c16b5991f.png\",\n      \"storageKey\": \"generated/drill/b24zwjh5ibcv7q6lgavdg9u8-ddb553aaf2ffd2011e6dcf8c16b5991f.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 4: 需求有层次\\nMain message: 功能请求不等于真实问题\\n\\nVisible text must be exactly these lines, with no extra words:\\n表层需求\\n我想要番茄钟\\n真实需求\\n我想减少拖延\\n潜在需求\\n我想更容易进入专注状态\\n\\nLayout:\\n三层向下钻取图。顶部是用户原话气泡，中间是问题理解层，底部是潜在目标与更优方案卡片。\\n\\nVisual style:\\n像素信息结构图，带少量聊天气泡和分层箭头，强调从表象到本质。\\n\\nAdditional image direction:\\nDesign a Chinese slide as a three-layer needs analysis diagram. Top layer: a speech bubble saying 我想要一个番茄钟功能. Middle layer: 真实需求 with 减少拖延. Bottom layer: 潜在需求 with 更容易进入专注状态, plus small product-solution cards such as 自动进入专注模式, 任务拆分提示, 干扰屏蔽, 专注记录反馈. Keep it diagrammatic, clean, and developer-editorial.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 4,\n      \"visibleText\": [\n        \"表层需求\",\n        \"我想要番茄钟\",\n        \"真实需求\",\n        \"我想减少拖延\",\n        \"潜在需求\",\n        \"我想更容易进入专注状态\"\n      ],\n      \"visualStyle\": \"像素信息结构图，带少量聊天气泡和分层箭头，强调从表象到本质。\",\n      \"speakerNotes\": \"这一页讲书中最关键的概念之一：用户需求是起点，而且需求有层次。源文把需求分成表层需求、真实需求、潜在需求，并用番茄钟举例。用户提出“我想要一个番茄钟功能”只是表层；继续追问后发现他不是想要计时器，而是想减少拖延、进入专注状态。所以更好的方案可能不是单纯做个计时器，而是自动专注模式、任务拆分提示、干扰屏蔽、专注反馈。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, landscape 1536x864, in the Neo-Retro Dev Deck / Pixel-Infographic Editorial style.\\n\\nLanguage: Chinese. Keep all visible text EXACTLY these six lines and no extra words anywhere on the slide:\\n表层需求\\n我想要番茄钟\\n真实需求\\n我想减少拖延\\n潜在需求\\n我想更容易进入专注状态\\n\\nDesign the slide as a three-layer needs analysis diagram with a developer-editorial, pixel-infographic feel.\\n\\nComposition:\\n- Light cream/off-white engineering notebook background with subtle square grid lines.\\n- Strong stacked modular layout, thick black borders, slight overlaps, collage-like assembly.\\n- Top layer: a hot-pink speech bubble / user quote card for 表层需求 and 我想要番茄钟.\\n- Middle layer: a yellow problem-understanding block for 真实需求 and 我想减少拖延.\\n- Bottom layer: a cyan deeper-need block for 潜在需求 and 我想更容易进入专注状态.\\n- Use downward drill arrows or pixel chevrons between layers to show progression from surface to core.\\n- Add a few small pixel-art icons only, no text: clock, arrow-down, brain, focus ring, shield from distractions, notebook, gears.\\n- At the bottom, add small unlabeled solution-card visuals as tiny icon boxes only, without any additional text.\\n\\nTypography:\\n- Bold geometric sans serif, black, slightly condensed, high contrast, presentation-ready.\\n- The six required lines should be large and readable at presentation distance.\\n- No other labels, captions, bullet points, logos, watermarks, or UI chrome.\\n\\nColor palette:\\n- Hot pink for surface/agent/intelligence concept.\\n- Bright yellow for problem/friction/tools concept.\\n- Cyan/light blue for deeper needs and execution.\\n- Black borders and text.\\n- Cream background.\\n\\nVisual mood:\\n- Confident, playful, opinionated, slightly rebellious.\\n- Like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Finished, polished, coherent, not sparse.\\n\\nImportant constraints:\\n- One slide only, not a contact sheet.\\n- No extra visible text beyond the six required lines.\\n- Keep the slide clean, diagrammatic, and highly legible.\\n- No realistic photos, no gradients, no soft shadows, no corporate template look.\",\n      \"storageFileId\": \"b24zwjh5ibcv7q6lgavdg9u8-ddb553aaf2ffd2011e6dcf8c16b5991f\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"产品经理像桥梁\",\n      \"layout\": \"十字平衡图或四象限约束图。中央是“产品决策”，四周四个约束模块向内汇聚。\",\n      \"status\": \"completed\",\n      \"message\": \"产品决策是在多种约束之间做平衡\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/v8mg9vidsy1xoc2h0kf75xxy-c672b4b444803d2332b7a443148ca262.png\",\n      \"storageKey\": \"generated/drill/v8mg9vidsy1xoc2h0kf75xxy-c672b4b444803d2332b7a443148ca262.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 5: 产品经理像桥梁\\nMain message: 产品决策是在多种约束之间做平衡\\n\\nVisible text must be exactly these lines, with no extra words:\\n用户价值\\n商业价值\\n技术可行性\\n资源限制\\n选当前最合适的方案\\n\\nLayout:\\n十字平衡图或四象限约束图。中央是“产品决策”，四周四个约束模块向内汇聚。\\n\\nVisual style:\\n工程图纸式信息图，细线结构，像系统架构决策板。\\n\\nAdditional image direction:\\nCreate a Chinese slide with a central decision hub labeled 产品决策, connected to four surrounding blocks: 用户价值, 商业价值, 技术可行性, 资源限制. The composition should resemble a clean architecture decision diagram on grid paper, with thin connector lines and a precise retro-tech manual feel.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 5,\n      \"visibleText\": [\n        \"用户价值\",\n        \"商业价值\",\n        \"技术可行性\",\n        \"资源限制\",\n        \"选当前最合适的方案\"\n      ],\n      \"visualStyle\": \"工程图纸式信息图，细线结构，像系统架构决策板。\",\n      \"speakerNotes\": \"源文指出，产品经理的经典认知是桥梁角色。未必直接写代码，也未必直接做设计，但负责把不同目标协调起来。常见约束包括用户价值、商业价值、技术可行性、资源限制。文中用一句近似公式表达本质：产品决策不是选最好，而是选当前最合适。这里不要展开太多，用视觉强调平衡关系即可。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, no extra pages, no contact sheet. Design a Neo-Retro Dev Deck / Pixel-Infographic Editorial slide with a light cream off-white engineering notebook grid background, subtle square grid lines, thick black borders, flat retro-tech shapes, and a precise system-architecture decision diagram feel.\\n\\nSlide topic: 产品经理像桥梁 / 产品决策是在多种约束之间做平衡.\\n\\nComposition:\\n- Center a bold decision hub labeled exactly: 产品决策\\n- Surround it with four modular constraint blocks arranged like a clean cross / four-quadrant architecture board, all connected inward with thin black connector lines and arrow-like chevrons.\\n- Each surrounding block should be a distinct color block from the strict palette, with one dominant color per section:\\n  1) Hot pink block: 用户价值\\n  2) Bright yellow block: 商业价值\\n  3) Cyan/light blue block: 技术可行性\\n  4) Cream/black-anchored block with accent: 资源限制\\n- The center should feel like the hub where these constraints converge.\\n- Add a final outcome line as a bottom or side callout, bold and readable: 选当前最合适的方案\\n- Keep the slide presentation-ready, polished, and visually finished, with editorial rhythm and controlled overlap.\\n\\nTypography:\\n- Heavy geometric sans serif, bold black headline treatment.\\n- Chinese text should be large, crisp, and highly legible at presentation distance.\\n- No extra captions, no decorative filler text, no fake UI, no logos, no watermarks.\\n\\nStyle specifics:\\n- Retro-futuristic, developer-centric, opinionated, slightly rebellious.\\n- Pixel-art inspired micro-icons or symbols can appear subtly in or near the blocks (e.g., tiny gear, code brackets, browser/agent motifs), but do not add any extra words.\\n- Thin technical connector lines, precise alignment, modular cards, slight collage overlap, engineering diagram clarity.\\n- Avoid gradients, realistic photos, soft shadows, corporate PPT look, and minimal emptiness.\\n\\nVisible text must be limited to these Chinese phrases only:\\n产品决策\\n用户价值\\n商业价值\\n技术可行性\\n资源限制\\n选当前最合适的方案\\n\\nEnsure all text is readable and there are no additional words, letters, or captions anywhere else on the slide.\",\n      \"storageFileId\": \"v8mg9vidsy1xoc2h0kf75xxy-c672b4b444803d2332b7a443148ca262\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"需求不是越多越好\",\n      \"layout\": \"左侧堆叠反馈便签，右侧优先级漏斗或筛选器，底部输出一个“先做注册流程优化”的高亮结果卡。\",\n      \"status\": \"completed\",\n      \"message\": \"关键能力不是收集需求，而是判断优先级\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/lg6rpcuhd2fy29wh1ay68ppv-67646c7e658f598f0232e290a6697a83.png\",\n      \"storageKey\": \"generated/drill/lg6rpcuhd2fy29wh1ay68ppv-67646c7e658f598f0232e290a6697a83.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 6: 需求不是越多越好\\nMain message: 关键能力不是收集需求，而是判断优先级\\n\\nVisible text must be exactly these lines, with no extra words:\\n10 条反馈 不等于 10 个待做功能\\n先看\\n核心用户\\n高频痛点\\n关键指标\\n实现成本 产品阶段\\n\\nLayout:\\n左侧堆叠反馈便签，右侧优先级漏斗或筛选器，底部输出一个“先做注册流程优化”的高亮结果卡。\\n\\nVisual style:\\n像素便签 + 过滤器信息图，强调从杂音到主线。\\n\\nAdditional image direction:\\nA Chinese slide showing many incoming feedback notes on the left, such as 深色模式, 导出 PDF, 接入 Notion, 团队协作, 多语言. On the right, show a filtering funnel labeled 核心用户, 高频痛点, 关键指标, 实现成本, 产品阶段, ending in one highlighted choice like 优化注册流程. Use a clean pixel-infographic editorial layout.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 6,\n      \"visibleText\": [\n        \"10 条反馈 不等于 10 个待做功能\",\n        \"先看\",\n        \"核心用户\",\n        \"高频痛点\",\n        \"关键指标\",\n        \"实现成本 产品阶段\"\n      ],\n      \"visualStyle\": \"像素便签 + 过滤器信息图，强调从杂音到主线。\",\n      \"speakerNotes\": \"这一页基于源文中关于优先级的部分。很多初学者误以为产品经理的工作是收集需求，但更关键的是判断哪些值得做、什么时候做、为什么做。判断标准包括是否影响核心用户、是否解决高频痛点、是否能提升关键指标、实现成本是否合理、是否符合产品阶段。可以顺带提到那个例子：在早期验证阶段，优化注册流程可能比深色模式更重要。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, landscape 1536x864, in a Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Light cream/off-white engineering notebook grid background with subtle square grid lines. Retro-futuristic, developer-centric, editorial infographic feel: 90s computer manual mixed with modern AI dev tools marketing, pixel art meets startup slide deck, confident playful opinionated slightly rebellious.\\n\\nSlide topic in Chinese: 需求不是越多越好. Main message: 关键能力不是收集需求，而是判断优先级.\\n\\nComposition: left side stacked incoming feedback sticky notes in pixel style, thick black borders, slightly overlapping, varied colors but controlled palette; notes should include readable Chinese items such as 深色模式, 导出 PDF, 接入 Notion, 团队协作, 多语言, plus small extra feedback note shapes. Right side a large filtering funnel / sorter infographic with stacked stages, each stage in a boxed label and thick black outline, ending in a bright highlighted output card at bottom. Bottom output card should be prominent and read: 先做注册流程优化. Emphasize that 10 feedbacks do not equal 10 features. Use visual motion from noisy notes to focused mainline.\\n\\nVisible text must be exactly these lines, with no extra words:\\n10 条反馈 不等于 10 个待做功能\\n先看\\n核心用户\\n高频痛点\\n关键指标\\n实现成本 产品阶段\\n\\nDo not add any other visible text except the specified lines and the Chinese feedback note labels already requested in the layout direction (深色模式, 导出 PDF, 接入 Notion, 团队协作, 多语言) and the output card text 先做注册流程优化. Make sure all visible text is readable at presentation distance. Large bold headline at top-left or top-center, slightly condensed geometric sans serif in black. Underline/section labels small clean type. Use hot pink for agent/priority emphasis, bright yellow for code/tools/feedback, cyan/light blue for browser/execution, black for text and borders, cream background. Stack modular blocks with rectangles and slight overlaps, horizontal section bars, arrows, chevrons, pixel sparks. Pixel-art icons: sticky notes, filter funnel, magnifying glass, gear, arrows. Controlled imperfection, assembled not sterile. No gradients, no soft shadows, no corporate template, no photorealism, no browser chrome, no watermark. Presentation-ready, cohesive, polished, strong hierarchy, editorial rhythm.\",\n      \"storageFileId\": \"lg6rpcuhd2fy29wh1ay68ppv-67646c7e658f598f0232e290a6697a83\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"它为什么对增长有用\",\n      \"layout\": \"横向流程图，一条从左到右的增长链路，阶段卡片逐步递进，最后两个结果节点突出。\",\n      \"status\": \"completed\",\n      \"message\": \"增长不只靠流量，更取决于前面的判断\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/p5xs5uy98awd04jn0ox3c1sw-d0e384db961c1e95515784199dd837b3.png\",\n      \"storageKey\": \"generated/drill/p5xs5uy98awd04jn0ox3c1sw-d0e384db961c1e95515784199dd837b3.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 7: 它为什么对增长有用\\nMain message: 增长不只靠流量，更取决于前面的判断\\n\\nVisible text must be exactly these lines, with no extra words:\\n用户问题\\n需求洞察\\n产品方案\\n首次体验\\n持续使用\\n付费与传播\\n\\nLayout:\\n横向流程图，一条从左到右的增长链路，阶段卡片逐步递进，最后两个结果节点突出。\\n\\nVisual style:\\n开发工作流海报感，步骤清晰，像构建流水线。\\n\\nAdditional image direction:\\nDesign a Chinese horizontal workflow slide with six connected stages: 用户问题 → 需求洞察 → 产品方案 → 首次体验 → 持续使用 → 付费与传播. Make it feel like a product-growth pipeline in a retro dev infographic style, using modular boxes, arrows, and strong editorial hierarchy on a subtle grid background.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 7,\n      \"visibleText\": [\n        \"用户问题\",\n        \"需求洞察\",\n        \"产品方案\",\n        \"首次体验\",\n        \"持续使用\",\n        \"付费与传播\"\n      ],\n      \"visualStyle\": \"开发工作流海报感，步骤清晰，像构建流水线。\",\n      \"speakerNotes\": \"这一页直接对应源文第三部分。它说明这本书对增长营销的帮助，不在单点技巧，而在打通产品、转化、留存。文中给出了一条非常清晰的链路：用户问题到需求洞察，到产品方案，到首次体验，到持续使用，最后到付费与传播。重点强调一句：如果前面的洞察错了，后面的转化和留存都会吃亏。\",\n      \"revisedPrompt\": \"Create a single 1536x864 landscape presentation slide in the style of Neo-Retro Dev Deck / Pixel-Infographic Editorial. Light cream off-white background with subtle engineering notebook grid lines. Strong editorial composition, retro-futuristic developer infographic, pixel-art meets startup slide deck. Thick black borders, modular boxes, slight overlaps, assembled collage feel, no soft shadows, no gradients, no photos, no corporate look.\\n\\nSlide topic: Chinese horizontal workflow showing why growth is useful. Build a left-to-right product-growth pipeline with six connected stages, each as a distinct modular card with bold black outlined rectangles and color accents. The flow should feel like a development workflow poster. Use arrows and chevrons between cards. Make the last two nodes more prominent and colorful.\\n\\nIMPORTANT: The only visible text on the slide must be exactly these six lines, and nothing else anywhere:\\n用户问题\\n需求洞察\\n产品方案\\n首次体验\\n持续使用\\n付费与传播\\n\\nDo not add any extra text, labels, titles, subtitles, captions, numbers, logos, or watermarks.\\n\\nVisual structure:\\n- Six connected stage cards laid out horizontally across the slide from left to right.\\n- Stage 1 and 2 in hot pink dominant blocks, stage 3 in yellow, stage 4 in cyan, stage 5 and 6 emphasized larger with stronger color presence and thicker borders.\\n- Each card contains one bold Chinese line only, centered or slightly offset, with clean heavy geometric sans serif typography, black text.\\n- Add pixel-art icons in each card: user/problem bubble, magnifier/insight, tool/plan, first-use browser/app window, repeat/loop, coin/share burst. Icons must be low-resolution 8-bit/16-bit style with black outline and flat colors.\\n- Use arrows, small motion lines, tiny pixel sparks, and gear-like decorative elements to connect the stages.\\n- Overall layout should be balanced and presentation-ready, not sparse. Keep text highly readable at presentation distance.\\n- The final two stages, \\\"持续使用\\\" and \\\"付费与传播\\\", should be visually highlighted as the outcome nodes, slightly larger and more vivid, implying growth depends on earlier judgment.\\n\\nStyle details:\\n- Big bold headline feel through composition, but since only the six required lines may appear, use the cards themselves as the typographic focus.\\n- Strict palette: hot pink, bright yellow, cyan/light blue, black, cream, with occasional white negative space.\\n- Thick black outlines around all blocks and icons.\\n- Slight intentional misalignment and overlap for a hand-assembled editorial feel.\\n- Clean, finished, visually rich, and coherent with the template.\\n\\nNo extra visible text beyond the six specified Chinese lines. Ensure there is no hidden or tiny text anywhere else in the image.\",\n      \"storageFileId\": \"p5xs5uy98awd04jn0ox3c1sw-d0e384db961c1e95515784199dd837b3\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"避免自嗨式开发\",\n      \"layout\": \"上半部分三条误区警示，下半部分三条行动原则，形成一一对应的修正关系。\",\n      \"status\": \"completed\",\n      \"message\": \"先验证问题，再实现方案\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/ljv7dzw2oyijavl84b3o9dxq-500bd5a6d11ac8200877b32ff94e1e1d.png\",\n      \"storageKey\": \"generated/drill/ljv7dzw2oyijavl84b3o9dxq-500bd5a6d11ac8200877b32ff94e1e1d.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 8: 避免自嗨式开发\\nMain message: 先验证问题，再实现方案\\n\\nVisible text must be exactly these lines, with no extra words:\\n不要因为能做就做\\n不要因为自己喜欢就做\\n不要因为有人提了就立刻做\\n先验证问题\\n先看用户行为\\n先抓主线价值\\n\\nLayout:\\n上半部分三条误区警示，下半部分三条行动原则，形成一一对应的修正关系。\\n\\nVisual style:\\n像素警示牌与原则卡片结合，结尾页有强结论感。\\n\\nAdditional image direction:\\nCreate a Chinese closing slide with a clear before-and-after structure. Top half shows three anti-pattern warning cards: 因为能做就做, 因为自己喜欢就做, 因为有人提了就立刻做. Bottom half shows three corrective principles: 先验证问题, 先看用户行为, 先抓主线价值. Use bold black outlines, small accent color blocks, and a memorable retro-dev editorial composition.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 8,\n      \"visibleText\": [\n        \"不要因为能做就做\",\n        \"不要因为自己喜欢就做\",\n        \"不要因为有人提了就立刻做\",\n        \"先验证问题\",\n        \"先看用户行为\",\n        \"先抓主线价值\"\n      ],\n      \"visualStyle\": \"像素警示牌与原则卡片结合，结尾页有强结论感。\",\n      \"speakerNotes\": \"最后用一个收束页总结对独立开发者最现实的价值。源文说，这本书能帮助独立开发者避免自嗨式开发。常见误区包括：因为技术上能做所以做，因为自己喜欢所以觉得用户也喜欢，因为有人提了需求就立刻开发。对应的产品思维是：先验证问题，再实现方案；先看用户行为，再听用户表述；先抓主线价值，再做边缘功能。结尾可以再落回一句总括：这不是岗位指南，而是帮助你提升判断框架。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in a Neo-Retro Dev Deck / Pixel-Infographic Editorial style: light cream off-white engineering notebook grid background, thick black outlines, modular stacked blocks, retro-futuristic developer editorial composition, pixel-art warning icons, bold geometric sans typography, hot pink / bright yellow / cyan accents, slightly rebellious but clean and presentation-ready. The slide is a clear before-and-after structure with strong conclusion energy.\\n\\nIMPORTANT TEXT RULES: The ONLY visible text on the entire slide must be exactly these six Chinese lines, and nothing else anywhere on the image:\\n不要因为能做就做\\n不要因为自己喜欢就做\\n不要因为有人提了就立刻做\\n先验证问题\\n先看用户行为\\n先抓主线价值\\nDo not add any title, subtitle, labels, numbers, bullets, captions, watermarks, logos, UI chrome, or extra text of any kind.\\n\\nLAYOUT: Top half = three anti-pattern warning cards, each with a pixel warning sign / alert icon and one of the first three lines, arranged left to right. Bottom half = three corrective principle cards, each with a small pixel arrow / gear / check-style icon and one of the last three lines, also arranged left to right. Make the top half visually tense and cautionary with hot pink/yellow warning blocks; make the bottom half calmer and more decisive with cyan/yellow action blocks. Use thick black borders, slight overlaps, editorial rhythm, and one-to-one correspondence from each top card to the card below it. Add a strong central divider or arrowed transition between the halves, but without any extra text.\\n\\nSTYLE: pixel-art warning placards, retro manual aesthetics, 90s computer manual mixed with modern AI dev tools marketing, flat colors, no gradients, no shadows, no photorealism. Keep the six lines highly legible at presentation distance, large bold black text, aligned within their cards. The result should feel like a finished closing slide with a memorable retro-dev editorial composition.\",\n      \"storageFileId\": \"ljv7dzw2oyijavl84b3o9dxq-500bd5a6d11ac8200877b32ff94e1e1d\"\n    }\n  ],\n  \"styleId\": \"neo_retro_dev\",\n  \"summary\": \"这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\",\n  \"audience\": \"独立开发者、增长营销从业者、刚接触产品思维的创业者与内容读者\",\n  \"imageSize\": \"1536x864\",\n  \"imageModel\": \"gpt-image-2\",\n  \"plannerModel\": \"gpt-5.4\"\n}","markdown":"# 为什么“人人都是产品经理”？\n\n{\n  \"style\": \"Neo-Retro Dev Deck / Pixel-Infographic Editorial\",\n  \"title\": \"为什么“人人都是产品经理”\",\n  \"format\": \"presenter_slides\",\n  \"slides\": [\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"不是转岗建议\",\n      \"layout\": \"封面式单页。左上大标题，中央一个像素风系统框图，把“用户需求、商业目标、实现路径”连成三节点结构，右下角放一句短结论。\",\n      \"status\": \"completed\",\n      \"message\": \"“人人都是产品经理”讲的是一种思维，不是一个职位\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/eh7kog0ffadmd17ymjqohay7-54539c9d19802eef22884ac2d4154dda.png\",\n      \"storageKey\": \"generated/drill/eh7kog0ffadmd17ymjqohay7-54539c9d19802eef22884ac2d4154dda.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 1: 不是转岗建议\\nMain message: “人人都是产品经理”讲的是一种思维，不是一个职位\\n\\nVisible text must be exactly these lines, with no extra words:\\n不是人人去做 PM\\n而是人人都在影响产品\\n产品 = 用户需求 × 商业目标 × 实现路径\\n\\nLayout:\\n封面式单页。左上大标题，中央一个像素风系统框图，把“用户需求、商业目标、实现路径”连成三节点结构，右下角放一句短结论。\\n\\nVisual style:\\n复古开发者社论风，轻网格背景，黑色线框，少量高对比强调色，像产品手册首页。\\n\\nAdditional image direction:\\nA Chinese presentation cover slide with a retro developer editorial feel. Show a clean off-white grid-paper background, sharp black typography, and a central pixel-infographic system diagram with three connected modules labeled 用户需求, 商业目标, 实现路径. The composition should feel like a smart developer manual cover, with strong hierarchy, minimal text, and one bold statement that this is not a job-title book but a way of thinking.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 1,\n      \"visibleText\": [\n        \"不是人人去做 PM\",\n        \"而是人人都在影响产品\",\n        \"产品 = 用户需求 × 商业目标 × 实现路径\"\n      ],\n      \"visualStyle\": \"复古开发者社论风，轻网格背景，黑色线框，少量高对比强调色，像产品手册首页。\",\n      \"speakerNotes\": \"开场先纠正书名带来的误解。源文明确指出，这本书的核心不是教你如何成为某个岗位上的产品经理，而是在传递更底层的观念：产品不是一个职位的工作，而是围绕用户需求、商业目标和实现路径的系统协作。这一页只讲一个点：它讲的是思维方式，而不是岗位名称。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in a Neo-Retro Dev Deck / Pixel-Infographic Editorial style.\\n\\nStrict content rule: the ONLY visible text on the slide must be exactly these three lines, and nothing else anywhere:\\n不是人人去做 PM\\n而是人人都在影响产品\\n产品 = 用户需求 × 商业目标 × 实现路径\\n\\nDesign direction:\\n- Chinese presentation cover slide, retro developer editorial feel.\\n- Light cream/off-white engineering notebook background with subtle square grid lines.\\n- Sharp black typography, bold geometric sans-serif, heavy condensed headline style.\\n- Strong hierarchy, minimal text, presentation-ready.\\n- Use thick black borders, modular rectangles, slight overlaps, pixel-infographic assembly.\\n- Style feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n\\nLayout:\\n- Top-left large headline block for the first two lines.\\n- Center a pixel-art system diagram with three connected modules arranged in a smart triangular or left-to-right flow, each module as a bold colored block with thick black border and simple pixel iconography. The modules should visually represent 用户需求, 商业目标, 实现路径, but DO NOT add any extra labels or captions beyond the exact required text lines.\\n- Use hot pink, bright yellow, cyan/light blue as the dominant accent colors, with black outlines and cream background.\\n- Bottom-right place the third line as a short conclusion block, integrated into the composition, using the exact text only.\\n- Add small motion arrows, pixel sparks, tiny gears, and editorial annotation marks as graphics only, not text.\\n- Make it feel like a polished manifesto-style developer manual cover, not sparse or placeholder.\\n\\nTypography and rendering:\\n- Ensure the three required lines are highly readable and accurately rendered in Chinese.\\n- No extra words, no subtitles, no logos, no UI chrome, no watermark, no signatures, no markdown symbols.\\n- No other visible text anywhere on the slide.\\n- Keep the composition cohesive, finished, and visually balanced.\\n\\nVisual vibe:\\n- Clean off-white grid-paper background.\\n- Black borders and typography.\\n- Hot pink/yellow/cyan modular blocks.\\n- Retro pixel-infographic editorial composition, strong and smart, like a product thinking handbook cover.\",\n      \"storageFileId\": \"eh7kog0ffadmd17ymjqohay7-54539c9d19802eef22884ac2d4154dda\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"为什么是“人人”\",\n      \"layout\": \"人物职能地图。中间一个像素风独立开发者角色，周围环绕六个职责卡片，用连线形成星状结构。\",\n      \"status\": \"completed\",\n      \"message\": \"因为每个岗位都在影响价值交付\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/t21udsfpuxu88de9tcbj5ed4-531d26ae4c81f5b7be339239fc1ba1b8.png\",\n      \"storageKey\": \"generated/drill/t21udsfpuxu88de9tcbj5ed4-531d26ae4c81f5b7be339239fc1ba1b8.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 2: 为什么是“人人”\\nMain message: 因为每个岗位都在影响价值交付\\n\\nVisible text must be exactly these lines, with no extra words:\\n独立开发者常常一人多职\\n产品经理\\n用户研究\\n文案策划\\n运营 数据分析 客服销售\\n\\nLayout:\\n人物职能地图。中间一个像素风独立开发者角色，周围环绕六个职责卡片，用连线形成星状结构。\\n\\nVisual style:\\n像素人物 + 信息卡片，轻量注释感，强调多角色切换。\\n\\nAdditional image direction:\\nCreate a Chinese slide showing a solo indie developer in the center as a pixel-art or simplified illustrated figure, surrounded by six connected role cards: 产品经理, 用户研究, 文案策划, 运营, 数据分析, 客服与销售. Use a clean grid background and black UI-like connector lines. The slide should communicate that one person often covers many roles in early-stage products.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 2,\n      \"visibleText\": [\n        \"独立开发者常常一人多职\",\n        \"产品经理\",\n        \"用户研究\",\n        \"文案策划\",\n        \"运营 数据分析 客服销售\"\n      ],\n      \"visualStyle\": \"像素人物 + 信息卡片，轻量注释感，强调多角色切换。\",\n      \"speakerNotes\": \"这一页承接上一页。源文给出的具体背景是：这本书会出现在增长营销书单中，是因为独立开发者经常同时扮演产品经理、用户研究员、文案策划、运营、数据分析师、客服与销售等多个角色。所以“人人”不是抽象口号，而是现实分工。每个动作都会影响产品最终如何被理解、被使用、被付费。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, landscape 1536x864, Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Light cream off-white background with subtle square engineering grid. Thick black borders, modular collage layout, retro-futuristic editorial infographic, pixel-art accents, clean but rebellious. Chinese slide, high presentation quality, no extra text anywhere except the required visible text lines below. Make all text large, readable, bold black geometric sans serif. Use hot pink, bright yellow, cyan blocks with black outlines. Strong centered composition.\\n\\nLayout: A central pixel-art solo indie developer character, simplified illustrated figure, standing on a yellow-pink platform in the middle. Around the character, connect six role cards with black UI-like connector lines in a star map. The cards should be visually distinct and finished, with one dominant color block each, slight overlap, and small pixel icons. The center figure should look like one person wearing dev hoodie/laptop vibe, suggesting one person covers many jobs. Add small pixel arrows and sparks to emphasize multi-role switching. Use editorial annotation feel, not corporate.\\n\\nIMPORTANT TEXT RULE: The only visible text on the slide must be exactly these five lines, placed as the role labels / headline text, with no additional words, captions, numbers, logos, or watermarks:\\n独立开发者常常一人多职\\n产品经理\\n用户研究\\n文案策划\\n运营 数据分析 客服销售\\n\\nDo not add any other text. Ensure the last line appears exactly as written, with spaces between 运营 数据分析 客服销售. Use the same Chinese text as the only labels. Make the slide cohesive and visually finished, not sparse. Avoid gradients, photos, realistic rendering, soft shadows, browser chrome, or template placeholders.\",\n      \"storageFileId\": \"t21udsfpuxu88de9tcbj5ed4-531d26ae4c81f5b7be339239fc1ba1b8\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"产品思维的起点\",\n      \"layout\": \"左右对比。左侧是“功能导向”清单，右侧是“任务导向”问题卡，中央用箭头表示思维切换。\",\n      \"status\": \"completed\",\n      \"message\": \"先问用户想完成什么，而不是先想自己能做什么\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/dsf58cc2l8f75bszthqcamwi-0bd5f444762c8f1f423f61ba5f7a8445.png\",\n      \"storageKey\": \"generated/drill/dsf58cc2l8f75bszthqcamwi-0bd5f444762c8f1f423f61ba5f7a8445.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 3: 产品思维的起点\\nMain message: 先问用户想完成什么，而不是先想自己能做什么\\n\\nVisible text must be exactly these lines, with no extra words:\\n不是\\n我要加更多模型\\n我要做更炫功能\\n而是\\n用户真正想完成什么任务\\n为什么会放弃现有方案\\n\\nLayout:\\n左右对比。左侧是“功能导向”清单，右侧是“任务导向”问题卡，中央用箭头表示思维切换。\\n\\nVisual style:\\n终端式对照板，左红右绿式逻辑反差，但整体保持纸面像素信息图风格。\\n\\nAdditional image direction:\\nA Chinese comparison slide with two columns. Left column labeled with a function-first mindset, listing ideas like 更多模型, 更快响应, 更炫功能. Right column labeled with a product-thinking mindset, showing questions like 用户真正想完成什么任务 and 为什么会放弃现有方案. Use a retro UI comparison board aesthetic, with black divider lines, subtle grid, and a strong center arrow showing the shift.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 3,\n      \"visibleText\": [\n        \"不是\",\n        \"我要加更多模型\",\n        \"我要做更炫功能\",\n        \"而是\",\n        \"用户真正想完成什么任务\",\n        \"为什么会放弃现有方案\"\n      ],\n      \"visualStyle\": \"终端式对照板，左红右绿式逻辑反差，但整体保持纸面像素信息图风格。\",\n      \"speakerNotes\": \"这里使用源文里的 AI 写作工具例子。只会写代码时，可能首先想到更多模型、更快响应、更炫功能。但产品思维会逼你先问：用户真正想完成什么任务，他们为什么放弃现有方案，第一次使用卡在哪里，他们愿意为什么付费。核心转折是从“我能做什么”切换到“用户需要什么、业务需要什么、我该如何平衡”。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Light cream off-white engineering notebook grid background, subtle square grid lines, thick black borders, retro computer manual meets modern AI dev deck, pixel-art UI, slightly rebellious editorial layout.\\n\\nSlide content in Chinese only, with NO extra words anywhere else. Visible text must be exactly these lines and nothing else:\\n不是\\n我要加更多模型\\n我要做更炫功能\\n而是\\n用户真正想完成什么任务\\n为什么会放弃现有方案\\n\\nComposition: a strong left-right comparison board. Left side is function-first mindset with a terminal-like card stack in warm red / hot pink / red-orange tones, thick black border, simple pixel icons of gears, code brackets, sparkles, and small blocky UI chips, arranged like a checklist of feature thoughts. Right side is product-thinking mindset with a task-oriented question card in green / mint / cyan tones, thick black border, pixel icons of user, target, chat bubble, browser window, and a bigger more confident card. Center has a large bold arrow showing the shift from left to right, black outline, retro UI style, slightly overlapping the two columns.\\n\\nTypography: huge bold geometric sans serif Chinese text, black, slightly condensed, highly readable. Make the six provided lines the only readable text, each line large and clear in stacked blocks. No other labels, no title, no footer, no watermark, no browser chrome.\\n\\nVisual style: terminal-style contrast board, left warm/red and right green/teal logic contrast, paper-like pixel information graphic, controlled imperfect collage, black divider lines, subtle motion lines and pixel sparks, presentation-ready, cohesive, finished, not sparse, not minimalist, no gradients, no realistic photos, no soft shadows, no extra captions, no fake logos.\",\n      \"storageFileId\": \"dsf58cc2l8f75bszthqcamwi-0bd5f444762c8f1f423f61ba5f7a8445\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"需求有层次\",\n      \"layout\": \"三层向下钻取图。顶部是用户原话气泡，中间是问题理解层，底部是潜在目标与更优方案卡片。\",\n      \"status\": \"completed\",\n      \"message\": \"功能请求不等于真实问题\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/b24zwjh5ibcv7q6lgavdg9u8-ddb553aaf2ffd2011e6dcf8c16b5991f.png\",\n      \"storageKey\": \"generated/drill/b24zwjh5ibcv7q6lgavdg9u8-ddb553aaf2ffd2011e6dcf8c16b5991f.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 4: 需求有层次\\nMain message: 功能请求不等于真实问题\\n\\nVisible text must be exactly these lines, with no extra words:\\n表层需求\\n我想要番茄钟\\n真实需求\\n我想减少拖延\\n潜在需求\\n我想更容易进入专注状态\\n\\nLayout:\\n三层向下钻取图。顶部是用户原话气泡，中间是问题理解层，底部是潜在目标与更优方案卡片。\\n\\nVisual style:\\n像素信息结构图，带少量聊天气泡和分层箭头，强调从表象到本质。\\n\\nAdditional image direction:\\nDesign a Chinese slide as a three-layer needs analysis diagram. Top layer: a speech bubble saying 我想要一个番茄钟功能. Middle layer: 真实需求 with 减少拖延. Bottom layer: 潜在需求 with 更容易进入专注状态, plus small product-solution cards such as 自动进入专注模式, 任务拆分提示, 干扰屏蔽, 专注记录反馈. Keep it diagrammatic, clean, and developer-editorial.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 4,\n      \"visibleText\": [\n        \"表层需求\",\n        \"我想要番茄钟\",\n        \"真实需求\",\n        \"我想减少拖延\",\n        \"潜在需求\",\n        \"我想更容易进入专注状态\"\n      ],\n      \"visualStyle\": \"像素信息结构图，带少量聊天气泡和分层箭头，强调从表象到本质。\",\n      \"speakerNotes\": \"这一页讲书中最关键的概念之一：用户需求是起点，而且需求有层次。源文把需求分成表层需求、真实需求、潜在需求，并用番茄钟举例。用户提出“我想要一个番茄钟功能”只是表层；继续追问后发现他不是想要计时器，而是想减少拖延、进入专注状态。所以更好的方案可能不是单纯做个计时器，而是自动专注模式、任务拆分提示、干扰屏蔽、专注反馈。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, landscape 1536x864, in the Neo-Retro Dev Deck / Pixel-Infographic Editorial style.\\n\\nLanguage: Chinese. Keep all visible text EXACTLY these six lines and no extra words anywhere on the slide:\\n表层需求\\n我想要番茄钟\\n真实需求\\n我想减少拖延\\n潜在需求\\n我想更容易进入专注状态\\n\\nDesign the slide as a three-layer needs analysis diagram with a developer-editorial, pixel-infographic feel.\\n\\nComposition:\\n- Light cream/off-white engineering notebook background with subtle square grid lines.\\n- Strong stacked modular layout, thick black borders, slight overlaps, collage-like assembly.\\n- Top layer: a hot-pink speech bubble / user quote card for 表层需求 and 我想要番茄钟.\\n- Middle layer: a yellow problem-understanding block for 真实需求 and 我想减少拖延.\\n- Bottom layer: a cyan deeper-need block for 潜在需求 and 我想更容易进入专注状态.\\n- Use downward drill arrows or pixel chevrons between layers to show progression from surface to core.\\n- Add a few small pixel-art icons only, no text: clock, arrow-down, brain, focus ring, shield from distractions, notebook, gears.\\n- At the bottom, add small unlabeled solution-card visuals as tiny icon boxes only, without any additional text.\\n\\nTypography:\\n- Bold geometric sans serif, black, slightly condensed, high contrast, presentation-ready.\\n- The six required lines should be large and readable at presentation distance.\\n- No other labels, captions, bullet points, logos, watermarks, or UI chrome.\\n\\nColor palette:\\n- Hot pink for surface/agent/intelligence concept.\\n- Bright yellow for problem/friction/tools concept.\\n- Cyan/light blue for deeper needs and execution.\\n- Black borders and text.\\n- Cream background.\\n\\nVisual mood:\\n- Confident, playful, opinionated, slightly rebellious.\\n- Like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Finished, polished, coherent, not sparse.\\n\\nImportant constraints:\\n- One slide only, not a contact sheet.\\n- No extra visible text beyond the six required lines.\\n- Keep the slide clean, diagrammatic, and highly legible.\\n- No realistic photos, no gradients, no soft shadows, no corporate template look.\",\n      \"storageFileId\": \"b24zwjh5ibcv7q6lgavdg9u8-ddb553aaf2ffd2011e6dcf8c16b5991f\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"产品经理像桥梁\",\n      \"layout\": \"十字平衡图或四象限约束图。中央是“产品决策”，四周四个约束模块向内汇聚。\",\n      \"status\": \"completed\",\n      \"message\": \"产品决策是在多种约束之间做平衡\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/v8mg9vidsy1xoc2h0kf75xxy-c672b4b444803d2332b7a443148ca262.png\",\n      \"storageKey\": \"generated/drill/v8mg9vidsy1xoc2h0kf75xxy-c672b4b444803d2332b7a443148ca262.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 5: 产品经理像桥梁\\nMain message: 产品决策是在多种约束之间做平衡\\n\\nVisible text must be exactly these lines, with no extra words:\\n用户价值\\n商业价值\\n技术可行性\\n资源限制\\n选当前最合适的方案\\n\\nLayout:\\n十字平衡图或四象限约束图。中央是“产品决策”，四周四个约束模块向内汇聚。\\n\\nVisual style:\\n工程图纸式信息图，细线结构，像系统架构决策板。\\n\\nAdditional image direction:\\nCreate a Chinese slide with a central decision hub labeled 产品决策, connected to four surrounding blocks: 用户价值, 商业价值, 技术可行性, 资源限制. The composition should resemble a clean architecture decision diagram on grid paper, with thin connector lines and a precise retro-tech manual feel.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 5,\n      \"visibleText\": [\n        \"用户价值\",\n        \"商业价值\",\n        \"技术可行性\",\n        \"资源限制\",\n        \"选当前最合适的方案\"\n      ],\n      \"visualStyle\": \"工程图纸式信息图，细线结构，像系统架构决策板。\",\n      \"speakerNotes\": \"源文指出，产品经理的经典认知是桥梁角色。未必直接写代码，也未必直接做设计，但负责把不同目标协调起来。常见约束包括用户价值、商业价值、技术可行性、资源限制。文中用一句近似公式表达本质：产品决策不是选最好，而是选当前最合适。这里不要展开太多，用视觉强调平衡关系即可。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, no extra pages, no contact sheet. Design a Neo-Retro Dev Deck / Pixel-Infographic Editorial slide with a light cream off-white engineering notebook grid background, subtle square grid lines, thick black borders, flat retro-tech shapes, and a precise system-architecture decision diagram feel.\\n\\nSlide topic: 产品经理像桥梁 / 产品决策是在多种约束之间做平衡.\\n\\nComposition:\\n- Center a bold decision hub labeled exactly: 产品决策\\n- Surround it with four modular constraint blocks arranged like a clean cross / four-quadrant architecture board, all connected inward with thin black connector lines and arrow-like chevrons.\\n- Each surrounding block should be a distinct color block from the strict palette, with one dominant color per section:\\n  1) Hot pink block: 用户价值\\n  2) Bright yellow block: 商业价值\\n  3) Cyan/light blue block: 技术可行性\\n  4) Cream/black-anchored block with accent: 资源限制\\n- The center should feel like the hub where these constraints converge.\\n- Add a final outcome line as a bottom or side callout, bold and readable: 选当前最合适的方案\\n- Keep the slide presentation-ready, polished, and visually finished, with editorial rhythm and controlled overlap.\\n\\nTypography:\\n- Heavy geometric sans serif, bold black headline treatment.\\n- Chinese text should be large, crisp, and highly legible at presentation distance.\\n- No extra captions, no decorative filler text, no fake UI, no logos, no watermarks.\\n\\nStyle specifics:\\n- Retro-futuristic, developer-centric, opinionated, slightly rebellious.\\n- Pixel-art inspired micro-icons or symbols can appear subtly in or near the blocks (e.g., tiny gear, code brackets, browser/agent motifs), but do not add any extra words.\\n- Thin technical connector lines, precise alignment, modular cards, slight collage overlap, engineering diagram clarity.\\n- Avoid gradients, realistic photos, soft shadows, corporate PPT look, and minimal emptiness.\\n\\nVisible text must be limited to these Chinese phrases only:\\n产品决策\\n用户价值\\n商业价值\\n技术可行性\\n资源限制\\n选当前最合适的方案\\n\\nEnsure all text is readable and there are no additional words, letters, or captions anywhere else on the slide.\",\n      \"storageFileId\": \"v8mg9vidsy1xoc2h0kf75xxy-c672b4b444803d2332b7a443148ca262\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"需求不是越多越好\",\n      \"layout\": \"左侧堆叠反馈便签，右侧优先级漏斗或筛选器，底部输出一个“先做注册流程优化”的高亮结果卡。\",\n      \"status\": \"completed\",\n      \"message\": \"关键能力不是收集需求，而是判断优先级\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/lg6rpcuhd2fy29wh1ay68ppv-67646c7e658f598f0232e290a6697a83.png\",\n      \"storageKey\": \"generated/drill/lg6rpcuhd2fy29wh1ay68ppv-67646c7e658f598f0232e290a6697a83.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 6: 需求不是越多越好\\nMain message: 关键能力不是收集需求，而是判断优先级\\n\\nVisible text must be exactly these lines, with no extra words:\\n10 条反馈 不等于 10 个待做功能\\n先看\\n核心用户\\n高频痛点\\n关键指标\\n实现成本 产品阶段\\n\\nLayout:\\n左侧堆叠反馈便签，右侧优先级漏斗或筛选器，底部输出一个“先做注册流程优化”的高亮结果卡。\\n\\nVisual style:\\n像素便签 + 过滤器信息图，强调从杂音到主线。\\n\\nAdditional image direction:\\nA Chinese slide showing many incoming feedback notes on the left, such as 深色模式, 导出 PDF, 接入 Notion, 团队协作, 多语言. On the right, show a filtering funnel labeled 核心用户, 高频痛点, 关键指标, 实现成本, 产品阶段, ending in one highlighted choice like 优化注册流程. Use a clean pixel-infographic editorial layout.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 6,\n      \"visibleText\": [\n        \"10 条反馈 不等于 10 个待做功能\",\n        \"先看\",\n        \"核心用户\",\n        \"高频痛点\",\n        \"关键指标\",\n        \"实现成本 产品阶段\"\n      ],\n      \"visualStyle\": \"像素便签 + 过滤器信息图，强调从杂音到主线。\",\n      \"speakerNotes\": \"这一页基于源文中关于优先级的部分。很多初学者误以为产品经理的工作是收集需求，但更关键的是判断哪些值得做、什么时候做、为什么做。判断标准包括是否影响核心用户、是否解决高频痛点、是否能提升关键指标、实现成本是否合理、是否符合产品阶段。可以顺带提到那个例子：在早期验证阶段，优化注册流程可能比深色模式更重要。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, landscape 1536x864, in a Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Light cream/off-white engineering notebook grid background with subtle square grid lines. Retro-futuristic, developer-centric, editorial infographic feel: 90s computer manual mixed with modern AI dev tools marketing, pixel art meets startup slide deck, confident playful opinionated slightly rebellious.\\n\\nSlide topic in Chinese: 需求不是越多越好. Main message: 关键能力不是收集需求，而是判断优先级.\\n\\nComposition: left side stacked incoming feedback sticky notes in pixel style, thick black borders, slightly overlapping, varied colors but controlled palette; notes should include readable Chinese items such as 深色模式, 导出 PDF, 接入 Notion, 团队协作, 多语言, plus small extra feedback note shapes. Right side a large filtering funnel / sorter infographic with stacked stages, each stage in a boxed label and thick black outline, ending in a bright highlighted output card at bottom. Bottom output card should be prominent and read: 先做注册流程优化. Emphasize that 10 feedbacks do not equal 10 features. Use visual motion from noisy notes to focused mainline.\\n\\nVisible text must be exactly these lines, with no extra words:\\n10 条反馈 不等于 10 个待做功能\\n先看\\n核心用户\\n高频痛点\\n关键指标\\n实现成本 产品阶段\\n\\nDo not add any other visible text except the specified lines and the Chinese feedback note labels already requested in the layout direction (深色模式, 导出 PDF, 接入 Notion, 团队协作, 多语言) and the output card text 先做注册流程优化. Make sure all visible text is readable at presentation distance. Large bold headline at top-left or top-center, slightly condensed geometric sans serif in black. Underline/section labels small clean type. Use hot pink for agent/priority emphasis, bright yellow for code/tools/feedback, cyan/light blue for browser/execution, black for text and borders, cream background. Stack modular blocks with rectangles and slight overlaps, horizontal section bars, arrows, chevrons, pixel sparks. Pixel-art icons: sticky notes, filter funnel, magnifying glass, gear, arrows. Controlled imperfection, assembled not sterile. No gradients, no soft shadows, no corporate template, no photorealism, no browser chrome, no watermark. Presentation-ready, cohesive, polished, strong hierarchy, editorial rhythm.\",\n      \"storageFileId\": \"lg6rpcuhd2fy29wh1ay68ppv-67646c7e658f598f0232e290a6697a83\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"它为什么对增长有用\",\n      \"layout\": \"横向流程图，一条从左到右的增长链路，阶段卡片逐步递进，最后两个结果节点突出。\",\n      \"status\": \"completed\",\n      \"message\": \"增长不只靠流量，更取决于前面的判断\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/p5xs5uy98awd04jn0ox3c1sw-d0e384db961c1e95515784199dd837b3.png\",\n      \"storageKey\": \"generated/drill/p5xs5uy98awd04jn0ox3c1sw-d0e384db961c1e95515784199dd837b3.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 7: 它为什么对增长有用\\nMain message: 增长不只靠流量，更取决于前面的判断\\n\\nVisible text must be exactly these lines, with no extra words:\\n用户问题\\n需求洞察\\n产品方案\\n首次体验\\n持续使用\\n付费与传播\\n\\nLayout:\\n横向流程图，一条从左到右的增长链路，阶段卡片逐步递进，最后两个结果节点突出。\\n\\nVisual style:\\n开发工作流海报感，步骤清晰，像构建流水线。\\n\\nAdditional image direction:\\nDesign a Chinese horizontal workflow slide with six connected stages: 用户问题 → 需求洞察 → 产品方案 → 首次体验 → 持续使用 → 付费与传播. Make it feel like a product-growth pipeline in a retro dev infographic style, using modular boxes, arrows, and strong editorial hierarchy on a subtle grid background.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 7,\n      \"visibleText\": [\n        \"用户问题\",\n        \"需求洞察\",\n        \"产品方案\",\n        \"首次体验\",\n        \"持续使用\",\n        \"付费与传播\"\n      ],\n      \"visualStyle\": \"开发工作流海报感，步骤清晰，像构建流水线。\",\n      \"speakerNotes\": \"这一页直接对应源文第三部分。它说明这本书对增长营销的帮助，不在单点技巧，而在打通产品、转化、留存。文中给出了一条非常清晰的链路：用户问题到需求洞察，到产品方案，到首次体验，到持续使用，最后到付费与传播。重点强调一句：如果前面的洞察错了，后面的转化和留存都会吃亏。\",\n      \"revisedPrompt\": \"Create a single 1536x864 landscape presentation slide in the style of Neo-Retro Dev Deck / Pixel-Infographic Editorial. Light cream off-white background with subtle engineering notebook grid lines. Strong editorial composition, retro-futuristic developer infographic, pixel-art meets startup slide deck. Thick black borders, modular boxes, slight overlaps, assembled collage feel, no soft shadows, no gradients, no photos, no corporate look.\\n\\nSlide topic: Chinese horizontal workflow showing why growth is useful. Build a left-to-right product-growth pipeline with six connected stages, each as a distinct modular card with bold black outlined rectangles and color accents. The flow should feel like a development workflow poster. Use arrows and chevrons between cards. Make the last two nodes more prominent and colorful.\\n\\nIMPORTANT: The only visible text on the slide must be exactly these six lines, and nothing else anywhere:\\n用户问题\\n需求洞察\\n产品方案\\n首次体验\\n持续使用\\n付费与传播\\n\\nDo not add any extra text, labels, titles, subtitles, captions, numbers, logos, or watermarks.\\n\\nVisual structure:\\n- Six connected stage cards laid out horizontally across the slide from left to right.\\n- Stage 1 and 2 in hot pink dominant blocks, stage 3 in yellow, stage 4 in cyan, stage 5 and 6 emphasized larger with stronger color presence and thicker borders.\\n- Each card contains one bold Chinese line only, centered or slightly offset, with clean heavy geometric sans serif typography, black text.\\n- Add pixel-art icons in each card: user/problem bubble, magnifier/insight, tool/plan, first-use browser/app window, repeat/loop, coin/share burst. Icons must be low-resolution 8-bit/16-bit style with black outline and flat colors.\\n- Use arrows, small motion lines, tiny pixel sparks, and gear-like decorative elements to connect the stages.\\n- Overall layout should be balanced and presentation-ready, not sparse. Keep text highly readable at presentation distance.\\n- The final two stages, \\\"持续使用\\\" and \\\"付费与传播\\\", should be visually highlighted as the outcome nodes, slightly larger and more vivid, implying growth depends on earlier judgment.\\n\\nStyle details:\\n- Big bold headline feel through composition, but since only the six required lines may appear, use the cards themselves as the typographic focus.\\n- Strict palette: hot pink, bright yellow, cyan/light blue, black, cream, with occasional white negative space.\\n- Thick black outlines around all blocks and icons.\\n- Slight intentional misalignment and overlap for a hand-assembled editorial feel.\\n- Clean, finished, visually rich, and coherent with the template.\\n\\nNo extra visible text beyond the six specified Chinese lines. Ensure there is no hidden or tiny text anywhere else in the image.\",\n      \"storageFileId\": \"p5xs5uy98awd04jn0ox3c1sw-d0e384db961c1e95515784199dd837b3\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"避免自嗨式开发\",\n      \"layout\": \"上半部分三条误区警示，下半部分三条行动原则，形成一一对应的修正关系。\",\n      \"status\": \"completed\",\n      \"message\": \"先验证问题，再实现方案\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/ljv7dzw2oyijavl84b3o9dxq-500bd5a6d11ac8200877b32ff94e1e1d.png\",\n      \"storageKey\": \"generated/drill/ljv7dzw2oyijavl84b3o9dxq-500bd5a6d11ac8200877b32ff94e1e1d.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: 为什么“人人都是产品经理”\\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 8: 避免自嗨式开发\\nMain message: 先验证问题，再实现方案\\n\\nVisible text must be exactly these lines, with no extra words:\\n不要因为能做就做\\n不要因为自己喜欢就做\\n不要因为有人提了就立刻做\\n先验证问题\\n先看用户行为\\n先抓主线价值\\n\\nLayout:\\n上半部分三条误区警示，下半部分三条行动原则，形成一一对应的修正关系。\\n\\nVisual style:\\n像素警示牌与原则卡片结合，结尾页有强结论感。\\n\\nAdditional image direction:\\nCreate a Chinese closing slide with a clear before-and-after structure. Top half shows three anti-pattern warning cards: 因为能做就做, 因为自己喜欢就做, 因为有人提了就立刻做. Bottom half shows three corrective principles: 先验证问题, 先看用户行为, 先抓主线价值. Use bold black outlines, small accent color blocks, and a memorable retro-dev editorial composition.\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 8,\n      \"visibleText\": [\n        \"不要因为能做就做\",\n        \"不要因为自己喜欢就做\",\n        \"不要因为有人提了就立刻做\",\n        \"先验证问题\",\n        \"先看用户行为\",\n        \"先抓主线价值\"\n      ],\n      \"visualStyle\": \"像素警示牌与原则卡片结合，结尾页有强结论感。\",\n      \"speakerNotes\": \"最后用一个收束页总结对独立开发者最现实的价值。源文说，这本书能帮助独立开发者避免自嗨式开发。常见误区包括：因为技术上能做所以做，因为自己喜欢所以觉得用户也喜欢，因为有人提了需求就立刻开发。对应的产品思维是：先验证问题，再实现方案；先看用户行为，再听用户表述；先抓主线价值，再做边缘功能。结尾可以再落回一句总括：这不是岗位指南，而是帮助你提升判断框架。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in a Neo-Retro Dev Deck / Pixel-Infographic Editorial style: light cream off-white engineering notebook grid background, thick black outlines, modular stacked blocks, retro-futuristic developer editorial composition, pixel-art warning icons, bold geometric sans typography, hot pink / bright yellow / cyan accents, slightly rebellious but clean and presentation-ready. The slide is a clear before-and-after structure with strong conclusion energy.\\n\\nIMPORTANT TEXT RULES: The ONLY visible text on the entire slide must be exactly these six Chinese lines, and nothing else anywhere on the image:\\n不要因为能做就做\\n不要因为自己喜欢就做\\n不要因为有人提了就立刻做\\n先验证问题\\n先看用户行为\\n先抓主线价值\\nDo not add any title, subtitle, labels, numbers, bullets, captions, watermarks, logos, UI chrome, or extra text of any kind.\\n\\nLAYOUT: Top half = three anti-pattern warning cards, each with a pixel warning sign / alert icon and one of the first three lines, arranged left to right. Bottom half = three corrective principle cards, each with a small pixel arrow / gear / check-style icon and one of the last three lines, also arranged left to right. Make the top half visually tense and cautionary with hot pink/yellow warning blocks; make the bottom half calmer and more decisive with cyan/yellow action blocks. Use thick black borders, slight overlaps, editorial rhythm, and one-to-one correspondence from each top card to the card below it. Add a strong central divider or arrowed transition between the halves, but without any extra text.\\n\\nSTYLE: pixel-art warning placards, retro manual aesthetics, 90s computer manual mixed with modern AI dev tools marketing, flat colors, no gradients, no shadows, no photorealism. Keep the six lines highly legible at presentation distance, large bold black text, aligned within their cards. The result should feel like a finished closing slide with a memorable retro-dev editorial composition.\",\n      \"storageFileId\": \"ljv7dzw2oyijavl84b3o9dxq-500bd5a6d11ac8200877b32ff94e1e1d\"\n    }\n  ],\n  \"styleId\": \"neo_retro_dev\",\n  \"summary\": \"这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\",\n  \"audience\": \"独立开发者、增长营销从业者、刚接触产品思维的创业者与内容读者\",\n  \"imageSize\": \"1536x864\",\n  \"imageModel\": \"gpt-image-2\",\n  \"plannerModel\": \"gpt-5.4\"\n}","structured":{"style":"Neo-Retro Dev Deck / Pixel-Infographic Editorial","title":"为什么“人人都是产品经理”","format":"presenter_slides","slides":[{"size":"1536x864","model":"gpt-image-2","title":"不是转岗建议","layout":"封面式单页。左上大标题，中央一个像素风系统框图，把“用户需求、商业目标、实现路径”连成三节点结构，右下角放一句短结论。","status":"completed","message":"“人人都是产品经理”讲的是一种思维，不是一个职位","imageUrl":"https://cdn.drillso.com/generated/drill/eh7kog0ffadmd17ymjqohay7-54539c9d19802eef22884ac2d4154dda.png","storageKey":"generated/drill/eh7kog0ffadmd17ymjqohay7-54539c9d19802eef22884ac2d4154dda.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: 为什么“人人都是产品经理”\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 1: 不是转岗建议\nMain message: “人人都是产品经理”讲的是一种思维，不是一个职位\n\nVisible text must be exactly these lines, with no extra words:\n不是人人去做 PM\n而是人人都在影响产品\n产品 = 用户需求 × 商业目标 × 实现路径\n\nLayout:\n封面式单页。左上大标题，中央一个像素风系统框图，把“用户需求、商业目标、实现路径”连成三节点结构，右下角放一句短结论。\n\nVisual style:\n复古开发者社论风，轻网格背景，黑色线框，少量高对比强调色，像产品手册首页。\n\nAdditional image direction:\nA Chinese presentation cover slide with a retro developer editorial feel. Show a clean off-white grid-paper background, sharp black typography, and a central pixel-infographic system diagram with three connected modules labeled 用户需求, 商业目标, 实现路径. The composition should feel like a smart developer manual cover, with strong hierarchy, minimal text, and one bold statement that this is not a job-title book but a way of thinking.\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":1,"visibleText":["不是人人去做 PM","而是人人都在影响产品","产品 = 用户需求 × 商业目标 × 实现路径"],"visualStyle":"复古开发者社论风，轻网格背景，黑色线框，少量高对比强调色，像产品手册首页。","speakerNotes":"开场先纠正书名带来的误解。源文明确指出，这本书的核心不是教你如何成为某个岗位上的产品经理，而是在传递更底层的观念：产品不是一个职位的工作，而是围绕用户需求、商业目标和实现路径的系统协作。这一页只讲一个点：它讲的是思维方式，而不是岗位名称。","revisedPrompt":"Create exactly one complete presentation slide image, 1536x864 landscape, in a Neo-Retro Dev Deck / Pixel-Infographic Editorial style.\n\nStrict content rule: the ONLY visible text on the slide must be exactly these three lines, and nothing else anywhere:\n不是人人去做 PM\n而是人人都在影响产品\n产品 = 用户需求 × 商业目标 × 实现路径\n\nDesign direction:\n- Chinese presentation cover slide, retro developer editorial feel.\n- Light cream/off-white engineering notebook background with subtle square grid lines.\n- Sharp black typography, bold geometric sans-serif, heavy condensed headline style.\n- Strong hierarchy, minimal text, presentation-ready.\n- Use thick black borders, modular rectangles, slight overlaps, pixel-infographic assembly.\n- Style feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Mood: confident, playful, opinionated, slightly rebellious.\n\nLayout:\n- Top-left large headline block for the first two lines.\n- Center a pixel-art system diagram with three connected modules arranged in a smart triangular or left-to-right flow, each module as a bold colored block with thick black border and simple pixel iconography. The modules should visually represent 用户需求, 商业目标, 实现路径, but DO NOT add any extra labels or captions beyond the exact required text lines.\n- Use hot pink, bright yellow, cyan/light blue as the dominant accent colors, with black outlines and cream background.\n- Bottom-right place the third line as a short conclusion block, integrated into the composition, using the exact text only.\n- Add small motion arrows, pixel sparks, tiny gears, and editorial annotation marks as graphics only, not text.\n- Make it feel like a polished manifesto-style developer manual cover, not sparse or placeholder.\n\nTypography and rendering:\n- Ensure the three required lines are highly readable and accurately rendered in Chinese.\n- No extra words, no subtitles, no logos, no UI chrome, no watermark, no signatures, no markdown symbols.\n- No other visible text anywhere on the slide.\n- Keep the composition cohesive, finished, and visually balanced.\n\nVisual vibe:\n- Clean off-white grid-paper background.\n- Black borders and typography.\n- Hot pink/yellow/cyan modular blocks.\n- Retro pixel-infographic editorial composition, strong and smart, like a product thinking handbook cover.","storageFileId":"eh7kog0ffadmd17ymjqohay7-54539c9d19802eef22884ac2d4154dda"},{"size":"1536x864","model":"gpt-image-2","title":"为什么是“人人”","layout":"人物职能地图。中间一个像素风独立开发者角色，周围环绕六个职责卡片，用连线形成星状结构。","status":"completed","message":"因为每个岗位都在影响价值交付","imageUrl":"https://cdn.drillso.com/generated/drill/t21udsfpuxu88de9tcbj5ed4-531d26ae4c81f5b7be339239fc1ba1b8.png","storageKey":"generated/drill/t21udsfpuxu88de9tcbj5ed4-531d26ae4c81f5b7be339239fc1ba1b8.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: 为什么“人人都是产品经理”\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 2: 为什么是“人人”\nMain message: 因为每个岗位都在影响价值交付\n\nVisible text must be exactly these lines, with no extra words:\n独立开发者常常一人多职\n产品经理\n用户研究\n文案策划\n运营 数据分析 客服销售\n\nLayout:\n人物职能地图。中间一个像素风独立开发者角色，周围环绕六个职责卡片，用连线形成星状结构。\n\nVisual style:\n像素人物 + 信息卡片，轻量注释感，强调多角色切换。\n\nAdditional image direction:\nCreate a Chinese slide showing a solo indie developer in the center as a pixel-art or simplified illustrated figure, surrounded by six connected role cards: 产品经理, 用户研究, 文案策划, 运营, 数据分析, 客服与销售. Use a clean grid background and black UI-like connector lines. The slide should communicate that one person often covers many roles in early-stage products.\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":2,"visibleText":["独立开发者常常一人多职","产品经理","用户研究","文案策划","运营 数据分析 客服销售"],"visualStyle":"像素人物 + 信息卡片，轻量注释感，强调多角色切换。","speakerNotes":"这一页承接上一页。源文给出的具体背景是：这本书会出现在增长营销书单中，是因为独立开发者经常同时扮演产品经理、用户研究员、文案策划、运营、数据分析师、客服与销售等多个角色。所以“人人”不是抽象口号，而是现实分工。每个动作都会影响产品最终如何被理解、被使用、被付费。","revisedPrompt":"Create exactly one complete presentation slide image, landscape 1536x864, Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Light cream off-white background with subtle square engineering grid. Thick black borders, modular collage layout, retro-futuristic editorial infographic, pixel-art accents, clean but rebellious. Chinese slide, high presentation quality, no extra text anywhere except the required visible text lines below. Make all text large, readable, bold black geometric sans serif. Use hot pink, bright yellow, cyan blocks with black outlines. Strong centered composition.\n\nLayout: A central pixel-art solo indie developer character, simplified illustrated figure, standing on a yellow-pink platform in the middle. Around the character, connect six role cards with black UI-like connector lines in a star map. The cards should be visually distinct and finished, with one dominant color block each, slight overlap, and small pixel icons. The center figure should look like one person wearing dev hoodie/laptop vibe, suggesting one person covers many jobs. Add small pixel arrows and sparks to emphasize multi-role switching. Use editorial annotation feel, not corporate.\n\nIMPORTANT TEXT RULE: The only visible text on the slide must be exactly these five lines, placed as the role labels / headline text, with no additional words, captions, numbers, logos, or watermarks:\n独立开发者常常一人多职\n产品经理\n用户研究\n文案策划\n运营 数据分析 客服销售\n\nDo not add any other text. Ensure the last line appears exactly as written, with spaces between 运营 数据分析 客服销售. Use the same Chinese text as the only labels. Make the slide cohesive and visually finished, not sparse. Avoid gradients, photos, realistic rendering, soft shadows, browser chrome, or template placeholders.","storageFileId":"t21udsfpuxu88de9tcbj5ed4-531d26ae4c81f5b7be339239fc1ba1b8"},{"size":"1536x864","model":"gpt-image-2","title":"产品思维的起点","layout":"左右对比。左侧是“功能导向”清单，右侧是“任务导向”问题卡，中央用箭头表示思维切换。","status":"completed","message":"先问用户想完成什么，而不是先想自己能做什么","imageUrl":"https://cdn.drillso.com/generated/drill/dsf58cc2l8f75bszthqcamwi-0bd5f444762c8f1f423f61ba5f7a8445.png","storageKey":"generated/drill/dsf58cc2l8f75bszthqcamwi-0bd5f444762c8f1f423f61ba5f7a8445.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: 为什么“人人都是产品经理”\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 3: 产品思维的起点\nMain message: 先问用户想完成什么，而不是先想自己能做什么\n\nVisible text must be exactly these lines, with no extra words:\n不是\n我要加更多模型\n我要做更炫功能\n而是\n用户真正想完成什么任务\n为什么会放弃现有方案\n\nLayout:\n左右对比。左侧是“功能导向”清单，右侧是“任务导向”问题卡，中央用箭头表示思维切换。\n\nVisual style:\n终端式对照板，左红右绿式逻辑反差，但整体保持纸面像素信息图风格。\n\nAdditional image direction:\nA Chinese comparison slide with two columns. Left column labeled with a function-first mindset, listing ideas like 更多模型, 更快响应, 更炫功能. Right column labeled with a product-thinking mindset, showing questions like 用户真正想完成什么任务 and 为什么会放弃现有方案. Use a retro UI comparison board aesthetic, with black divider lines, subtle grid, and a strong center arrow showing the shift.\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":3,"visibleText":["不是","我要加更多模型","我要做更炫功能","而是","用户真正想完成什么任务","为什么会放弃现有方案"],"visualStyle":"终端式对照板，左红右绿式逻辑反差，但整体保持纸面像素信息图风格。","speakerNotes":"这里使用源文里的 AI 写作工具例子。只会写代码时，可能首先想到更多模型、更快响应、更炫功能。但产品思维会逼你先问：用户真正想完成什么任务，他们为什么放弃现有方案，第一次使用卡在哪里，他们愿意为什么付费。核心转折是从“我能做什么”切换到“用户需要什么、业务需要什么、我该如何平衡”。","revisedPrompt":"Create exactly one complete presentation slide image, 1536x864 landscape, Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Light cream off-white engineering notebook grid background, subtle square grid lines, thick black borders, retro computer manual meets modern AI dev deck, pixel-art UI, slightly rebellious editorial layout.\n\nSlide content in Chinese only, with NO extra words anywhere else. Visible text must be exactly these lines and nothing else:\n不是\n我要加更多模型\n我要做更炫功能\n而是\n用户真正想完成什么任务\n为什么会放弃现有方案\n\nComposition: a strong left-right comparison board. Left side is function-first mindset with a terminal-like card stack in warm red / hot pink / red-orange tones, thick black border, simple pixel icons of gears, code brackets, sparkles, and small blocky UI chips, arranged like a checklist of feature thoughts. Right side is product-thinking mindset with a task-oriented question card in green / mint / cyan tones, thick black border, pixel icons of user, target, chat bubble, browser window, and a bigger more confident card. Center has a large bold arrow showing the shift from left to right, black outline, retro UI style, slightly overlapping the two columns.\n\nTypography: huge bold geometric sans serif Chinese text, black, slightly condensed, highly readable. Make the six provided lines the only readable text, each line large and clear in stacked blocks. No other labels, no title, no footer, no watermark, no browser chrome.\n\nVisual style: terminal-style contrast board, left warm/red and right green/teal logic contrast, paper-like pixel information graphic, controlled imperfect collage, black divider lines, subtle motion lines and pixel sparks, presentation-ready, cohesive, finished, not sparse, not minimalist, no gradients, no realistic photos, no soft shadows, no extra captions, no fake logos.","storageFileId":"dsf58cc2l8f75bszthqcamwi-0bd5f444762c8f1f423f61ba5f7a8445"},{"size":"1536x864","model":"gpt-image-2","title":"需求有层次","layout":"三层向下钻取图。顶部是用户原话气泡，中间是问题理解层，底部是潜在目标与更优方案卡片。","status":"completed","message":"功能请求不等于真实问题","imageUrl":"https://cdn.drillso.com/generated/drill/b24zwjh5ibcv7q6lgavdg9u8-ddb553aaf2ffd2011e6dcf8c16b5991f.png","storageKey":"generated/drill/b24zwjh5ibcv7q6lgavdg9u8-ddb553aaf2ffd2011e6dcf8c16b5991f.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: 为什么“人人都是产品经理”\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 4: 需求有层次\nMain message: 功能请求不等于真实问题\n\nVisible text must be exactly these lines, with no extra words:\n表层需求\n我想要番茄钟\n真实需求\n我想减少拖延\n潜在需求\n我想更容易进入专注状态\n\nLayout:\n三层向下钻取图。顶部是用户原话气泡，中间是问题理解层，底部是潜在目标与更优方案卡片。\n\nVisual style:\n像素信息结构图，带少量聊天气泡和分层箭头，强调从表象到本质。\n\nAdditional image direction:\nDesign a Chinese slide as a three-layer needs analysis diagram. Top layer: a speech bubble saying 我想要一个番茄钟功能. Middle layer: 真实需求 with 减少拖延. Bottom layer: 潜在需求 with 更容易进入专注状态, plus small product-solution cards such as 自动进入专注模式, 任务拆分提示, 干扰屏蔽, 专注记录反馈. Keep it diagrammatic, clean, and developer-editorial.\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":4,"visibleText":["表层需求","我想要番茄钟","真实需求","我想减少拖延","潜在需求","我想更容易进入专注状态"],"visualStyle":"像素信息结构图，带少量聊天气泡和分层箭头，强调从表象到本质。","speakerNotes":"这一页讲书中最关键的概念之一：用户需求是起点，而且需求有层次。源文把需求分成表层需求、真实需求、潜在需求，并用番茄钟举例。用户提出“我想要一个番茄钟功能”只是表层；继续追问后发现他不是想要计时器，而是想减少拖延、进入专注状态。所以更好的方案可能不是单纯做个计时器，而是自动专注模式、任务拆分提示、干扰屏蔽、专注反馈。","revisedPrompt":"Create exactly one complete presentation slide image, landscape 1536x864, in the Neo-Retro Dev Deck / Pixel-Infographic Editorial style.\n\nLanguage: Chinese. Keep all visible text EXACTLY these six lines and no extra words anywhere on the slide:\n表层需求\n我想要番茄钟\n真实需求\n我想减少拖延\n潜在需求\n我想更容易进入专注状态\n\nDesign the slide as a three-layer needs analysis diagram with a developer-editorial, pixel-infographic feel.\n\nComposition:\n- Light cream/off-white engineering notebook background with subtle square grid lines.\n- Strong stacked modular layout, thick black borders, slight overlaps, collage-like assembly.\n- Top layer: a hot-pink speech bubble / user quote card for 表层需求 and 我想要番茄钟.\n- Middle layer: a yellow problem-understanding block for 真实需求 and 我想减少拖延.\n- Bottom layer: a cyan deeper-need block for 潜在需求 and 我想更容易进入专注状态.\n- Use downward drill arrows or pixel chevrons between layers to show progression from surface to core.\n- Add a few small pixel-art icons only, no text: clock, arrow-down, brain, focus ring, shield from distractions, notebook, gears.\n- At the bottom, add small unlabeled solution-card visuals as tiny icon boxes only, without any additional text.\n\nTypography:\n- Bold geometric sans serif, black, slightly condensed, high contrast, presentation-ready.\n- The six required lines should be large and readable at presentation distance.\n- No other labels, captions, bullet points, logos, watermarks, or UI chrome.\n\nColor palette:\n- Hot pink for surface/agent/intelligence concept.\n- Bright yellow for problem/friction/tools concept.\n- Cyan/light blue for deeper needs and execution.\n- Black borders and text.\n- Cream background.\n\nVisual mood:\n- Confident, playful, opinionated, slightly rebellious.\n- Like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Finished, polished, coherent, not sparse.\n\nImportant constraints:\n- One slide only, not a contact sheet.\n- No extra visible text beyond the six required lines.\n- Keep the slide clean, diagrammatic, and highly legible.\n- No realistic photos, no gradients, no soft shadows, no corporate template look.","storageFileId":"b24zwjh5ibcv7q6lgavdg9u8-ddb553aaf2ffd2011e6dcf8c16b5991f"},{"size":"1536x864","model":"gpt-image-2","title":"产品经理像桥梁","layout":"十字平衡图或四象限约束图。中央是“产品决策”，四周四个约束模块向内汇聚。","status":"completed","message":"产品决策是在多种约束之间做平衡","imageUrl":"https://cdn.drillso.com/generated/drill/v8mg9vidsy1xoc2h0kf75xxy-c672b4b444803d2332b7a443148ca262.png","storageKey":"generated/drill/v8mg9vidsy1xoc2h0kf75xxy-c672b4b444803d2332b7a443148ca262.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: 为什么“人人都是产品经理”\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 5: 产品经理像桥梁\nMain message: 产品决策是在多种约束之间做平衡\n\nVisible text must be exactly these lines, with no extra words:\n用户价值\n商业价值\n技术可行性\n资源限制\n选当前最合适的方案\n\nLayout:\n十字平衡图或四象限约束图。中央是“产品决策”，四周四个约束模块向内汇聚。\n\nVisual style:\n工程图纸式信息图，细线结构，像系统架构决策板。\n\nAdditional image direction:\nCreate a Chinese slide with a central decision hub labeled 产品决策, connected to four surrounding blocks: 用户价值, 商业价值, 技术可行性, 资源限制. The composition should resemble a clean architecture decision diagram on grid paper, with thin connector lines and a precise retro-tech manual feel.\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":5,"visibleText":["用户价值","商业价值","技术可行性","资源限制","选当前最合适的方案"],"visualStyle":"工程图纸式信息图，细线结构，像系统架构决策板。","speakerNotes":"源文指出，产品经理的经典认知是桥梁角色。未必直接写代码，也未必直接做设计，但负责把不同目标协调起来。常见约束包括用户价值、商业价值、技术可行性、资源限制。文中用一句近似公式表达本质：产品决策不是选最好，而是选当前最合适。这里不要展开太多，用视觉强调平衡关系即可。","revisedPrompt":"Create exactly one complete presentation slide image, 1536x864 landscape, no extra pages, no contact sheet. Design a Neo-Retro Dev Deck / Pixel-Infographic Editorial slide with a light cream off-white engineering notebook grid background, subtle square grid lines, thick black borders, flat retro-tech shapes, and a precise system-architecture decision diagram feel.\n\nSlide topic: 产品经理像桥梁 / 产品决策是在多种约束之间做平衡.\n\nComposition:\n- Center a bold decision hub labeled exactly: 产品决策\n- Surround it with four modular constraint blocks arranged like a clean cross / four-quadrant architecture board, all connected inward with thin black connector lines and arrow-like chevrons.\n- Each surrounding block should be a distinct color block from the strict palette, with one dominant color per section:\n  1) Hot pink block: 用户价值\n  2) Bright yellow block: 商业价值\n  3) Cyan/light blue block: 技术可行性\n  4) Cream/black-anchored block with accent: 资源限制\n- The center should feel like the hub where these constraints converge.\n- Add a final outcome line as a bottom or side callout, bold and readable: 选当前最合适的方案\n- Keep the slide presentation-ready, polished, and visually finished, with editorial rhythm and controlled overlap.\n\nTypography:\n- Heavy geometric sans serif, bold black headline treatment.\n- Chinese text should be large, crisp, and highly legible at presentation distance.\n- No extra captions, no decorative filler text, no fake UI, no logos, no watermarks.\n\nStyle specifics:\n- Retro-futuristic, developer-centric, opinionated, slightly rebellious.\n- Pixel-art inspired micro-icons or symbols can appear subtly in or near the blocks (e.g., tiny gear, code brackets, browser/agent motifs), but do not add any extra words.\n- Thin technical connector lines, precise alignment, modular cards, slight collage overlap, engineering diagram clarity.\n- Avoid gradients, realistic photos, soft shadows, corporate PPT look, and minimal emptiness.\n\nVisible text must be limited to these Chinese phrases only:\n产品决策\n用户价值\n商业价值\n技术可行性\n资源限制\n选当前最合适的方案\n\nEnsure all text is readable and there are no additional words, letters, or captions anywhere else on the slide.","storageFileId":"v8mg9vidsy1xoc2h0kf75xxy-c672b4b444803d2332b7a443148ca262"},{"size":"1536x864","model":"gpt-image-2","title":"需求不是越多越好","layout":"左侧堆叠反馈便签，右侧优先级漏斗或筛选器，底部输出一个“先做注册流程优化”的高亮结果卡。","status":"completed","message":"关键能力不是收集需求，而是判断优先级","imageUrl":"https://cdn.drillso.com/generated/drill/lg6rpcuhd2fy29wh1ay68ppv-67646c7e658f598f0232e290a6697a83.png","storageKey":"generated/drill/lg6rpcuhd2fy29wh1ay68ppv-67646c7e658f598f0232e290a6697a83.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: 为什么“人人都是产品经理”\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 6: 需求不是越多越好\nMain message: 关键能力不是收集需求，而是判断优先级\n\nVisible text must be exactly these lines, with no extra words:\n10 条反馈 不等于 10 个待做功能\n先看\n核心用户\n高频痛点\n关键指标\n实现成本 产品阶段\n\nLayout:\n左侧堆叠反馈便签，右侧优先级漏斗或筛选器，底部输出一个“先做注册流程优化”的高亮结果卡。\n\nVisual style:\n像素便签 + 过滤器信息图，强调从杂音到主线。\n\nAdditional image direction:\nA Chinese slide showing many incoming feedback notes on the left, such as 深色模式, 导出 PDF, 接入 Notion, 团队协作, 多语言. On the right, show a filtering funnel labeled 核心用户, 高频痛点, 关键指标, 实现成本, 产品阶段, ending in one highlighted choice like 优化注册流程. Use a clean pixel-infographic editorial layout.\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":6,"visibleText":["10 条反馈 不等于 10 个待做功能","先看","核心用户","高频痛点","关键指标","实现成本 产品阶段"],"visualStyle":"像素便签 + 过滤器信息图，强调从杂音到主线。","speakerNotes":"这一页基于源文中关于优先级的部分。很多初学者误以为产品经理的工作是收集需求，但更关键的是判断哪些值得做、什么时候做、为什么做。判断标准包括是否影响核心用户、是否解决高频痛点、是否能提升关键指标、实现成本是否合理、是否符合产品阶段。可以顺带提到那个例子：在早期验证阶段，优化注册流程可能比深色模式更重要。","revisedPrompt":"Create exactly one complete presentation slide image, landscape 1536x864, in a Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Light cream/off-white engineering notebook grid background with subtle square grid lines. Retro-futuristic, developer-centric, editorial infographic feel: 90s computer manual mixed with modern AI dev tools marketing, pixel art meets startup slide deck, confident playful opinionated slightly rebellious.\n\nSlide topic in Chinese: 需求不是越多越好. Main message: 关键能力不是收集需求，而是判断优先级.\n\nComposition: left side stacked incoming feedback sticky notes in pixel style, thick black borders, slightly overlapping, varied colors but controlled palette; notes should include readable Chinese items such as 深色模式, 导出 PDF, 接入 Notion, 团队协作, 多语言, plus small extra feedback note shapes. Right side a large filtering funnel / sorter infographic with stacked stages, each stage in a boxed label and thick black outline, ending in a bright highlighted output card at bottom. Bottom output card should be prominent and read: 先做注册流程优化. Emphasize that 10 feedbacks do not equal 10 features. Use visual motion from noisy notes to focused mainline.\n\nVisible text must be exactly these lines, with no extra words:\n10 条反馈 不等于 10 个待做功能\n先看\n核心用户\n高频痛点\n关键指标\n实现成本 产品阶段\n\nDo not add any other visible text except the specified lines and the Chinese feedback note labels already requested in the layout direction (深色模式, 导出 PDF, 接入 Notion, 团队协作, 多语言) and the output card text 先做注册流程优化. Make sure all visible text is readable at presentation distance. Large bold headline at top-left or top-center, slightly condensed geometric sans serif in black. Underline/section labels small clean type. Use hot pink for agent/priority emphasis, bright yellow for code/tools/feedback, cyan/light blue for browser/execution, black for text and borders, cream background. Stack modular blocks with rectangles and slight overlaps, horizontal section bars, arrows, chevrons, pixel sparks. Pixel-art icons: sticky notes, filter funnel, magnifying glass, gear, arrows. Controlled imperfection, assembled not sterile. No gradients, no soft shadows, no corporate template, no photorealism, no browser chrome, no watermark. Presentation-ready, cohesive, polished, strong hierarchy, editorial rhythm.","storageFileId":"lg6rpcuhd2fy29wh1ay68ppv-67646c7e658f598f0232e290a6697a83"},{"size":"1536x864","model":"gpt-image-2","title":"它为什么对增长有用","layout":"横向流程图，一条从左到右的增长链路，阶段卡片逐步递进，最后两个结果节点突出。","status":"completed","message":"增长不只靠流量，更取决于前面的判断","imageUrl":"https://cdn.drillso.com/generated/drill/p5xs5uy98awd04jn0ox3c1sw-d0e384db961c1e95515784199dd837b3.png","storageKey":"generated/drill/p5xs5uy98awd04jn0ox3c1sw-d0e384db961c1e95515784199dd837b3.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: 为什么“人人都是产品经理”\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 7: 它为什么对增长有用\nMain message: 增长不只靠流量，更取决于前面的判断\n\nVisible text must be exactly these lines, with no extra words:\n用户问题\n需求洞察\n产品方案\n首次体验\n持续使用\n付费与传播\n\nLayout:\n横向流程图，一条从左到右的增长链路，阶段卡片逐步递进，最后两个结果节点突出。\n\nVisual style:\n开发工作流海报感，步骤清晰，像构建流水线。\n\nAdditional image direction:\nDesign a Chinese horizontal workflow slide with six connected stages: 用户问题 → 需求洞察 → 产品方案 → 首次体验 → 持续使用 → 付费与传播. Make it feel like a product-growth pipeline in a retro dev infographic style, using modular boxes, arrows, and strong editorial hierarchy on a subtle grid background.\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":7,"visibleText":["用户问题","需求洞察","产品方案","首次体验","持续使用","付费与传播"],"visualStyle":"开发工作流海报感，步骤清晰，像构建流水线。","speakerNotes":"这一页直接对应源文第三部分。它说明这本书对增长营销的帮助，不在单点技巧，而在打通产品、转化、留存。文中给出了一条非常清晰的链路：用户问题到需求洞察，到产品方案，到首次体验，到持续使用，最后到付费与传播。重点强调一句：如果前面的洞察错了，后面的转化和留存都会吃亏。","revisedPrompt":"Create a single 1536x864 landscape presentation slide in the style of Neo-Retro Dev Deck / Pixel-Infographic Editorial. Light cream off-white background with subtle engineering notebook grid lines. Strong editorial composition, retro-futuristic developer infographic, pixel-art meets startup slide deck. Thick black borders, modular boxes, slight overlaps, assembled collage feel, no soft shadows, no gradients, no photos, no corporate look.\n\nSlide topic: Chinese horizontal workflow showing why growth is useful. Build a left-to-right product-growth pipeline with six connected stages, each as a distinct modular card with bold black outlined rectangles and color accents. The flow should feel like a development workflow poster. Use arrows and chevrons between cards. Make the last two nodes more prominent and colorful.\n\nIMPORTANT: The only visible text on the slide must be exactly these six lines, and nothing else anywhere:\n用户问题\n需求洞察\n产品方案\n首次体验\n持续使用\n付费与传播\n\nDo not add any extra text, labels, titles, subtitles, captions, numbers, logos, or watermarks.\n\nVisual structure:\n- Six connected stage cards laid out horizontally across the slide from left to right.\n- Stage 1 and 2 in hot pink dominant blocks, stage 3 in yellow, stage 4 in cyan, stage 5 and 6 emphasized larger with stronger color presence and thicker borders.\n- Each card contains one bold Chinese line only, centered or slightly offset, with clean heavy geometric sans serif typography, black text.\n- Add pixel-art icons in each card: user/problem bubble, magnifier/insight, tool/plan, first-use browser/app window, repeat/loop, coin/share burst. Icons must be low-resolution 8-bit/16-bit style with black outline and flat colors.\n- Use arrows, small motion lines, tiny pixel sparks, and gear-like decorative elements to connect the stages.\n- Overall layout should be balanced and presentation-ready, not sparse. Keep text highly readable at presentation distance.\n- The final two stages, \"持续使用\" and \"付费与传播\", should be visually highlighted as the outcome nodes, slightly larger and more vivid, implying growth depends on earlier judgment.\n\nStyle details:\n- Big bold headline feel through composition, but since only the six required lines may appear, use the cards themselves as the typographic focus.\n- Strict palette: hot pink, bright yellow, cyan/light blue, black, cream, with occasional white negative space.\n- Thick black outlines around all blocks and icons.\n- Slight intentional misalignment and overlap for a hand-assembled editorial feel.\n- Clean, finished, visually rich, and coherent with the template.\n\nNo extra visible text beyond the six specified Chinese lines. Ensure there is no hidden or tiny text anywhere else in the image.","storageFileId":"p5xs5uy98awd04jn0ox3c1sw-d0e384db961c1e95515784199dd837b3"},{"size":"1536x864","model":"gpt-image-2","title":"避免自嗨式开发","layout":"上半部分三条误区警示，下半部分三条行动原则，形成一一对应的修正关系。","status":"completed","message":"先验证问题，再实现方案","imageUrl":"https://cdn.drillso.com/generated/drill/ljv7dzw2oyijavl84b3o9dxq-500bd5a6d11ac8200877b32ff94e1e1d.png","storageKey":"generated/drill/ljv7dzw2oyijavl84b3o9dxq-500bd5a6d11ac8200877b32ff94e1e1d.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: 为什么“人人都是产品经理”\nDeck summary: 这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 8: 避免自嗨式开发\nMain message: 先验证问题，再实现方案\n\nVisible text must be exactly these lines, with no extra words:\n不要因为能做就做\n不要因为自己喜欢就做\n不要因为有人提了就立刻做\n先验证问题\n先看用户行为\n先抓主线价值\n\nLayout:\n上半部分三条误区警示，下半部分三条行动原则，形成一一对应的修正关系。\n\nVisual style:\n像素警示牌与原则卡片结合，结尾页有强结论感。\n\nAdditional image direction:\nCreate a Chinese closing slide with a clear before-and-after structure. Top half shows three anti-pattern warning cards: 因为能做就做, 因为自己喜欢就做, 因为有人提了就立刻做. Bottom half shows three corrective principles: 先验证问题, 先看用户行为, 先抓主线价值. Use bold black outlines, small accent color blocks, and a memorable retro-dev editorial composition.\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":8,"visibleText":["不要因为能做就做","不要因为自己喜欢就做","不要因为有人提了就立刻做","先验证问题","先看用户行为","先抓主线价值"],"visualStyle":"像素警示牌与原则卡片结合，结尾页有强结论感。","speakerNotes":"最后用一个收束页总结对独立开发者最现实的价值。源文说，这本书能帮助独立开发者避免自嗨式开发。常见误区包括：因为技术上能做所以做，因为自己喜欢所以觉得用户也喜欢，因为有人提了需求就立刻开发。对应的产品思维是：先验证问题，再实现方案；先看用户行为，再听用户表述；先抓主线价值，再做边缘功能。结尾可以再落回一句总括：这不是岗位指南，而是帮助你提升判断框架。","revisedPrompt":"Create exactly one complete presentation slide image, 1536x864 landscape, in a Neo-Retro Dev Deck / Pixel-Infographic Editorial style: light cream off-white engineering notebook grid background, thick black outlines, modular stacked blocks, retro-futuristic developer editorial composition, pixel-art warning icons, bold geometric sans typography, hot pink / bright yellow / cyan accents, slightly rebellious but clean and presentation-ready. The slide is a clear before-and-after structure with strong conclusion energy.\n\nIMPORTANT TEXT RULES: The ONLY visible text on the entire slide must be exactly these six Chinese lines, and nothing else anywhere on the image:\n不要因为能做就做\n不要因为自己喜欢就做\n不要因为有人提了就立刻做\n先验证问题\n先看用户行为\n先抓主线价值\nDo not add any title, subtitle, labels, numbers, bullets, captions, watermarks, logos, UI chrome, or extra text of any kind.\n\nLAYOUT: Top half = three anti-pattern warning cards, each with a pixel warning sign / alert icon and one of the first three lines, arranged left to right. Bottom half = three corrective principle cards, each with a small pixel arrow / gear / check-style icon and one of the last three lines, also arranged left to right. Make the top half visually tense and cautionary with hot pink/yellow warning blocks; make the bottom half calmer and more decisive with cyan/yellow action blocks. Use thick black borders, slight overlaps, editorial rhythm, and one-to-one correspondence from each top card to the card below it. Add a strong central divider or arrowed transition between the halves, but without any extra text.\n\nSTYLE: pixel-art warning placards, retro manual aesthetics, 90s computer manual mixed with modern AI dev tools marketing, flat colors, no gradients, no shadows, no photorealism. Keep the six lines highly legible at presentation distance, large bold black text, aligned within their cards. The result should feel like a finished closing slide with a memorable retro-dev editorial composition.","storageFileId":"ljv7dzw2oyijavl84b3o9dxq-500bd5a6d11ac8200877b32ff94e1e1d"}],"styleId":"neo_retro_dev","summary":"这组短 deck 解释《人人都是产品经理》的核心意思：它不是岗位转岗指南，而是一套围绕用户需求、商业目标与实现路径的产品思维。面向独立开发与增长场景，重点说明为什么每个角色都在影响产品，以及这种思维如何帮助改进研究、转化、留存与迭代。","audience":"独立开发者、增长营销从业者、刚接触产品思维的创业者与内容读者","imageSize":"1536x864","imageModel":"gpt-image-2","plannerModel":"gpt-5.4"},"children":[]},"breadcrumbs":[{"id":"4dc3f3af-bd00-4742-a922-5d94722d05f2","slug":"独立开发增长营销流量综合阅读书单推荐-4dc3f3af","title":"独立开发增长营销流量综合阅读书单推荐","type":"page","url":"https://drillso.com/en/share/sessions/C6j7J1Pqk2dm/%E7%8B%AC%E7%AB%8B%E5%BC%80%E5%8F%91%E5%A2%9E%E9%95%BF%E8%90%A5%E9%94%80%E6%B5%81%E9%87%8F%E7%BB%BC%E5%90%88%E9%98%85%E8%AF%BB%E4%B9%A6%E5%8D%95%E6%8E%A8%E8%8D%90-4dc3f3af","agentUrl":"https://drillso.com/en/share/sessions/C6j7J1Pqk2dm/agent.json?node=%E7%8B%AC%E7%AB%8B%E5%BC%80%E5%8F%91%E5%A2%9E%E9%95%BF%E8%90%A5%E9%94%80%E6%B5%81%E9%87%8F%E7%BB%BC%E5%90%88%E9%98%85%E8%AF%BB%E4%B9%A6%E5%8D%95%E6%8E%A8%E8%8D%90-4dc3f3af"},{"id":"da0ab35a-5cc9-4d2a-b623-a3ef823ed4c1","slug":"人人都是产品经理-da0ab35a","title":"《人人都是产品经理》","type":"page","url":"https://drillso.com/en/share/sessions/C6j7J1Pqk2dm/%E4%BA%BA%E4%BA%BA%E9%83%BD%E6%98%AF%E4%BA%A7%E5%93%81%E7%BB%8F%E7%90%86-da0ab35a","agentUrl":"https://drillso.com/en/share/sessions/C6j7J1Pqk2dm/agent.json?node=%E4%BA%BA%E4%BA%BA%E9%83%BD%E6%98%AF%E4%BA%A7%E5%93%81%E7%BB%8F%E7%90%86-da0ab35a"}],"parent":{"id":"da0ab35a-5cc9-4d2a-b623-a3ef823ed4c1","slug":"人人都是产品经理-da0ab35a","title":"《人人都是产品经理》","type":"page","url":"https://drillso.com/en/share/sessions/C6j7J1Pqk2dm/%E4%BA%BA%E4%BA%BA%E9%83%BD%E6%98%AF%E4%BA%A7%E5%93%81%E7%BB%8F%E7%90%86-da0ab35a","agentUrl":"https://drillso.com/en/share/sessions/C6j7J1Pqk2dm/agent.json?node=%E4%BA%BA%E4%BA%BA%E9%83%BD%E6%98%AF%E4%BA%A7%E5%93%81%E7%BB%8F%E7%90%86-da0ab35a"},"children":[],"fullTree":null,"warnings":[],"truncated":false}