How do I install the Vite Plugin Svg Icons Ng Workspace skill?

Run npx skillmds@latest add tomevault-io/vite-plugin-svg-icons-ng-workspace in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vite Plugin Svg Icons Ng Workspace safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vite Plugin Svg Icons Ng Workspace?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vite Plugin Svg Icons Ng Workspace free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vite Plugin Svg Icons Ng Workspace?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vite Plugin Svg Icons Ng Workspace by tomevault-io

Name: Vite Plugin Svg Icons Ng Workspace
Author: tomevault-io

Vite Plugin Svg Icons Ng Workspace

Workspace skill for the vite-plugin-svg-icons-ng monorepo. Use when you need repository-level facts such as monorepo structure, package ownership, docs or playground boundaries, release scripts, workspace commands, or cross-package validation before changing code, tests, docs, or release flow. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

vite-plugin-svg-icons-ng-workspace

Scope

Use this skill for workspace-level questions only:

monorepo structure and package boundaries
which package owns which responsibility
docs, playground, scripts, patches responsibilities
root scripts, workspace commands, release flow, and validation entrypoints

Do not use this skill for plugin internals such as scan flow, cache behavior, virtual modules, or HMR details. Use vite-plugin-svg-icons-ng for plugin implementation facts.

Workspace Layout

packages/vite-plugin-svg-icons-ng/: published Vite plugin package.
packages/svg-icon-baker/: internal SVG-to-symbol conversion package used by the plugin.
docs/: VitePress documentation site.
playground/: runnable integration examples and behavior checks.
scripts/: release and maintenance scripts.
patches/: patched upstream dependency files.

Ownership Boundaries

Root package.json: workspace commands, shared tooling, and release entrypoints.
pnpm-workspace.yaml: workspace membership, dependency patching, and overrides.
packages/vite-plugin-svg-icons-ng: Vite-facing runtime integration.
packages/svg-icon-baker: SVG transformation and symbol conversion logic.
docs: user-facing documentation, not runtime source of truth.
playground: integration verification targets, not package source of truth.

Workspace Conventions

Package builds and tests run through pnpm workspace filters.
Cross-package edits should preserve the boundary: plugin orchestrates, baker converts.
If behavior and docs diverge, prefer package source and tests over docs/.
Root validation should cover both package-level correctness and workspace-level regressions.

Validation

pnpm build
pnpm test
pnpm tsc
pnpm build:docs
pnpm build:playground

Gotchas

Do not move plugin internals into this skill; keep implementation detail in the plugin skill.
Do not treat playground or docs as the source of truth for package contracts.
Do not blur package boundaries when changing both vite-plugin-svg-icons-ng and svg-icon-baker.

Source: yangxu52/vite-plugin-svg-icons-ng — distributed by TomeVault.

---name: vite-plugin-svg-icons-ng-workspacedescription: Workspace skill for the vite-plugin-svg-icons-ng monorepo. Use when you need repository-level facts such as monorepo structure, package ownership, docs or playground boundaries, release scripts, workspace commands, or cross-package validation before changing code, tests, docs, or release flow. Use when this capability is needed.---# vite-plugin-svg-icons-ng-workspace## ScopeUse this skill for workspace-level questions only:- monorepo structure and package boundaries- which package owns which responsibility- `docs`, `playground`, `scripts`, `patches` responsibilities- root scripts, workspace commands, release flow, and validation entrypointsDo not use this skill for plugin internals such as scan flow, cache behavior, virtual modules, or HMR details.Use `vite-plugin-svg-icons-ng` for plugin implementation facts.## Workspace Layout- `packages/vite-plugin-svg-icons-ng/`: published Vite plugin package.- `packages/svg-icon-baker/`: internal SVG-to-symbol conversion package used by the plugin.- `docs/`: VitePress documentation site.- `playground/`: runnable integration examples and behavior checks.- `scripts/`: release and maintenance scripts.- `patches/`: patched upstream dependency files.## Ownership Boundaries- Root `package.json`: workspace commands, shared tooling, and release entrypoints.- `pnpm-workspace.yaml`: workspace membership, dependency patching, and overrides.- `packages/vite-plugin-svg-icons-ng`: Vite-facing runtime integration.- `packages/svg-icon-baker`: SVG transformation and symbol conversion logic.- `docs`: user-facing documentation, not runtime source of truth.- `playground`: integration verification targets, not package source of truth.## Workspace Conventions- Package builds and tests run through pnpm workspace filters.- Cross-package edits should preserve the boundary: plugin orchestrates, baker converts.- If behavior and docs diverge, prefer package source and tests over `docs/`.- Root validation should cover both package-level correctness and workspace-level regressions.## Validation- `pnpm build`- `pnpm test`- `pnpm tsc`- `pnpm build:docs`- `pnpm build:playground`## Gotchas- Do not move plugin internals into this skill; keep implementation detail in the plugin skill.- Do not treat `playground` or `docs` as the source of truth for package contracts.- Do not blur package boundaries when changing both `vite-plugin-svg-icons-ng` and `svg-icon-baker`.---> Source: [yangxu52/vite-plugin-svg-icons-ng](https://github.com/yangxu52/vite-plugin-svg-icons-ng) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions