SignalCanvas/signalcanvas-skills

Playwright VueFlow canvas inspector: extracts node/edge/port data from the live app and detects alignment errors, wire overlaps, node overlaps, and routing problems.

SignalCanvas code quality rules: file size, naming, DRY, no magic numbers, trash not rm

Write a HANDOFF.md at the active project root so context can be cleared and resumed cleanly in a fresh session

Enforces the architecture boundary between PatchLang (.patch) and the JSON layout sidecar — use when touching device data, connection types, canvas scene store, emitter, or loader

Per-project Claude Code session log. Injects recent history at session start and nudges Claude to write entries after meaningful work.

Build or import a SignalCanvas rig via MCP — from conversation, CSV/XLSX patch lists, or screenshots. Section-by-section set_patch protocol with spring animation.

Package a new SignalCanvas release via /scpkg — picks branch, bumps version, updates changelog and BETA-README, builds the .pkg installer

PatchLang DSL authoring: syntax, templates, instances, ports, bridges, and validation

SignalCanvas test automation: /scbt (Playwright browser trace), /scpt (Vitest signal flow), /scft (label scanner)

Build, edit, or audit device templates in the SignalCanvas stock library (src/data/stdlib/) — channel counts, connector types, port definitions, card slot templates

Vue 3 + TypeScript best practices: reactivity, SFC structure, composables, provide/inject, Pinia, component decomposition, file-size gates