agentleFS
HashLipsHashLips/agent-skills/skills/vector-drawing/SKILL.md

vector-drawing

Skill29 starsChanged 7 months agoMITView on GitHub

Creates SVG images and vector-based artworks. Use whenever you need to create SVG images, vector graphics, or vector-based artworks instead of raster or bitmap images.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When generating or editing SVG artwork, apply concepts in this order and read the referenced file when you need that topic.

    line 41
  2. Very specific:

    Document structure and svg/viewBox basics: reference/structure.md

    line 43
  3. Very specific:

    Structure first: use path, g, defs clearly.

    line 61
  4. Very specific:

    Accessibility: add <title> and aria-* where meaning is conveyed by the graphic.

    line 63
  5. Distinctive:

    avoid embedding raster images unless explicitly requested

    line 72

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

Vector Drawing

This skill guides creation of vector-based artworks using SVG—scalable, resolution-independent graphics. Apply it when the user asks for SVG output, vector graphics, logos, icons, illustrations, or any artwork that must scale cleanly.

Disclaimer (for the user)

This is an experimental skill; outcomes are not guaranteed. Use at your own risk. For the full disclaimer, see the repository README.

Canonical specification

The official standard is SVG 2 (W3C). Use it as the authority for syntax and behavior; do not copy the spec verbatim into outputs. Build understanding from it and express it as instructions.

  • Specification: https://www.w3.org/TR/SVG2/
  • Key sections: Structure, Basic Shapes, Paths, Painting, Coordinate Systems and Transforms, Clipping and Masking, Gradients and Patterns, Text, Reuse (defs/use).

Core subset for AI-generated artwork

For most vector art, this subset is enough:

  • svg — Root and canvas.
  • viewBox — Coordinate system and aspect ratio.
  • path — Arbitrary shapes and outlines.
  • g — Grouping and inheritance.
  • fill — Interior color or pattern.
  • stroke — Outline color and width.
  • transform — Move, scale, rotate, skew.
  • clipPath — Hard-edged visibility.
  • mask — Soft or gradient visibility.
  • defs — Define reusable content.
  • use — Reuse content by reference.

Master these before reaching for shapes, text, or filters.

Reference Index (skill flow)

When generating or editing SVG artwork, apply concepts in this order and read the referenced file when you need that topic.

  1. Document structure and svg/viewBox basics: reference/structure.md
  2. Basic shapes (rectangles, circles, lines, etc.): reference/shapes.md
  3. Paths and path commands for arbitrary shapes: reference/paths.md
  4. Styling (fill, stroke, painting rules): reference/styling.md
  5. Grouping and hierarchy with g: reference/grouping.md
  6. Transforms and coordinate manipulation (transform): reference/transforms.md
  7. Clipping and masking (clipPath, mask): reference/clipping-masking.md
  8. Gradients and patterns: reference/gradients.md
  9. Composition, reuse, and defs/use: reference/composition.md

When to use

  • User asks for SVG, vector graphics, or scalable artwork
  • Task is logos, icons, illustrations, diagrams, or print-ready art
  • Output must stay sharp at any size or resolution

Quick principles

  • Structure first: use path, g, defs clearly; keep markup readable.
  • Prefer the core subset unless the design needs text, filters, or advanced features.
  • Accessibility: add <title> and aria-* where meaning is conveyed by the graphic.

Output Contract

SVG outputs produced with this skill should:

  • render correctly as valid SVG 2 markup
  • be structurally readable (clear grouping, paths, and viewBox usage)
  • rely on the core subset of elements unless advanced features are clearly needed
  • avoid embedding raster images unless explicitly requested

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.