[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CQTSHSQXKXC3YEWSSYRCG":3,"skill-same:01M75CQTSHSQXKXC3YEWSSYRCG":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M75CQTSHSQXKXC3YEWSSYRCG","infographic-generator",null,"Generate branded infographic specifications from any content or data. Outputs structured layout, copy, data visualization, and color scheme — ready to render as HTML\u002FCSS, 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\".","LongLeo287\u002FSEOSONA-OS","LongLeo287","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141803367?v=4","01M6JK75C62VCNZKR5BRZ386YV","LongLeo","01M75CK60XQGYJY3YDGGFJQDYT",2,"MIT","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Faffiliate-skills\u002Fskills\u002Fcontent\u002Finfographic-generator\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: infographic-generator\ndescription: >\n  Generate branded infographic specifications from any content or data. Outputs structured\n  layout, copy, data visualization, and color scheme — ready to render as HTML\u002FCSS,\n  Satori, Canva, or any design tool. Use this skill when the user wants an infographic,\n  data visual, social media image, comparison chart, stat card, or says \"create an\n  infographic for [content]\", \"make a visual for my LinkedIn post\", \"design an image\n  for [topic]\", \"stat graphic for [data]\", \"comparison infographic\", \"branded image\",\n  \"social media graphic\", \"infographic for [blog post]\", \"data visualization\",\n  \"visual content\", \"image for my post\", \"LinkedIn carousel image\", \"feature comparison\n  chart\", \"pricing table image\".\nlicense: MIT\nversion: \"1.0.0\"\ntags: [\"affiliate-marketing\", \"content-creation\", \"infographic\", \"visual\", \"design\", \"branded\"]\ncompatibility: \"Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent\"\nmetadata:\n  author: affitor\n  version: \"1.0\"\n  stage: S2-Content\n---\n\n# Infographic Generator\n\nGenerate complete infographic specifications from any content, data, or topic.\nOutputs structured layout + all copy + data points + color scheme — ready to render\nas HTML\u002FCSS, with [Satori](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fsatori) (server-side), in Canva,\nFigma, or any design tool.\n\n**LinkedIn posts with images get 2-3x more engagement.** This skill turns your content\ninto visual assets without design skills.\n\nInspired by [content-pipeline](https:\u002F\u002Fgithub.com\u002FAffitor\u002Fcontent-pipeline)'s Satori\nrendering: AI writes the content → structured spec → rendered as a branded image.\n\n## Stage\n\nThis skill belongs to Stage S2: Content\n\n## When to Use\n\n- After `viral-post-writer` creates a LinkedIn post — add a visual\n- After `content-research-brief` collects stats — visualize them\n- When creating comparison content — feature\u002Fpricing comparison chart\n- When sharing data or stats — stat highlight cards\n- When creating a listicle — visual checklist or numbered list\n- For any social media post that would benefit from a branded image\n\n## Input Schema\n\n```yaml\ncontent: string                # (required) Content to visualize — post text, data, or article\ninfographic_type: string       # (optional, default: auto-detected)\n                               # \"stat_highlight\" — 1-3 key numbers, large and bold\n                               # \"comparison\" — side-by-side product\u002Ffeature comparison\n                               # \"process_flow\" — step-by-step workflow or how-to\n                               # \"checklist\" — list of items with checkmarks\n                               # \"timeline\" — chronological events\n                               # \"data_chart\" — bar\u002Fpie chart representation\n                               # \"quote_card\" — featured quote with attribution\n                               # \"feature_grid\" — grid of features\u002Fbenefits with icons\nplatform: string               # (optional, default: \"linkedin\")\n                               # \"linkedin\" — 1080×1350 (portrait, optimal engagement)\n                               # \"instagram\" — 1080×1080 (square)\n                               # \"twitter\" — 1200×675 (landscape)\n                               # \"facebook\" — 1200×630\n                               # \"blog\" — 1200×800 (featured image)\nbrand: object                  # (optional) Brand customization\n  name: string                 # Company\u002Fpersonal brand name\n  primary_color: string        # Hex — \"#0066FF\"\n  secondary_color: string      # Hex — \"#1A1A2E\"\n  accent_color: string         # Hex — \"#FF6B35\"\n  font_style: string           # \"modern\" | \"classic\" | \"bold\" | \"minimal\"\n  logo_text: string            # Text-based logo — \"Affitor\" | \"@yourhandle\"\noutput_format: string          # (optional, default: \"spec\")\n                               # \"spec\" — structured JSON spec (for any renderer)\n                               # \"html\" — renderable HTML\u002FCSS (self-contained)\n                               # \"both\" — spec + HTML\n```\n\n## Workflow\n\n### Step 1: Analyze Content and Select Type\n\nRead the input content and detect the best infographic type:\n\n| Content Pattern | Auto-detected Type |\n|----------------|-------------------|\n| Contains 1-3 prominent numbers\u002Fstats | `stat_highlight` |\n| Contains \"vs\", comparison data | `comparison` |\n| Contains numbered steps or a process | `process_flow` |\n| Contains a list of items (3-10) | `checklist` or `feature_grid` |\n| Contains dates or chronological events | `timeline` |\n| Contains a notable quote | `quote_card` |\n| Contains percentages or proportions | `data_chart` |\n\nIf `infographic_type` is provided, use that. Otherwise auto-detect.\n\n### Step 2: Extract Visual Data\n\nFrom the content, extract exactly what needs to appear in the infographic:\n\n**For `stat_highlight`:**\n```yaml\nstats:\n  - number: \"30%\"        # The big number\n    label: \"commission\"   # What it measures\n    context: \"recurring\"  # Additional context\n  - number: \"60\"\n    label: \"cookie days\"\n    context: \"industry avg: 30\"\n```\n\n**For `comparison`:**\n```yaml\nitems:\n  - name: \"HeyGen\"\n    features:\n      - label: \"Commission\"\n        value: \"30% recurring\"\n        highlight: true         # winner for this row\n      - label: \"Cookie\"\n        value: \"60 days\"\n        highlight: true\n  - name: \"Synthesia\"\n    features:\n      - label: \"Commission\"\n        value: \"25% one-time\"\n        highlight: false\n      - label: \"Cookie\"\n        value: \"30 days\"\n        highlight: false\n```\n\n**For `process_flow`:**\n```yaml\nsteps:\n  - number: 1\n    title: \"Research\"\n    description: \"Find winning programs\"\n    icon: \"🔍\"\n  - number: 2\n    title: \"Create\"\n    description: \"Write content that converts\"\n    icon: \"✍️\"\n```\n\n**For `checklist`:**\n```yaml\nitems:\n  - text: \"Recurring commission\"\n    checked: true\n  - text: \"60+ day cookie\"\n    checked: true\n  - text: \"Free trial available\"\n    checked: true\n  - text: \"Dedicated affiliate manager\"\n    checked: false\n```\n\n### Step 3: Design Layout\n\nBased on type + platform, define the layout:\n\n**Platform dimensions:**\n| Platform | Width | Height | Aspect |\n|----------|-------|--------|--------|\n| LinkedIn | 1080 | 1350 | 4:5 (portrait) |\n| Instagram | 1080 | 1080 | 1:1 (square) |\n| Twitter | 1200 | 675 | 16:9 (landscape) |\n| Facebook | 1200 | 630 | ~2:1 |\n| Blog | 1200 | 800 | 3:2 |\n\n**Layout structure (all types):**\n```\n┌─────────────────────────────┐\n│         HEADER              │  10-15% height\n│    Headline \u002F Title         │\n├─────────────────────────────┤\n│                             │\n│         BODY                │  70-80% height\n│    Data \u002F Content           │\n│    (type-specific layout)   │\n│                             │\n├─────────────────────────────┤\n│         FOOTER              │  10% height\n│    Brand \u002F CTA \u002F Source     │\n└─────────────────────────────┘\n```\n\n### Step 4: Generate Color Scheme\n\n**If brand colors provided:** Use them directly.\n\n**If no brand colors:** Generate a professional palette:\n\n```yaml\n# Default professional palette options\npalettes:\n  dark_modern:       # Dark background, light text\n    bg: \"#1A1A2E\"\n    text: \"#FFFFFF\"\n    accent: \"#0066FF\"\n    secondary: \"#16213E\"\n    \n  light_clean:       # Light background, dark text\n    bg: \"#FFFFFF\"\n    text: \"#1A1A2E\"\n    accent: \"#0066FF\"\n    secondary: \"#F0F4F8\"\n    \n  warm_bold:         # Warm tones\n    bg: \"#FFF8F0\"\n    text: \"#2D2D2D\"\n    accent: \"#FF6B35\"\n    secondary: \"#FFE8D6\"\n    \n  dark_gradient:     # Gradient dark\n    bg: \"linear-gradient(135deg, #1A1A2E, #16213E)\"\n    text: \"#FFFFFF\"\n    accent: \"#00D4AA\"\n    secondary: \"#2A2A4A\"\n```\n\nAuto-select based on platform:\n- LinkedIn → `dark_modern` or `light_clean` (professional)\n- Twitter → `dark_gradient` or `warm_bold` (attention-grabbing)\n- Instagram → Any (most visual flexibility)\n\n### Step 5: Generate All Copy\n\nWrite every piece of text that appears in the infographic:\n\n```yaml\ncopy:\n  headline: string          # Main title — bold, short (max 8 words)\n  subheadline: string       # Optional supporting line\n  body_items: string[]      # Data labels, descriptions, etc.\n  cta: string               # Call-to-action text — \"Link in bio\" | \"See comments for link\"\n  footer: string            # Brand name or @handle\n  source: string            # \"Data: openaffiliate.dev\" or source attribution\n```\n\n**Copy rules:**\n- Headlines: 3-8 words, bold claim or specific number\n- All text must be readable at mobile scale (not too small)\n- No more than 50 total words on the infographic (less = better)\n- Data > adjectives (show numbers, not \"amazing\" or \"incredible\")\n\n### Step 6: Output\n\n**Spec output (default):**\n\nComplete structured spec that any renderer can consume:\n\n```yaml\ninfographic_spec:\n  type: string\n  platform: string\n  dimensions:\n    width: number\n    height: number\n  colors:\n    background: string\n    text: string\n    accent: string\n    secondary: string\n  layout:\n    header: object\n    body: object\n    footer: object\n  data: object              # Type-specific data (stats, comparison items, steps, etc.)\n  copy:\n    headline: string\n    subheadline: string\n    body_items: string[]\n    cta: string\n    footer: string\n    source: string\n```\n\n**HTML output (if `output_format` is \"html\" or \"both\"):**\n\nGenerate a self-contained HTML file with inline CSS that renders the infographic\nat exact dimensions. This can be:\n- Opened in a browser and screenshotted\n- Rendered server-side with Satori or Puppeteer\n- Used as a starting point for design iteration\n\n```html\n\u003C!-- Self-contained, no external dependencies -->\n\u003Cdiv style=\"width: 1080px; height: 1350px; ...\">\n  \u003C!-- Header -->\n  \u003C!-- Body (type-specific) -->\n  \u003C!-- Footer -->\n\u003C\u002Fdiv>\n```\n\n### Step 7: Self-Validation\n\nBefore presenting output, verify:\n\n- [ ] Total word count on infographic ≤ 50 words\n- [ ] All text readable at 50% zoom (minimum effective font size)\n- [ ] Color contrast meets accessibility (WCAG AA: 4.5:1 ratio)\n- [ ] Data points are accurate and attributed\n- [ ] Layout doesn't feel cramped — whitespace is intentional\n- [ ] Platform dimensions are correct\n\nIf any check fails, fix before delivering.\n\n## Output Format\n\n```markdown\n## Infographic: [Headline]\n\n### Spec\n- **Type:** [stat_highlight]\n- **Platform:** [LinkedIn] — 1080×1350\n- **Colors:** [dark_modern] — bg: #1A1A2E, accent: #0066FF\n\n### Preview (text representation)\n\n┌─────────────────────────────────┐\n│                                 │\n│     HeyGen vs Synthesia         │\n│     The Real Comparison         │\n│                                 │\n│  ┌──────────┐  ┌──────────┐    │\n│  │  HeyGen  │  │Synthesia │    │\n│  │          │  │          │    │\n│  │ 30% rec. │  │ 25% once │    │\n│  │ 60 days  │  │ 30 days  │    │\n│  │ ★ 127    │  │ ★ 84     │    │\n│  └──────────┘  └──────────┘    │\n│                                 │\n│     🏆 Winner: HeyGen           │\n│                                 │\n│  ───────────────────────────    │\n│  @yourhandle · openaffiliate.dev │\n└─────────────────────────────────┘\n\n### Data\n\n[Structured spec as YAML or JSON]\n\n### HTML (if requested)\n\n[Self-contained HTML\u002FCSS code block]\n\n### Next Steps\n- Post to [platform] with your viral post from `viral-post-writer`\n- Create variations for other platforms: `--platform instagram`\n- Generate more infographics from different data in your `content-research-brief`\n```\n\n## Error Handling\n\n- **Content has no extractable data:** Generate a `quote_card` or `checklist` type instead. Note: *\"No numerical data found. Created a [type] infographic instead.\"*\n- **Too much data for one infographic:** Select top 3-5 most impactful data points. Note: *\"Content has [X] data points. Selected the [Y] most impactful for visual clarity. Consider creating multiple infographics.\"*\n- **No brand colors:** Use default palette. Note: *\"No brand colors specified. Using [palette name]. Add brand colors for consistent branding.\"*\n- **HTML output too complex:** Simplify layout. Infographics should be simple — complexity kills visual impact.\n\n## Examples\n\n**Example 1:**\nUser: \"Make an infographic comparing HeyGen vs Synthesia for LinkedIn\"\n→ type: comparison, platform: linkedin (1080×1350)\n→ Extract: commission, cookie, rating, price for each\n→ Output: side-by-side comparison card with winner highlighted\n→ Dark modern palette, bold numbers\n\n**Example 2:**\nUser: \"Create a stat card from my research brief showing HeyGen's key numbers\"\n→ type: stat_highlight, platform: linkedin\n→ Extract: \"$60M raised\", \"40K businesses\", \"30% commission\"\n→ Output: 3 large numbers with labels and context\n\n**Example 3:**\nUser: \"Visualize the affiliate funnel steps as an infographic\"\n→ type: process_flow, platform: blog (1200×800)\n→ Steps: Research → Content → Landing → Deploy → Track → Optimize\n→ Output: horizontal flow with icons and brief descriptions\n\n## Feedback & Issue Reporting\n\nWhen this skill produces unexpected, incomplete, or incorrect output, generate a\n`skill_feedback` block (see `shared\u002Freferences\u002Ffeedback-protocol.md` for full schema).\n\n**Skill-specific failure modes:**\n- **No extractable data from content:** Content is purely narrative, no stats\u002Fnumbers. Report as `data_quality`.\n- **HTML output doesn't render correctly:** CSS issues, wrong dimensions, text overflow. Report as `wrong_output` with the HTML.\n- **Too many words on infographic:** >50 words makes it unreadable. Report as `wrong_output`.\n\n**Auto-detect triggers:**\n- `infographic_spec.data` has \u003C2 data points\n- Total word count in all copy fields > 60\n- Dimensions don't match declared platform\n\nReport issues: [GitHub Issues](https:\u002F\u002Fgithub.com\u002FAffitor\u002Faffiliate-skills\u002Fissues\u002Fnew?labels=skill-feedback&title=infographic-generator) | [Discussions](https:\u002F\u002Fgithub.com\u002FAffitor\u002Faffiliate-skills\u002Fdiscussions\u002Fcategories\u002Fideas)\n\n## References\n\n- `shared\u002Freferences\u002Fsocial-data-providers.md` — data sources for infographic content\n- `shared\u002Freferences\u002Fplatform-rules.md` — platform-specific image requirements\n- `shared\u002Freferences\u002Fflywheel-connections.md` — master flywheel connection map\n- `shared\u002Freferences\u002Ffeedback-protocol.md` — issue detection and reporting standard\n\n## Flywheel Connections\n\n### Feeds Into\n- `social-media-scheduler` (S5) — infographic ready to schedule with post\n- `landing-page-creator` (S4) — infographic as hero image or section visual\n- `email-drip-sequence` (S5) — infographic as email visual content\n- `bio-link-deployer` (S5) — infographic in link hub\n\n### Fed By\n- `content-research-brief` (S2) — key stats and data for visualization\n- `viral-post-writer` (S2) — post content to create accompanying visual\n- `affiliate-blog-builder` (S3) — blog data for featured image infographic\n- `trending-content-scout` (S1) — engagement data for benchmark visuals\n- `traffic-analyzer` (S1) — traffic data for comparison infographics\n- `comparison-post-writer` (S3) — comparison data for visual format\n- `commission-calculator` (S1) — commission data for stat highlights\n\n### Feedback Loop\n- S6 posts with infographics vs without → `performance-report` shows engagement lift → prioritize infographic creation for high-value content\n\n## Quality Gate\n\nBefore delivering output, verify:\n\n1. Would I stop scrolling for this image?\n2. Can I understand the main point in under 3 seconds?\n3. Is the data accurate and attributed?\n4. Does it look professional, not like clip art?\n5. Is it readable on a phone screen?\n\nAny NO → redesign before delivering.\n\n```yaml\nchain_metadata:\n  skill_slug: \"infographic-generator\"\n  stage: \"content\"\n  timestamp: string\n  suggested_next:\n    - \"social-media-scheduler\"\n    - \"viral-post-writer\"\n    - \"landing-page-creator\"\n```\n","# Infographic Generator\n\nGenerate complete infographic specifications from any content, data, or topic.\nOutputs structured layout + all copy + data points + color scheme — ready to render\nas HTML\u002FCSS, with [Satori](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fsatori) (server-side), in Canva,\nFigma, or any design tool.\n\n**LinkedIn posts with images get 2-3x more engagement.** This skill turns your content\ninto visual assets without design skills.\n\nInspired by [content-pipeline](https:\u002F\u002Fgithub.com\u002FAffitor\u002Fcontent-pipeline)'s Satori\nrendering: AI writes the content → structured spec → rendered as a branded image.\n\n## Stage\n\nThis skill belongs to Stage S2: Content\n\n## When to Use\n\n- After `viral-post-writer` creates a LinkedIn post — add a visual\n- After `content-research-brief` collects stats — visualize them\n- When creating comparison content — feature\u002Fpricing comparison chart\n- When sharing data or stats — stat highlight cards\n- When creating a listicle — visual checklist or numbered list\n- For any social media post that would benefit from a branded image\n\n## Input Schema\n\n```yaml\ncontent: string                # (required) Content to visualize — post text, data, or article\ninfographic_type: string       # (optional, default: auto-detected)\n                               # \"stat_highlight\" — 1-3 key numbers, large and bold\n                               # \"comparison\" — side-by-side product\u002Ffeature comparison\n                               # \"process_flow\" — step-by-step workflow or how-to\n                               # \"checklist\" — list of items with checkmarks\n                               # \"timeline\" — chronological events\n                               # \"data_chart\" — bar\u002Fpie chart representation\n                               # \"quote_card\" — featured quote with attribution\n                               # \"feature_grid\" — grid of features\u002Fbenefits with icons\nplatform: string               # (optional, default: \"linkedin\")\n                               # \"linkedin\" — 1080×1350 (portrait, optimal engagement)\n                               # \"instagram\" — 1080×1080 (square)\n                               # \"twitter\" — 1200×675 (landscape)\n                               # \"facebook\" — 1200×630\n                               # \"blog\" — 1200×800 (featured image)\nbrand: object                  # (optional) Brand customization\n  name: string                 # Company\u002Fpersonal brand name\n  primary_color: string        # Hex — \"#0066FF\"\n  secondary_color: string      # Hex — \"#1A1A2E\"\n  accent_color: string         # Hex — \"#FF6B35\"\n  font_style: string           # \"modern\" | \"classic\" | \"bold\" | \"minimal\"\n  logo_text: string            # Text-based logo — \"Affitor\" | \"@yourhandle\"\noutput_format: string          # (optional, default: \"spec\")\n                               # \"spec\" — structured JSON spec (for any renderer)\n                               # \"html\" — renderable HTML\u002FCSS (self-contained)\n                               # \"both\" — spec + HTML\n```\n\n## Workflow\n\n### Step 1: Analyze Content and Select Type\n\nRead the input content and detect the best infographic type:\n\n| Content Pattern | Auto-detected Type |\n|----------------|-------------------|\n| Contains 1-3 prominent numbers\u002Fstats | `stat_highlight` |\n| Contains \"vs\", comparison data | `comparison` |\n| Contains numbered steps or a process | `process_flow` |\n| Contains a list of items (3-10) | `checklist` or `feature_grid` |\n| Contains dates or chronological events | `timeline` |\n| Contains a notable quote | `quote_card` |\n| Contains percentages or proportions | `data_chart` |\n\nIf `infographic_type` is provided, use that. Otherwise auto-detect.\n\n### Step 2: Extract Visual Data\n\nFrom the content, extract exactly what needs to appear in the infographic:\n\n**For `stat_highlight`:**\n```yaml\nstats:\n  - number: \"30%\"        # The big number\n    label: \"commission\"   # What it measures\n    context: \"recurring\"  # Additional context\n  - number: \"60\"\n    label: \"cookie days\"\n    context: \"industry avg: 30\"\n```\n\n**For `comparison`:**\n```yaml\nitems:\n  - name: \"HeyGen\"\n    features:\n      - label: \"Commission\"\n        value: \"30% recurring\"\n        highlight: true         # winner for this row\n      - label: \"Cookie\"\n        value: \"60 days\"\n        highlight: true\n  - name: \"Synthesia\"\n    features:\n      - label: \"Commission\"\n        value: \"25% one-time\"\n        highlight: false\n      - label: \"Cookie\"\n        value: \"30 days\"\n        highlight: false\n```\n\n**For `process_flow`:**\n```yaml\nsteps:\n  - number: 1\n    title: \"Research\"\n    description: \"Find winning programs\"\n    icon: \"🔍\"\n  - number: 2\n    title: \"Create\"\n    description: \"Write content that converts\"\n    icon: \"✍️\"\n```\n\n**For `checklist`:**\n```yaml\nitems:\n  - text: \"Recurring commission\"\n    checked: true\n  - text: \"60+ day cookie\"\n    checked: true\n  - text: \"Free trial available\"\n    checked: true\n  - text: \"Dedicated affiliate manager\"\n    checked: false\n```\n\n### Step 3: Design Layout\n\nBased on type + platform, define the layout:\n\n**Platform dimensions:**\n| Platform | Width | Height | Aspect |\n|----------|-------|--------|--------|\n| LinkedIn | 1080 | 1350 | 4:5 (portrait) |\n| Instagram | 1080 | 1080 | 1:1 (square) |\n| Twitter | 1200 | 675 | 16:9 (landscape) |\n| Facebook | 1200 | 630 | ~2:1 |\n| Blog | 1200 | 800 | 3:2 |\n\n**Layout structure (all types):**\n```\n┌─────────────────────────────┐\n│         HEADER              │  10-15% height\n│    Headline \u002F Title         │\n├─────────────────────────────┤\n│                             │\n│         BODY                │  70-80% height\n│    Data \u002F Content           │\n│    (type-specific layout)   │\n│                             │\n├─────────────────────────────┤\n│         FOOTER              │  10% height\n│    Brand \u002F CTA \u002F Source     │\n└─────────────────────────────┘\n```\n\n### Step 4: Generate Color Scheme\n\n**If brand colors provided:** Use them directly.\n\n**If no brand colors:** Generate a professional palette:\n\n```yaml\n# Default professional palette options\npalettes:\n  dark_modern:       # Dark background, light text\n    bg: \"#1A1A2E\"\n    text: \"#FFFFFF\"\n    accent: \"#0066FF\"\n    secondary: \"#16213E\"\n    \n  light_clean:       # Light background, dark text\n    bg: \"#FFFFFF\"\n    text: \"#1A1A2E\"\n    accent: \"#0066FF\"\n    secondary: \"#F0F4F8\"\n    \n  warm_bold:         # Warm tones\n    bg: \"#FFF8F0\"\n    text: \"#2D2D2D\"\n    accent: \"#FF6B35\"\n    secondary: \"#FFE8D6\"\n    \n  dark_gradient:     # Gradient dark\n    bg: \"linear-gradient(135deg, #1A1A2E, #16213E)\"\n    text: \"#FFFFFF\"\n    accent: \"#00D4AA\"\n    secondary: \"#2A2A4A\"\n```\n\nAuto-select based on platform:\n- LinkedIn → `dark_modern` or `light_clean` (professional)\n- Twitter → `dark_gradient` or `warm_bold` (attention-grabbing)\n- Instagram → Any (most visual flexibility)\n\n### Step 5: Generate All Copy\n\nWrite every piece of text that appears in the infographic:\n\n```yaml\ncopy:\n  headline: string          # Main title — bold, short (max 8 words)\n  subheadline: string       # Optional supporting line\n  body_items: string[]      # Data labels, descriptions, etc.\n  cta: string               # Call-to-action text — \"Link in bio\" | \"See comments for link\"\n  footer: string            # Brand name or @handle\n  source: string            # \"Data: openaffiliate.dev\" or source attribution\n```\n\n**Copy rules:**\n- Headlines: 3-8 words, bold claim or specific number\n- All text must be readable at mobile scale (not too small)\n- No more than 50 total words on the infographic (less = better)\n- Data > adjectives (show numbers, not \"amazing\" or \"incredible\")\n\n### Step 6: Output\n\n**Spec output (default):**\n\nComplete structured spec that any renderer can consume:\n\n```yaml\ninfographic_spec:\n  type: string\n  platform: string\n  dimensions:\n    width: number\n    height: number\n  colors:\n    background: string\n    text: string\n    accent: string\n    secondary: string\n  layout:\n    header: object\n    body: object\n    footer: object\n  data: object              # Type-specific data (stats, comparison items, steps, etc.)\n  copy:\n    headline: string\n    subheadline: string\n    body_items: string[]\n    cta: string\n    footer: string\n    source: string\n```\n\n**HTML output (if `output_format` is \"html\" or \"both\"):**\n\nGenerate a self-contained HTML file with inline CSS that renders the infographic\nat exact dimensions. This can be:\n- Opened in a browser and screenshotted\n- Rendered server-side with Satori or Puppeteer\n- Used as a starting point for design iteration\n\n```html\n\u003C!-- Self-contained, no external dependencies -->\n\u003Cdiv style=\"width: 1080px; height: 1350px; ...\">\n  \u003C!-- Header -->\n  \u003C!-- Body (type-specific) -->\n  \u003C!-- Footer -->\n\u003C\u002Fdiv>\n```\n\n### Step 7: Self-Validation\n\nBefore presenting output, verify:\n\n- [ ] Total word count on infographic ≤ 50 words\n- [ ] All text readable at 50% zoom (minimum effective font size)\n- [ ] Color contrast meets accessibility (WCAG AA: 4.5:1 ratio)\n- [ ] Data points are accurate and attributed\n- [ ] Layout doesn't feel cramped — whitespace is intentional\n- [ ] Platform dimensions are correct\n\nIf any check fails, fix before delivering.\n\n## Output Format\n\n```markdown\n## Infographic: [Headline]\n\n### Spec\n- **Type:** [stat_highlight]\n- **Platform:** [LinkedIn] — 1080×1350\n- **Colors:** [dark_modern] — bg: #1A1A2E, accent: #0066FF\n\n### Preview (text representation)\n\n┌─────────────────────────────────┐\n│                                 │\n│     HeyGen vs Synthesia         │\n│     The Real Comparison         │\n│                                 │\n│  ┌──────────┐  ┌──────────┐    │\n│  │  HeyGen  │  │Synthesia │    │\n│  │          │  │          │    │\n│  │ 30% rec. │  │ 25% once │    │\n│  │ 60 days  │  │ 30 days  │    │\n│  │ ★ 127    │  │ ★ 84     │    │\n│  └──────────┘  └──────────┘    │\n│                                 │\n│     🏆 Winner: HeyGen           │\n│                                 │\n│  ───────────────────────────    │\n│  @yourhandle · openaffiliate.dev │\n└─────────────────────────────────┘\n\n### Data\n\n[Structured spec as YAML or JSON]\n\n### HTML (if requested)\n\n[Self-contained HTML\u002FCSS code block]\n\n### Next Steps\n- Post to [platform] with your viral post from `viral-post-writer`\n- Create variations for other platforms: `--platform instagram`\n- Generate more infographics from different data in your `content-research-brief`\n```\n\n## Error Handling\n\n- **Content has no extractable data:** Generate a `quote_card` or `checklist` type instead. Note: *\"No numerical data found. Created a [type] infographic instead.\"*\n- **Too much data for one infographic:** Select top 3-5 most impactful data points. Note: *\"Content has [X] data points. Selected the [Y] most impactful for visual clarity. Consider creating multiple infographics.\"*\n- **No brand colors:** Use default palette. Note: *\"No brand colors specified. Using [palette name]. Add brand colors for consistent branding.\"*\n- **HTML output too complex:** Simplify layout. Infographics should be simple — complexity kills visual impact.\n\n## Examples\n\n**Example 1:**\nUser: \"Make an infographic comparing HeyGen vs Synthesia for LinkedIn\"\n→ type: comparison, platform: linkedin (1080×1350)\n→ Extract: commission, cookie, rating, price for each\n→ Output: side-by-side comparison card with winner highlighted\n→ Dark modern palette, bold numbers\n\n**Example 2:**\nUser: \"Create a stat card from my research brief showing HeyGen's key numbers\"\n→ type: stat_highlight, platform: linkedin\n→ Extract: \"$60M raised\", \"40K businesses\", \"30% commission\"\n→ Output: 3 large numbers with labels and context\n\n**Example 3:**\nUser: \"Visualize the affiliate funnel steps as an infographic\"\n→ type: process_flow, platform: blog (1200×800)\n→ Steps: Research → Content → Landing → Deploy → Track → Optimize\n→ Output: horizontal flow with icons and brief descriptions\n\n## Feedback & Issue Reporting\n\nWhen this skill produces unexpected, incomplete, or incorrect output, generate a\n`skill_feedback` block (see `shared\u002Freferences\u002Ffeedback-protocol.md` for full schema).\n\n**Skill-specific failure modes:**\n- **No extractable data from content:** Content is purely narrative, no stats\u002Fnumbers. Report as `data_quality`.\n- **HTML output doesn't render correctly:** CSS issues, wrong dimensions, text overflow. Report as `wrong_output` with the HTML.\n- **Too many words on infographic:** >50 words makes it unreadable. Report as `wrong_output`.\n\n**Auto-detect triggers:**\n- `infographic_spec.data` has \u003C2 data points\n- Total word count in all copy fields > 60\n- Dimensions don't match declared platform\n\nReport issues: [GitHub Issues](https:\u002F\u002Fgithub.com\u002FAffitor\u002Faffiliate-skills\u002Fissues\u002Fnew?labels=skill-feedback&title=infographic-generator) | [Discussions](https:\u002F\u002Fgithub.com\u002FAffitor\u002Faffiliate-skills\u002Fdiscussions\u002Fcategories\u002Fideas)\n\n## References\n\n- `shared\u002Freferences\u002Fsocial-data-providers.md` — data sources for infographic content\n- `shared\u002Freferences\u002Fplatform-rules.md` — platform-specific image requirements\n- `shared\u002Freferences\u002Fflywheel-connections.md` — master flywheel connection map\n- `shared\u002Freferences\u002Ffeedback-protocol.md` — issue detection and reporting standard\n\n## Flywheel Connections\n\n### Feeds Into\n- `social-media-scheduler` (S5) — infographic ready to schedule with post\n- `landing-page-creator` (S4) — infographic as hero image or section visual\n- `email-drip-sequence` (S5) — infographic as email visual content\n- `bio-link-deployer` (S5) — infographic in link hub\n\n### Fed By\n- `content-research-brief` (S2) — key stats and data for visualization\n- `viral-post-writer` (S2) — post content to create accompanying visual\n- `affiliate-blog-builder` (S3) — blog data for featured image infographic\n- `trending-content-scout` (S1) — engagement data for benchmark visuals\n- `traffic-analyzer` (S1) — traffic data for comparison infographics\n- `comparison-post-writer` (S3) — comparison data for visual format\n- `commission-calculator` (S1) — commission data for stat highlights\n\n### Feedback Loop\n- S6 posts with infographics vs without → `performance-report` shows engagement lift → prioritize infographic creation for high-value content\n\n## Quality Gate\n\nBefore delivering output, verify:\n\n1. Would I stop scrolling for this image?\n2. Can I understand the main point in under 3 seconds?\n3. Is the data accurate and attributed?\n4. Does it look professional, not like clip art?\n5. Is it readable on a phone screen?\n\nAny NO → redesign before delivering.\n\n```yaml\nchain_metadata:\n  skill_slug: \"infographic-generator\"\n  stage: \"content\"\n  timestamp: string\n  suggested_next:\n    - \"social-media-scheduler\"\n    - \"viral-post-writer\"\n    - \"landing-page-creator\"\n```\n",{"name":5,"tags":24,"license":15,"version":31,"metadata":32,"description":36,"compatibility":37},[25,26,27,28,29,30],"affiliate-marketing","content-creation","infographic","visual","design","branded","1.0.0",{"stage":33,"author":34,"version":35},"S2-Content","affitor","1.0","Generate branded infographic specifications from any content or data. Outputs structured layout, copy, data visualization, and color scheme — ready to render as HTML\u002FCSS, 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\".\n","Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent","main","4fd50b1281e8cd978866b6b4556242605cabf708",".agents\u002Fskills\u002Faffiliate-skills\u002Fskills\u002Fcontent\u002Finfographic-generator",1,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS","https:\u002F\u002Fseosona-os.vercel.app","https:\u002F\u002Fgithub.com\u002FLongLeo287","https:\u002F\u002Fwww.facebook.com\u002FResourceRookie2023","2026-10-09 15:14:13",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add LongLeo287\u002FSEOSONA-OS --skill infographic-generator",{"tool":53,"command":54},"bunx","bunx skills add LongLeo287\u002FSEOSONA-OS --skill infographic-generator",{"tool":56,"command":57},"pnpm","pnpm dlx skills add LongLeo287\u002FSEOSONA-OS --skill infographic-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Faffiliate-skills\u002Fskills\u002Fcontent\u002Finfographic-generator\u002FSKILL.md",true,[],[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M75F0T3V3W7JQQ05X26NNN2T","web_crawler_katana","High-speed web crawling using Katana patterns for deep site mapping, URL discovery, and content extraction.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fweb_crawler_katana\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M75F0Q2QJXDGAFKC7D84GT88","server_log_analyzer","Analyzes Nginx\u002FApache server logs to identify Googlebot crawl patterns, errors, and performance bottlenecks.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fserver_log_analyzer\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M75F0KZP6D8R8XPN2YT35BAJ","schema_markup_generator","Auto-generates JSON-LD structured data for any page type (Article, Product, FAQ, LocalBusiness, etc.).","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fschema_markup_generator\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M75F0G3KX4Y86AXJXTKXVEVA","internal_linking_optimizer","Analyzes and optimizes the internal link graph of a website for SEO authority distribution.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Finternal_linking_optimizer\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M75F0CS1RYX4YPJC7N6RAAQJ","google_trends_analyzer","Detects trending topics and seasonal patterns using Google Trends data for content planning and keyword strategy.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fgoogle_trends_analyzer\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M75F0ASMQ1GKPFX82D19SRTN","brand_context_analyzer","Tracks brand mentions, sentiment, and online reputation across web sources.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fbrand_context_analyzer\u002FSKILL.md",[],[]]