CommunityBildgithub.com

cbrock84/visual-content

Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals that are not stopping the scroll.

Was ist visual-content?

visual-content is a Claude Code agent skill that designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals that are not stopping the scroll.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/visual-content

Installed? Explore more Bild skills: steipete/songsee, affaan-m/frontend-design-direction, affaan-m/ios-icon-gen · View all 6 →

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Visual content

The format follows the content's shape

  • Sequence or process → carousel. One step per slide, one idea per slide.
  • Comparison or relationship → single diagram. A carousel would break what needs to be seen at once.
  • A single memorable claim → quote graphic.
  • Quantity, trend, or proportion → chart, with one message.
  • Anything with more than about seven elements → it is two visuals.

Choosing format by what is fashionable rather than by the content's shape is why so many carousels are a paragraph cut into ten pieces.

Carousels

The first slide is the entire hook — treat it as a headline, not a title card. Every subsequent slide must earn the swipe, which means each ends slightly incomplete.

Consistent template across slides: same margins, same type positions, same palette. Variation across slides reads as error. Number them so the reader knows the commitment.

Last slide lands the idea. A last slide that only says "follow for more" wastes the only slide with guaranteed attention from everyone who finished.

Infographics and diagrams

A diagram earns its place when it shows a relationship prose would take three paragraphs to establish. If it restates the text, cut it.

Label directly on the element. Legends make the reader hold a mapping in memory while looking elsewhere. Strip anything not carrying meaning — decorative gradients, 3D effects, and drop shadows on data.

Designing for the actual context

Almost all of this is seen small, on a phone, in a feed, at speed. Test at that size before finishing. If the headline is not readable at thumbnail scale, it does not exist.

High contrast between subject and background is what stops the scroll. Subtlety is a desktop luxury.

Where images are generated

Write the prompt as a brief: subject, composition, lighting, palette, mood, and negative constraints. Generate one concept per image. Then check the output actually renders any embedded text correctly and matches the brand palette — generated imagery drifts, and drifted brand color is worse than no brand color.

Never

  • Choose a visual format before knowing whether the content is a sequence, a comparison, or a single claim.
  • Design at full size for something that will be seen at thumbnail size.
  • Put load-bearing information in an image alone. It is unsearchable, untranslatable, and invisible to a screen reader.

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

cbrock84/interface-craft

Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.

cbrock84/org-design

Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.

cbrock84/portfolio-governance

Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.

cbrock84/product-launch

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day.

cbrock84/program-management

Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.

cbrock84/project-delivery

Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.

cbrock84/retention

Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.

cbrock84/sales-enablement

Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.

cbrock84/tax

Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check what a remote hire or new market triggers.

cbrock84/unit-economics

Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.

cbrock84/video-content

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

Verwandte Skills