When the user wants to plan, create, or repurpose visual content (images, infographics, social post images) across channels. Also use when the user mentions "content images," "social media images," "infographic," "visual content," "post image," "image specs," "visual repurposing," "content visuals," or "image for social post." For Pinterest, use pinterest-posts.
Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.
读取 https://funcoding.ai/skills/kostja94/marketing-skills/visual-content/install.md ，按里面的步骤帮我安装这个 Skill。
Guides visual content planning and creation across website, social media, email, and other channels. Images are needed not just for websites—social posts, infographics, and repurposed content all require visuals. Visual-first planning in content calendars improves engagement; cross-channel consistency and repurposing maximize ROI.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
Identify:
| Content Type | Visual Need | Notes |
|---|---|---|
| Article / Blog | Hero image, in-article images, screenshots | See image-optimization for web (alt, WebP, LCP) |
| Social post | Single image, carousel, or link preview | Platform-specific specs below |
| Infographic | Primary format; data visualization | Repurpose to social (cropped), blog (full) |
| Case study | Customer photo, results chart, logo | Repurpose to LinkedIn carousel, blog |
| Product update | Screenshot, feature graphic | Changelog, email, social |
| Header image, inline graphics | Keep lightweight; many clients block images | |
| Landing page | Hero, trust badges, screenshots | See hero-generator, image-optimization |
| Context | Priority | Skill |
|---|---|---|
| Website | Alt text, WebP, LCP, responsive, lazy loading | image-optimization |
| Social posts | Platform dimensions, aspect ratio, file size | Platform skills (X, LinkedIn, Pinterest, etc.) |
| OG / Twitter Cards | 1200×630, 1200×675 for link previews | open-graph, twitter-cards |
| Inline-friendly; avoid heavy images; alt for blocked | email-marketing |
| Platform | Post Image | Stories / Reels | Profile | Notes |
|---|---|---|---|---|
| X (Twitter) | 1200×675 (16:9), 800×800 | — | 400×400 | See twitter-x-posts |
| 1200×627, 1200×1200; carousel up to 20 | — | 400×400 | See linkedin-posts; vertical preferred on mobile | |
| 1000×1500 (2:3) | — | 165×165 | Alt text ~25% more impressions; see pinterest-posts | |
| 1080×1350 (4:5), 1080×1080 | 1080×1920 (9:16) | 320×320 | 4:5 outperforms square on feed | |
| 1200×630, 1080×1080 | 1080×1920 | 320×320 | ||
| YouTube | Thumbnail 1280×720 | — | 800×800 |
General: 1080px width works across most platforms; vertical (4:5, 9:16) outperforms square on mobile-first feeds. Keep critical elements (logo, text) in safe center—platforms may crop.
Principle: One core visual → multiple crops/formats → multiple channels.
| Core Visual | Adaptations | Channels |
|---|---|---|
| Infographic | Full (blog), cropped sections (Instagram, LinkedIn carousel), square (X) | Blog, LinkedIn, Instagram, X |
| Case study graphic | Hero (blog), single slide (LinkedIn), story (Instagram) | Blog, LinkedIn, Instagram |
| Product screenshot | Hero (landing), post (X, LinkedIn), email header | Website, social, email |
| Quote graphic | Square (X, LinkedIn), 4:5 (Instagram) | X, LinkedIn, Instagram |
Workflow: Design at largest needed size; export platform-specific crops. Use consistent colors, fonts, logo placement (see brand-visual-generator).
anthropics/skills180kApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
AI & agents
anthropics/skills180kA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
AI & agents
anthropics/skills180kanthropics/skills180kGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
AI & agents
anthropics/skills180kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
AI & agents
anthropics/skills180kStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
AI & agents