infographic-generator
Generate branded infographic specifications from any content or data. Outputs structured layout, copy, data visualization, and color scheme — ready to render as HTML/CSS, Satori, Canva, or any design tool. Use this skill when the user wants an infographic, data visual, social media image, comparison chart, stat card, or says "create an infographic for [content]", "make a visual for my LinkedIn post", "design an image for [topic]", "stat graphic for [data]", "comparison infographic", "branded image", "social media graphic", "infographic for [blog post]", "data visualization", "visual content", "image for my post", "LinkedIn carousel image", "feature comparison chart", "pricing table image".
What this skill does
# Infographic Generator
Generate complete infographic specifications from any content, data, or topic.
Outputs structured layout + all copy + data points + color scheme — ready to render
as HTML/CSS, with [Satori](https://github.com/vercel/satori) (server-side), in Canva,
Figma, or any design tool.
**LinkedIn posts with images get 2-3x more engagement.** This skill turns your content
into visual assets without design skills.
Inspired by [content-pipeline](https://github.com/Affitor/content-pipeline)'s Satori
rendering: AI writes the content → structured spec → rendered as a branded image.
## Stage
This skill belongs to Stage S2: Content
## When to Use
- After `viral-post-writer` creates a LinkedIn post — add a visual
- After `content-research-brief` collects stats — visualize them
- When creating comparison content — feature/pricing comparison chart
- When sharing data or stats — stat highlight cards
- When creating a listicle — visual checklist or numbered list
- For any social media post that would benefit from a branded image
## Input Schema
```yaml
content: string # (required) Content to visualize — post text, data, or article
infographic_type: string # (optional, default: auto-detected)
# "stat_highlight" — 1-3 key numbers, large and bold
# "comparison" — side-by-side product/feature comparison
# "process_flow" — step-by-step workflow or how-to
# "checklist" — list of items with checkmarks
# "timeline" — chronological events
# "data_chart" — bar/pie chart representation
# "quote_card" — featured quote with attribution
# "feature_grid" — grid of features/benefits with icons
platform: string # (optional, default: "linkedin")
# "linkedin" — 1080×1350 (portrait, optimal engagement)
# "instagram" — 1080×1080 (square)
# "twitter" — 1200×675 (landscape)
# "facebook" — 1200×630
# "blog" — 1200×800 (featured image)
brand: object # (optional) Brand customization
name: string # Company/personal brand name
primary_color: string # Hex — "#0066FF"
secondary_color: string # Hex — "#1A1A2E"
accent_color: string # Hex — "#FF6B35"
font_style: string # "modern" | "classic" | "bold" | "minimal"
logo_text: string # Text-based logo — "Affitor" | "@yourhandle"
output_format: string # (optional, default: "spec")
# "spec" — structured JSON spec (for any renderer)
# "html" — renderable HTML/CSS (self-contained)
# "both" — spec + HTML
```
## Workflow
### Step 1: Analyze Content and Select Type
Read the input content and detect the best infographic type:
| Content Pattern | Auto-detected Type |
|----------------|-------------------|
| Contains 1-3 prominent numbers/stats | `stat_highlight` |
| Contains "vs", comparison data | `comparison` |
| Contains numbered steps or a process | `process_flow` |
| Contains a list of items (3-10) | `checklist` or `feature_grid` |
| Contains dates or chronological events | `timeline` |
| Contains a notable quote | `quote_card` |
| Contains percentages or proportions | `data_chart` |
If `infographic_type` is provided, use that. Otherwise auto-detect.
### Step 2: Extract Visual Data
From the content, extract exactly what needs to appear in the infographic:
**For `stat_highlight`:**
```yaml
stats:
- number: "30%" # The big number
label: "commission" # What it measures
context: "recurring" # Additional context
- number: "60"
label: "cookie days"
context: "industry avg: 30"
```
**For `comparison`:**
```yaml
items:
- name: "HeyGen"
features:
- label: "Commission"
value: "30% recurring"
highlight: true # winner for this row
- label: "Cookie"
value: "60 days"
highlight: true
- name: "Synthesia"
features:
- label: "Commission"
value: "25% one-time"
highlight: false
- label: "Cookie"
value: "30 days"
highlight: false
```
**For `process_flow`:**
```yaml
steps:
- number: 1
title: "Research"
description: "Find winning programs"
icon: "🔍"
- number: 2
title: "Create"
description: "Write content that converts"
icon: "✍️"
```
**For `checklist`:**
```yaml
items:
- text: "Recurring commission"
checked: true
- text: "60+ day cookie"
checked: true
- text: "Free trial available"
checked: true
- text: "Dedicated affiliate manager"
checked: false
```
### Step 3: Design Layout
Based on type + platform, define the layout:
**Platform dimensions:**
| Platform | Width | Height | Aspect |
|----------|-------|--------|--------|
| LinkedIn | 1080 | 1350 | 4:5 (portrait) |
| Instagram | 1080 | 1080 | 1:1 (square) |
| Twitter | 1200 | 675 | 16:9 (landscape) |
| Facebook | 1200 | 630 | ~2:1 |
| Blog | 1200 | 800 | 3:2 |
**Layout structure (all types):**
```
┌─────────────────────────────┐
│ HEADER │ 10-15% height
│ Headline / Title │
├─────────────────────────────┤
│ │
│ BODY │ 70-80% height
│ Data / Content │
│ (type-specific layout) │
│ │
├─────────────────────────────┤
│ FOOTER │ 10% height
│ Brand / CTA / Source │
└─────────────────────────────┘
```
### Step 4: Generate Color Scheme
**If brand colors provided:** Use them directly.
**If no brand colors:** Generate a professional palette:
```yaml
# Default professional palette options
palettes:
dark_modern: # Dark background, light text
bg: "#1A1A2E"
text: "#FFFFFF"
accent: "#0066FF"
secondary: "#16213E"
light_clean: # Light background, dark text
bg: "#FFFFFF"
text: "#1A1A2E"
accent: "#0066FF"
secondary: "#F0F4F8"
warm_bold: # Warm tones
bg: "#FFF8F0"
text: "#2D2D2D"
accent: "#FF6B35"
secondary: "#FFE8D6"
dark_gradient: # Gradient dark
bg: "linear-gradient(135deg, #1A1A2E, #16213E)"
text: "#FFFFFF"
accent: "#00D4AA"
secondary: "#2A2A4A"
```
Auto-select based on platform:
- LinkedIn → `dark_modern` or `light_clean` (professional)
- Twitter → `dark_gradient` or `warm_bold` (attention-grabbing)
- Instagram → Any (most visual flexibility)
### Step 5: Generate All Copy
Write every piece of text that appears in the infographic:
```yaml
copy:
headline: string # Main title — bold, short (max 8 words)
subheadline: string # Optional supporting line
body_items: string[] # Data labels, descriptions, etc.
cta: string # Call-to-action text — "Link in bio" | "See comments for link"
footer: string # Brand name or @handle
source: string # "Data: list.affitor.com" or source attribution
```
**Copy rules:**
- Headlines: 3-8 words, bold claim or specific number
- All text must be readable at mobile scale (not too small)
- No more than 50 total words on the infographic (less = better)
- Data > adjectives (show numbers, not "amazing" or "incredible")
### Step 6: Output
**Spec output (default):**
Complete structured spec that any renderer can consume:
```yaml
infographic_spec:
type: string
platform: string
dimensions:
width: number
height: number
colors:
background: string
text: string
accent: string
secondary: string
layout:
header: object
body: object
footer: object
data: object # Type-specific data (stats, comRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.