Ki stack symbols

Skill Milind220/Ki-Stack/skills/ki-stack/ki-stack-symbols

Deep KiCad skills for coding agents

Install

npx -y skills add Milind220/Ki-Stack --skill ki-stack-symbols

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

One thing to look at

6 stars6 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

Symbol-focused KiCad workflows built on top of the Phase 1 substrate skills. Use when the task is about symbol libraries, symbol inspection, symbol rendering, or proving symbol-side changes with deterministic exports.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.3 KB, as published. Nobody here has run it

ki-stack-symbols

Purpose

This Phase 2 domain skill orchestrates symbol-focused work by composing:

ki-stack-render
ki-stack-file-surgery
ki-stack-verify

Use it when the user's intent is specifically about symbols or symbol libraries.

What it covers

symbol rendering
symbol library inspection
symbol-side offline edits and regeneration workflows
symbol verification through exports

Routing rules

Use `ki-stack-render` when

the user wants to inspect or compare a symbol visually
the task is to export symbol artifacts

Use `ki-stack-file-surgery` when

the symbol task is a deterministic library or file transform
preserving file structure and tokens matters

Use `ki-stack-verify` after

any symbol edit that should be proven visually

Phase 1: Orient

Confirm the task is symbol-scoped.
Identify the .kicad_sym file and exact symbol name.
If the symbol name is missing, stop and ask for it or search the library contents first.

Phase 2: Inspect

The most useful first step is usually rendering the target symbol.

Canonical command:

skills/ki-stack/bin/kicad-render symbol-svg library.kicad_sym out_dir --symbol Device:R

If the task is an offline edit, inspect the relevant library files before mutation.

Phase 3: Execute

For symbol work in v1, prefer deterministic offline workflows over speculative live APIs.

Common execution path:

identify the symbol library file
render the baseline symbol
apply the symbol-side change offline
render the symbol again
report before/after artifacts

Phase 4: Verify

The main proof for symbol tasks is visual and export-based.

Prefer:

render before
change symbol
render after
report both artifact paths

If the task affects downstream library behavior, note any limits in verification.

Common symbol workflows

Workflow: inspect a symbol visually

render the symbol as SVG
convert to PNG if a raster artifact is needed
report the artifact path

Workflow: verify a symbol edit

render before
apply edit
render after
report the before/after paths and any file-level transform used

Helper assets

Skills to compose:

skills/ki-stack/ki-stack-render/SKILL.md
skills/ki-stack/ki-stack-file-surgery/SKILL.md
skills/ki-stack/ki-stack-verify/SKILL.md

References:

skills/ki-stack/references/render-recipes.md

Helpers:

skills/ki-stack/bin/kicad-render
skills/ki-stack/bin/kicad-svg-to-png

Guardrails

Do not assume a symbol name if the user did not specify one.
Prefer export-based proof over prose description.
If the task is really about footprints or schematics, route to those skills.

Completion states

DONE: symbol task completed and visually verified
DONE_WITH_CONCERNS: completed but verification is partial
BLOCKED: file, symbol name, or tooling issue prevented completion
NEEDS_CONTEXT: symbol library path or symbol identifier is missing