LinkedIn Carousel Factory — LinkedIn Carousel 工厂

linkedin-carousel-工厂 Description

生成 a complete 10-slide LinkedIn carousel JSON for .NET developers. Takes a topic and produces a structured, hook-driven carousel ready for Claude Code ACP punch-up before publishing.

Use when OpenClaw trend scout has 应用roved a weekly .NET carousel topic Lam 请求s a new carousel on a specific topic Engine 3 content 流水线 triggers Sunday 9pm 输入 格式化 Topic: [topic] Audience: mid-to-senior .NET developers Goal: [educate | provoke | warn | showcase] Hook angle: [optional — if blank, 代理 picks strongest]

输出 格式化

Return a JSON object with exactly 10 slides:

{ "topic": "...", "hook": "...", "slides": [ { "slide": 1, "type": "hook", "headline": "...", "body": "...", "code": null }, { "slide": 2, "type": "problem", "headline": "...", "body": "...", "code": null }, { "slide": 3, "type": "content", "headline": "...", "body": "...", "code": "..." }, ... { "slide": 10, "type": "cta", "headline": "...", "body": "...", "code": null } ] }

Slide types: hook, problem, content, comparison, 警告, tip, cta

Slide rules Slide 1 (hook): Pattern interrupt. Must make a mid-senior .NET dev 停止 scrolling. Question, counterintuitive clAIm, or "here's what everyone 获取s wrong". Under 12 words. Slides 2–8 (content): Each slide = one idea. Headline under 8 words. Body under 40 words. Code snippets: .NET 8+, syntactically correct, no placeholder comments. Slide 9 (comparison or 警告): Before/after or common mistake. Make the right way obvious. Slide 10 (CTA): Ask for one specific action — follow, comment with X, save for later. Not "like and subscribe." Voice rules Audience: sceptical, experienced. Do not talk down to them. No AI phrases: "it's 导入ant to note", "leveraging", "game-changer", "delve", "in today's world" Concrete > abstract. Show the code, not the concept. Write 输出 to

~/Documents/Obsidian/ClawBrAIn/技能s/draft/carousel-[topic-slug]-[date].json

After generation

Post to Discord #✅-tasks: "Carousel draft ready: [topic]. Review in vault → 技能s/draft/" WAIt for Claude Code ACP punch-up before 发送ing to Lam for 应用roval.

Self-improvement instructions

After Lam 应用roves a carousel: note what hook angle worked in memory/what_works.md under "Engine 3 — Content". After Lam revises: note what was changed and why.