Logo design
Skill1 starsChanged 8 days agoMITView on GitHub
Design a logo system for an app or system interactively, presenting five distinct versions before writing any SVG. Use when the user asks to create, redesign or explore a logo, icon, mark, favicon or brand mark.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- Add skillSkill
- Commit and pushSkill
- GitHub PagesSkill
- Project setupSkill
- READMESkill
- Release cutSkill
- Release summarySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. About 0 are common, 18 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Ask, or infer from the repository:
- Distinctive: line 22
If the user gives nothing, ask only these four and state the defaults you will use:
- Distinctive: line 32
When the user has no idea, present 6 to 8 short directions before any drawing.
- Very specific: line 41
Use the starters in references/concepts.md.
- Very specific: line 47
Always present exactly five labeled versions before creating files: V1 to V5.
- Distinctive: line 76
Do not write SVG until the user explicitly picks a version.
- Very specific: line 94
Use a square viewBox (64×64 or 24×24) with no fixed width/height.
- Distinctive: line 98
No embedded raster images, external references, scripts or filters that break at small sizes.
- Distinctive: line 100
Keep strokes consistent and align shapes to a grid.
- Distinctive: line 102
Keep each file under ~10 KB and trim excessive decimals.
- Very specific: line 103
Use role="img" and a meaningful aria-label only when the SVG is a standalone image.
- Distinctive: line 105
Document the palette and the intended background for each variant.
- Distinctive: line 109
Check the chosen mark:
- Distinctive: line 120
If a variant fails at small sizes, simplify the geometry rather than adding detail.
- Very specific: line 126
Add the mark to README files with light/dark <picture> variants.
- Distinctive: line 127
Add app-icon exports at the sizes the platform requires.
- Distinctive: line 128
Never overwrite an existing brand without approval.
- Distinctive: line 129
Never commit, push or tag unless the user asks.
- Distinctive: line 133
Never skip the five-version comparison.
- Distinctive: line 134
Never trace or closely copy an existing trademark.
- Distinctive: line 135
Never ship a raster image or AI-generated bitmap as the final logo.
- Distinctive: line 136
Never embed text, fonts, secrets or absolute paths in the SVG.
- Distinctive: line 137
Never add a logo to a project without explicit approval.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Logo design
Design a logo system through a short, interactive process. The rule that matters: present five distinct versions and get approval before writing any SVG.
1. Understand the project
Ask, or infer from the repository:
- name and one-line purpose;
- audience and tone: technical, playful, premium, minimal, bold;
- existing colors, typography and brand assets;
- constraints: must work at 16 px, single color, dark background, no text;
- where it will appear: app icon, docs header, README, favicon, social preview;
- words, symbols or competitors to avoid.
If the user gives nothing, ask only these four and state the defaults you will use:
- What is the product, in one sentence?
- Who is it for?
- Which tone: technical, playful, premium or minimal?
- Any color, symbol or cliché to avoid?
2. Offer concept directions
When the user has no idea, present 6 to 8 short directions before any drawing. For each:
- name;
- metaphor or construction;
- one or two sentences describing the visual;
- why it fits the product;
- main risk.
Use the starters in references/concepts.md. Ask the user to pick one or two,
combine them, or say "surprise me". Do not start the five versions until the
direction is clear.
3. Present five versions
Always present exactly five labeled versions before creating files:
V1 to V5.
Each version must be genuinely different, not a color swap. Cover at least:
- one symbol-led mark;
- one monogram or letterform;
- one abstract or metaphorical mark;
- one negative-space or minimal mark;
- one wordmark-led or lockup-led direction.
For each version, include:
| Field | Content |
| Name | Short, memorable |
| Concept | The idea in one sentence |
| Geometry | Shapes, grid, strokes, proportions |
| Palette | Hex values and roles |
| Type | Wordmark font direction or "symbol only" |
| Small size | How it reads at 16–32 px |
| Risk | What could go wrong |
Present them as a compact comparison table or a short list. Then ask:
- which version to build;
- whether to combine elements;
- whether to run another round.
Do not write SVG until the user explicitly picks a version. If the user insists on skipping the comparison, present five one-line versions and ask for a choice; never skip the step silently.
4. Build the SVG system
After approval, create:
| File | Purpose |
logo.svg | Primary mark, light background |
logo-dark.svg | Dark-background variant |
logo-mono.svg | Single color, currentColor |
favicon.svg | Square tile for 16–64 px |
logo-wordmark.svg | Optional horizontal lockup |
Rules:
- Use a square
viewBox(64×64 or 24×24) with no fixedwidth/height. - Build the mark from paths, not
<text>. - For a wordmark, convert letters to paths or document the exact font; never rely on an installed font.
- No embedded raster images, external references, scripts or filters that break at small sizes.
- Keep strokes consistent and align shapes to a grid. Use round caps and joins deliberately.
- Keep each file under ~10 KB and trim excessive decimals.
- Use
role="img"and a meaningfularia-labelonly when the SVG is a standalone image. Decorative marks get an emptyalt. - Document the palette and the intended background for each variant.
5. Validate
Check the chosen mark:
- at 16, 24, 32, 64 and 200 px;
- in one color and in the full palette;
- on white, black, the primary color and a photo or gradient;
- with and without the wordmark;
- that it does not rely on color alone;
- that it is recognizable without text;
- that it is valid XML and opens in a browser;
- that it does not resemble an existing trademark you know of.
If a variant fails at small sizes, simplify the geometry rather than adding detail. A logo is not an illustration.
6. Integrate only when asked
- Replace the favicon and header mark.
- Add the mark to README files with light/dark
<picture>variants. - Add app-icon exports at the sizes the platform requires.
- Never overwrite an existing brand without approval.
- Never commit, push or tag unless the user asks.
Boundaries
- Never skip the five-version comparison.
- Never trace or closely copy an existing trademark.
- Never ship a raster image or AI-generated bitmap as the final logo.
- Never embed text, fonts, secrets or absolute paths in the SVG.
- Never add a logo to a project without explicit approval.
References
references/concepts.md— concept starters and when to use each.references/svg-checklist.md— technical checklist and snippets.
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
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.

