Svg create

Install

npx -y skills add alavten/svg-create

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Creates valid standalone .svg files: dark minimal diagrams, structural architecture diagrams (knowledge and engineering types), flowcharts, and node graphs. Use for SVG, vector diagrams, .svg edits, or embeddable graphics.

SKILL.md

4.6 KB, as published. Nobody here has run it

SVG Create

Purpose

Produce valid standalone .svg files: explicit viewBox, semantic XML structure, crisp vectors, dark minimal styling.

In scope: .svg create, edit, restyle; six structural diagram types. Out of scope: React/TSX, React Flow, HTML canvas, CSS-only graphics, animated web UI.

Quick Start

Structural diagram:

Classify type → structural-spec.md
Model nodes/edges → knowledge-diagrams.md or engineering-diagrams.md
Layout ID → layouts.md
Tokens → tokens.md
Implement → quality.md; check checklists.md L1 → L0

Generic SVG: nodes from user → layouts.md graph-shape matrix → tokens.md + quality.md.

Structural diagram types

Family	Type	Spec
Knowledge	Concept Tree	knowledge-diagrams.md#concept-tree
Knowledge	Capability Map	knowledge-diagrams.md#capability-map
Knowledge	Learning Path	knowledge-diagrams.md#learning-path
Knowledge	Domain Model	knowledge-diagrams.md#domain-model
Engineering	Module Dependency	engineering-diagrams.md#module-dependency
Engineering	Data Flow	engineering-diagrams.md#data-flow
Engineering	C4 Level 2 Container	engineering-diagrams.md#c4-level-2-container

Cross-type rules and glossary: structural-spec.md.

Intent matrix

User intent	Action	Reference
Concept taxonomy	structural	Concept Tree
Business capabilities	structural	Capability Map
Curriculum / onboarding	structural	Learning Path
DDD domain structure	structural	Domain Model
Module depends-on	structural	Module Dependency
Logical data movement	structural	Data Flow
C4 containers	structural	C4 L2
Generic flowchart / graph	generic	layouts + tokens + quality
edit / restyle	edit	Preserve topology, `viewBox`, `id`s
recolor only	edit	`fill`/`stroke` only

Guardrails

Well-formed SVG (xmlns, viewBox).
Do not add nodes/edges user did not imply.
On edit, preserve geometry unless restructure requested.
No HTML/React wrappers.
Structural: one type per file (SD-S-005); no mixed knowledge/engineering roles (SD-S-004) unless user requests derived view.
Closed node/edge enums only.

Workflow

- [ ] 1. Structural type or generic
- [ ] 2. List node/edge roles (structural: from type spec)
- [ ] 3. Layout ID from layouts.md matrix
- [ ] 4. viewBox + tokens
- [ ] 5. Draw; legend if required
- [ ] 6. checklists L1 → quality L0 → deliver

SOP: structural-spec.md § Seven-step SOP.

Validation

quality.md § L0
Structural: checklists.md L1 + L0-S items

Delivery format

Files — .svg path(s)
Diagram type — six types or generic
Structure — node/edge summary with roles
Layout — layout ID
Rule IDs — satisfied; exceptions noted
Checklists — L0, L1 (structural), L2 if applicable
Deviations — token overrides

References

File	Role
structural-spec.md	Selection, SOP, boundaries, glossary
knowledge-diagrams.md	4 knowledge types
engineering-diagrams.md	3 engineering types
checklists.md	L1, L2; L0 → quality
layouts.md	Layout IDs + type matrix
tokens.md	Visual + semantic bindings
quality.md	L0 markup