agentleFS
Taltal190002-movTaltal190002-mov/claude-skills/visual-generator/SKILL.md

visual-generator

Skill2 starsChanged 6 months agoMITView on GitHub

Generate complete visual assets as HTML/CSS files or SVGs: OG images, social media cards, banners, email headers, property cards, agent profile cards, presentation slides, and UI mockups. Use this skill when the user needs a designed visual output — not just an image, but a full composed layout. Trigger on: "צור כרטיס", "banner", "OG image", "עמוד נחיתה ויזואלי", "social card", "property card", "תמונת פרופיל לסוכן", "כרטיס ביקור דיגיטלי", "presentation slide", "מצגת", "email header", "visual mockup", "תמונה לשיתוף", "open graph". Also use when generating any visual component that needs layout + design, not just a raw photo.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always check for BRAND.md in the project root first.

    line 34
  2. Distinctive:

    Use the defined colors (CSS custom properties)

    line 35
  3. Distinctive:

    If no brand file exists, use a clean neutral palette as default, then offer to run brand-guidelines.

    line 39
  4. Distinctive:

    Use real CSS grid layout, brand colors, rounded corners

    line 57
  5. Distinctive:

    Create a self-contained HTML file:

    line 76
  6. Very specific:

    No external fonts (use system-ui or embed Google Fonts via @import)

    line 100
  7. Very specific:

    No external images (use CSS gradients, SVG shapes, or <img> with placeholder URLs)

    line 101
  8. Distinctive:

    After creating the HTML file, tell the user:

    line 109
  9. Very specific:

    If Playwright MCP is available (mcp__playwright__*), offer to screenshot automatically:

    line 116
  10. Distinctive:

    Consistency: All radii, spacing, and font sizes match the brand system

    line 128
  11. Distinctive:

    Simplicity: Remove anything that doesn't serve the main message

    line 129
  12. Distinctive:

    Always tell the user:

    line 135

≈ “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

Visual Generator

You generate polished visual layouts as self-contained HTML/CSS files that render in a browser and can be screenshotted for use as images, or used directly as UI components.


When to use HTML/CSS vs. raw image generation

Use caseApproach
OG/social share image, banner, cardHTML/CSS → screenshot
Property listing cardHTML/CSS component
Agent profile cardHTML/CSS component
Photo of a place/person/scene→ use image-gen skill instead
Logo / icon→ use logo-creator skill instead

Brand integration

Always check for BRAND.md in the project root first. If found:

  • Use the defined colors (CSS custom properties)
  • Match the typography and border-radius style
  • Apply the tone of visual style described

If no brand file exists, use a clean neutral palette as default, then offer to run brand-guidelines.


Asset types and specs

OG / Social share image

  • Size: 1200×630px
  • Font: large headline (48–72px), short subheadline, logo top-left or bottom
  • Background: gradient or solid brand color; high contrast text
  • Export hint: "screenshot at 1200×630 using Playwright or browser screenshot"

Instagram square post

  • Size: 1080×1080px (simulate at 540×540 in HTML)
  • Bold headline, minimal text, strong visual hierarchy

Property card (for listing)

  • Contains: photo placeholder, address, price, beds/baths/sqm badges, agent name
  • Use real CSS grid layout, brand colors, rounded corners

Agent profile card

  • Contains: photo circle, name, title, phone, email, logo
  • Clean, professional, printable as PDF

Email header banner

  • Width: 600px, height: 160–200px
  • Logo left, headline center/right, CTA button

Presentation slide

  • 16:9 ratio (960×540px)
  • Title, body text area, optional chart/image placeholder
  • Brand colors, clean typography

Output structure

Create a self-contained HTML file:

<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<style>
  /* All styles inline — no external dependencies */
  :root {
    /* brand tokens here */
  }
  * { box-sizing: border-box; margin: 0; padding: 0; }
  body { width: [W]px; height: [H]px; overflow: hidden; }
  /* component styles */
</style>
</head>
<body>
  <!-- visual content -->
</body>
</html>

Key rules:

  • No external fonts (use system-ui or embed Google Fonts via @import)
  • No external images (use CSS gradients, SVG shapes, or <img> with placeholder URLs)
  • The file must render correctly when opened directly in a browser
  • Include a comment at the top: <!-- [asset-name] | [W]x[H]px -->

Screenshot instructions

After creating the HTML file, tell the user:

פתח את הקובץ בדפדפן ועשה צילום מסך בגודל [W]x[H]px.
לחלופין, אם יש Playwright מותקן, אני יכול לצלם אוטומטית.

If Playwright MCP is available (mcp__playwright__*), offer to screenshot automatically:

  1. Navigate to the file URL
  2. Set viewport to exact asset dimensions
  3. Take screenshot and save as PNG

Design principles (applied to all visuals)

  • Hierarchy: One dominant element per visual (headline or image, not both equally)
  • Whitespace: 24–48px padding minimum around content
  • Contrast: Text must pass WCAG AA (4.5:1 ratio on body text)
  • Consistency: All radii, spacing, and font sizes match the brand system
  • Simplicity: Remove anything that doesn't serve the main message

After delivering

Always tell the user:

  1. The file path
  2. The exact pixel dimensions
  3. How to convert to PNG (browser screenshot or Playwright)
  4. 2–3 things easy to customize (change headline, swap color, add photo)

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.