agentleFS
Sign inStart free
jgamaraalvjgamaraalv/delivery-loop/.claude/skills/create-svg/SKILL.md

create-svg

Skill0 starsChanged 4 months agoMITView on GitHub

Create professional SVG logos, brand identities, icons, wordmarks, and visual marks — multiple concepts, layouts, and color variations. Use when asked to design a logo, brand identity, icon, or visual mark.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create professional, scalable SVG logos and visual marks from a brief — multiple concepts, layouts, and color variations.

    line 8

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

Create SVG

Create professional, scalable SVG logos and visual marks from a brief — multiple concepts, layouts, and color variations.

Core Workflow

Work through these phases in order, reading the matching reference for the depth you need:

  1. Requirements Gathering — collect brand info, design preferences, logo type, style, technical constraints, and number of variations. See references/requirements.md.
  2. Concept Development — develop a primary direction plus alternatives, with design thinking and a base SVG structure. See references/concepts-layouts.md.
  3. Layout Variations — produce horizontal, vertical, square, icon-only, and text-only lockups per concept. See references/concepts-layouts.md.
  4. SVG Generation — write clean, scalable, optimized, accessible SVG code. See references/svg-construction.md.
  5. Presentation — present concepts with rationale, layouts, and color variations. See references/presentation-delivery.md.
  6. File Generation — save each variation with a consistent naming convention. See references/presentation-delivery.md.
  7. Usage Guidelines & Delivery — document usage, clear space, PNG export, web/print specs, and the final package. See references/presentation-delivery.md.

Throughout: choose colors via references/style-color.md, lean on references/examples.md for ready patterns, and iterate per references/process.md.

References

Each file is loaded on demand — read one only when the task needs that depth (progressive disclosure).

  • references/requirements.md — the Phase 1 requirements checklist: brand info, logo types, style guidelines, technical requirements, number of variations · read when starting a logo and gathering what to build.
  • references/concepts-layouts.md — Phase 2–3 concept development (design thinking + base SVG structure) and the five layout lockups · read when developing concepts or producing layout variations.
  • references/svg-construction.md — Phase 4 SVG best practices: semantic code, scalable viewBox, color management, optimization, accessibility · read when writing or optimizing the SVG markup.
  • references/style-color.md — color psychology guide mapping seven color families to meanings, hex values, and industries · read when choosing or justifying a color palette.
  • references/examples.md — ready SVG patterns (wordmark, geometric icon, abstract mark, combination mark) and a full worked example workflow · read when you need a concrete starting template or an end-to-end walkthrough.
  • references/presentation-delivery.md — Phases 5–7 plus deliverables: presentation format, file naming, usage guidelines, clear space, PNG export, web/print specs, file organization · read when presenting, saving files, or documenting usage.
  • references/process.md — the iteration loop and communication style for working with users · read when gathering feedback, refining a concept, or shaping how you talk through choices.

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.

Check your setup, free