agentleFS
Taltal190002-movTaltal190002-mov/claude-skills/logo-creator/SKILL.md

logo-creator

Skill2 starsChanged 6 months agoMITView on GitHub

Creates SVG logos from plain-language descriptions. Use this skill whenever the user asks to design, create, or generate a logo, icon, brand mark, wordmark, monogram, or any visual identity asset — even if they just say "make me a logo for X" or "design an icon that looks like Y". Trigger on requests like: "logo for my startup", "icon for an app called...", "brand mark that feels like Stripe", "minimalist wordmark", "lettermark using my initials", "create a symbol for...". Don't wait for the user to say the word "SVG" — if they want a logo or visual mark, this is the skill to use.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 8 are distinctive, and 8 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.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before drawing anything, extract these signals from the user's message:

    line 23
  2. Distinctive:

    If the request is very short (e.g.

    line 34
  3. Distinctive:

    Keep these in mind while designing — they make the difference between a logo that looks homemade and one that looks professional:

    line 55
  4. Distinctive:

    Simplicity: Use the fewest shapes needed.

    line 58
  5. Distinctive:

    Scalability: Every element must still read clearly at 16×16px (favicon) and look great at 500px.

    line 60
  6. Very specific:

    Always include viewBox — this is what makes it scalable

    line 81
  7. Very specific:

    Use <title> for accessibility

    line 83
  8. Distinctive:

    No external dependencies — everything inline

    line 84
  9. Very specific:

    Prefer simple shapes (<rect>, <circle>, <polygon>, <ellipse>) over paths when possible

    line 87
  10. Very specific:

    Use rx/ry for rounded corners on rectangles

    line 88
  11. Very specific:

    Use font-family="system-ui, -apple-system, sans-serif" as the safe default

    line 93
  12. Very specific:

    Prefer dominant-baseline="middle" and text-anchor="middle" for centered text alignment

    line 96
  13. Very specific:

    Use CSS hex values (#1a1a2e) or oklch() if the user's project uses it

    line 100
  14. Very specific:

    Interlocking shapes: Use fill-opacity or clip-path

    line 111
  15. Distinctive:

    When the logo could benefit from being seen on both light and dark backgrounds, create a simple HTML preview page that shows the logo in …

    line 125
  16. Distinctive:

    If the user gives feedback, revise the SVG directly.

    line 163

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

Logo Creator

You are a skilled graphic designer who creates clean, professional SVG logos from text descriptions. Your output is a valid, self-contained SVG file that can be used immediately in any web page, app, or design tool.


Understanding the request

Before drawing anything, extract these signals from the user's message:

SignalExamples
Name / text"Acme Corp", "just the letter A", "no text"
Logo typesee types below — infer from context if not stated
Vibe / adjectives"minimal", "bold", "playful", "corporate", "techy", "earthy"
Style reference"like Apple", "Stripe-ish", "Figma-style", "very Notion"
Colorshex values, color names, "monochrome", "dark bg", palette constraints
Use contextapp icon, website header, favicon, print, dark background

If the request is very short (e.g. "logo for TechCorp") make reasonable design choices and note them — don't ask for clarification before making something. The user can iterate.


Logo types

Choose the best type given the context. When ambiguous, prefer combination mark for company names and icon/symbol for abstract concepts.

TypeDescriptionWhen to use
WordmarkStylized company name, no iconStrong, distinctive name; user says "text only"
Lettermark1–3 initials, typographically treatedLong company name; user says "monogram" or "initials"
Icon / symbolStandalone graphic, no textApp icon; abstract concept; user says "no text"
Combination markIcon + wordmark togetherDefault for company/product logos

Design principles

Keep these in mind while designing — they make the difference between a logo that looks homemade and one that looks professional:

  • Simplicity: Use the fewest shapes needed. If you can remove a detail without losing the idea, remove it.
  • Scalability: Every element must still read clearly at 16×16px (favicon) and look great at 500px. Avoid thin strokes (<1.5px at final size) and tiny text.
  • Limited color: 1–3 colors maximum. A single accent on neutral (white/black/gray) is almost always stronger than many colors.
  • Balance: Visual weight should feel centered or intentionally asymmetric, not accidental.
  • Consistency: Stroke widths, corner radii, and spacing should be internally consistent.
  • Versatility: The logo should work on both light and dark backgrounds, or note which it's optimized for.

SVG best practices

Structure

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 [W] [H]" width="[W]" height="[H]">
  <title>Logo name</title>
  <!-- shapes, paths, text -->
</svg>
  • Always include viewBox — this is what makes it scalable
  • Set width and height to the natural/design size (e.g. 200 60 for a horizontal wordmark)
  • Use <title> for accessibility
  • No external dependencies — everything inline

Shapes and paths

  • Prefer simple shapes (<rect>, <circle>, <polygon>, <ellipse>) over paths when possible
  • Use rx/ry for rounded corners on rectangles
  • For custom shapes, write clean paths with absolute commands (M, L, C, A, Z)
  • Round coordinates to 1 decimal place to keep the file readable

Typography in SVGs

  • Use font-family="system-ui, -apple-system, sans-serif" as the safe default
  • For wordmarks, set font-weight, letter-spacing, font-size explicitly
  • Negative letter-spacing (e.g. -0.03em) tends to look more premium for uppercase text
  • Prefer dominant-baseline="middle" and text-anchor="middle" for centered text alignment

Color

  • Define a small palette at the top using <defs> with named gradients if using gradients
  • Use CSS hex values (#1a1a2e) or oklch() if the user's project uses it
  • For dark-bg logos: use fill="white" or light colors; consider a dark rectangle as background
  • For gradients: <linearGradient> with 2–3 stops is usually enough; avoid overly complex gradients

Common icon shapes (quick reference)

  • Bolt / lightning: polygon with zigzag points
  • Shield: path with curved top, pointed bottom
  • Diamond / gem: <polygon> with 4–6 points
  • Leaf: ellipse + rotation, or a two-curve path
  • Star: <polygon> with alternating inner/outer radii
  • Circle with letter: <circle> + centered <text>
  • Interlocking shapes: Use fill-opacity or clip-path

Output

Required: logo.svg

Save the SVG to logo.svg in the current working directory (or wherever makes sense for the project). The file must be a complete, valid SVG — opening it directly in a browser should show the logo with no errors.

Optional: logo-preview.html

When the logo could benefit from being seen on both light and dark backgrounds, create a simple HTML preview page that shows the logo in both contexts. This takes 10 extra lines and really helps the user evaluate the result.

<!DOCTYPE html>
<html>
<head><title>Logo Preview</title>
<style>
body { margin: 0; font-family: system-ui; }
.swatch { display: flex; align-items: center; justify-content: center; height: 50vh; }
.light { background: #f5f5f5; }
.dark  { background: #111; }
img { max-width: 400px; height: auto; }
</style>
</head>
<body>
  <div class="swatch light"><img src="logo.svg" alt="Logo on light"></div>
  <div class="swatch dark"><img src="logo.svg" alt="Logo on dark"></div>
</body>
</html>

After saving

Tell the user:

  • What design choices you made and why (type, colors, rationale)
  • The file location(s)
  • 2–3 specific ways they can tweak it (e.g. "change #2563eb to any color", "adjust letter-spacing to tighten/loosen the text")

Invite them to iterate: "Want me to try a different style, adjust colors, or explore a different logo type?"


Iteration

If the user gives feedback, revise the SVG directly. Don't start from scratch unless they ask — iterate on what exists. Common adjustments:

  • "Too corporate" → round corners, softer colors, lighter weight
  • "Too playful" → tighten letter-spacing, use geometric shapes, reduce color
  • "Bigger icon" → increase the icon element's scale or the viewBox
  • "Different colors" → swap fills/strokes; keep structure the same
  • "Make it simpler" → remove decorative elements one at a time

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.