agentleFS
moronireismoronireis/agent-system-partners/.claude/skills/format-carousel/SKILL.md

format-carousel

Skill0 starsChanged 2 months agoMITView on GitHub

10-slide narrative arcs, slide copy limits, and the visual-brief handoff structure for dsg-ui. Use when mkt-content builds an Instagram or LinkedIn carousel.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every slide must earn the next swipe — the whole carousel is a chain of hooks, not just slide 1.

    line 21
  2. Distinctive:

    If a slide needs a headline plus subtitle plus body plus CTA all at once, it's actually two slides.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Format: Carousel

10-slide carousels for Instagram/LinkedIn. Produced by mkt-content with a dual output: the final slide copy AND a structured visual brief handed to dsg-ui. The brief must be implementable without the designer needing to ask a clarifying question.

10-Slide Narrative Arc

  1. Cover — stop-scroll hook: a contrarian claim, a specific number, or a curiosity gap. Its only job is earning the first swipe. Must be testable in about one second.
  2. Addiction — a line strong enough that stopping feels wrong; usually a reframe of the cover that opens a loop. 3-8. Development — one idea per slide, six slides total. Consecutive slides must contrast (tone, length, claim-vs-proof) — two visually or rhythmically identical slides in a row breaks momentum.
  3. Payoff — the transformation or reframe the reader now owns; the "so what" lands here.
  4. CTA — one specific action, named plainly, with the reason to act now.

Rules That Never Bend

  • One idea per slide — if a slide carries two ideas, split it or cut one.
  • Every slide must earn the next swipe — the whole carousel is a chain of hooks, not just slide 1.
  • Contrast between consecutive slides is deliberate, never accidental.
  • Slide copy stays short — roughly 25 words per slide is the ceiling before mobile readability breaks down; trim or split above that.

Slide Copy Limits

  • Title: short enough to read in under 2 seconds.
  • Body (if present): counts toward the ~25-word ceiling together with the title.
  • If a slide needs a headline plus subtitle plus body plus CTA all at once, it's actually two slides.

Visual Brief Structure (per slide, handed to dsg-ui)

  • Layout — center / left-aligned / top-aligned / full-bleed / split
  • Typography hierarchy — which tier (display / headline / body) carries the slide
  • Background/surface level — per the active project pack's token system
  • Accent usage — where the brand accent appears, if at all
  • Visual element — geometric shape / icon / number / quote mark / none
  • Contrast note vs. previous slide — explicit, one line

Output Format

# Carousel — <Topic>
Platform: <Instagram / LinkedIn / both> | Hook source: <from format-hooks, if any>

## Slide 1 — Cover
Title: <> | Body: <> | Layout: <> | Typography: <> | Visual element: <> | Why this earns the swipe: <>

## Slide 2 — Addiction
[same structure] | Contrast with Slide 1: <>

## Slides 3-8 — Development
[same structure, one block per slide]

## Slide 9 — Payoff
[same structure]

## Slide 10 — CTA
Title: <specific action> | Body: <reason to act now> | Layout: <>

---
Caption brief: <caption, no emoji spam, soft CTA, strategic hashtags per platform norms>

## Designer Handoff (to dsg-ui)
Typography scale: <> | Color token map: <per project pack> | Icon/shape inventory: <per slide> | Spacing/mobile-safe-area notes: <>
Brand compliance checklist: [ ] matches project pack voice/visual tokens [ ] no unapproved elements [ ] platform safe-area respected

Handoff

Slide copy is marked READY FOR MKT-EDITOR and passed to mkt-editor. The visual brief is handed to dsg-ui in parallel — the two streams rejoin before publishing. Never let the visual brief skip the editor gate on the copy side just because design work has already started.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.