mcpField
C
creating-svg-illustrations

creating-svg-illustrations

github.com/narumirunaDesign & UI17227 installsUpdated 6d ago
Repository

About creating-svg-illustrations

A workflow skill for creating and validating editable SVG illustrations for slides and documents. It guides authors through layout, accessibility, portability, and renderer checks.

Key features

  1. 01Slide and document inspection
  2. 02Editable SVG construction
  3. 03Accessibility metadata and alt text
  4. 04Portable asset guidance
  5. 05SVG validation and rendering checks

Use cases

  1. 01Create diagrams for presentation slides
  2. 02Embed SVG illustrations in Marp
  3. 03Diagnose SVG rendering issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/narumiruna/skills --skill creating-svg-illustrations

After installing, type/creating-svg-illustrationsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/examples/
with-diagrams.md
references/
core-rules.md
embedding.md
pattern-examples.md
troubleshooting.md

Details

From the project README

SVG Illustrations

Start with references/core-rules.md; load only the extra detail the artifact needs.

NeedRead or use
Canvas, style, text, accessibility, validationreferences/core-rules.md
Reusable compositionsreferences/pattern-examples.md
Marp embeddingreferences/embedding.md
Rendering failuresreferences/troubleshooting.md
Known-good deck exampleassets/examples/with-diagrams.md

Workflow

  1. Inspect the target slide or document, required dimensions, surrounding palette, and renderer.
  2. Create the smallest editable SVG that communicates the idea. Use a correct viewBox, explicit text styles, consistent geometry, and SVG title/description where the visual carries meaning. When embedding, also provide descriptive host-level alt text or an adjacent semantic equivalent as required by references/embedding.md; internal SVG metadata alone is not sufficient.
  3. Keep assets portable: avoid embedded fonts, unexplained emoji, unnecessary filters, and base64 content unless the output must be self-contained.
  4. Validate with svglint when available, then open or embed the SVG in the target artifact and inspect clipping, scaling, contrast, text, and relative paths.
  5. Return the SVG artifact first, followed by validation performed and any renderer or font caveat.

Use slide-authoring or color guidance only when the request also requires it. Do not claim visual inspection when only source validation ran, and do not commit or publish the artifact unless requested.

Comments

Markdown supported