agentleFS
gabrielSantosLimagabrielSantosLima/harness/skills/logo/SKILL.md

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.

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
  1. Distinctive:

    Ask, or infer from the repository:

    line 13
  2. Distinctive:

    If the user gives nothing, ask only these four and state the defaults you will use:

    line 22
  3. Distinctive:

    When the user has no idea, present 6 to 8 short directions before any drawing.

    line 32
  4. Very specific:

    Use the starters in references/concepts.md.

    line 41
  5. Very specific:

    Always present exactly five labeled versions before creating files: V1 to V5.

    line 47
  6. Distinctive:

    Do not write SVG until the user explicitly picks a version.

    line 76
  7. Very specific:

    Use a square viewBox (64×64 or 24×24) with no fixed width/height.

    line 94
  8. Distinctive:

    No embedded raster images, external references, scripts or filters that break at small sizes.

    line 98
  9. Distinctive:

    Keep strokes consistent and align shapes to a grid.

    line 100
  10. Distinctive:

    Keep each file under ~10 KB and trim excessive decimals.

    line 102
  11. Very specific:

    Use role="img" and a meaningful aria-label only when the SVG is a standalone image.

    line 103
  12. Distinctive:

    Document the palette and the intended background for each variant.

    line 105
  13. Distinctive:

    Check the chosen mark:

    line 109
  14. Distinctive:

    If a variant fails at small sizes, simplify the geometry rather than adding detail.

    line 120
  15. Very specific:

    Add the mark to README files with light/dark <picture> variants.

    line 126
  16. Distinctive:

    Add app-icon exports at the sizes the platform requires.

    line 127
  17. Distinctive:

    Never overwrite an existing brand without approval.

    line 128
  18. Distinctive:

    Never commit, push or tag unless the user asks.

    line 129
  19. Distinctive:

    Never skip the five-version comparison.

    line 133
  20. Distinctive:

    Never trace or closely copy an existing trademark.

    line 134
  21. Distinctive:

    Never ship a raster image or AI-generated bitmap as the final logo.

    line 135
  22. Distinctive:

    Never embed text, fonts, secrets or absolute paths in the SVG.

    line 136
  23. Distinctive:

    Never add a logo to a project without explicit approval.

    line 137

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. What is the product, in one sentence?
  2. Who is it for?
  3. Which tone: technical, playful, premium or minimal?
  4. 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:

FieldContent
NameShort, memorable
ConceptThe idea in one sentence
GeometryShapes, grid, strokes, proportions
PaletteHex values and roles
TypeWordmark font direction or "symbol only"
Small sizeHow it reads at 16–32 px
RiskWhat 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:

FilePurpose
logo.svgPrimary mark, light background
logo-dark.svgDark-background variant
logo-mono.svgSingle color, currentColor
favicon.svgSquare tile for 16–64 px
logo-wordmark.svgOptional horizontal lockup

Rules:

  • Use a square viewBox (64×64 or 24×24) with no fixed width/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 meaningful aria-label only when the SVG is a standalone image. Decorative marks get an empty alt.
  • 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.

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.