signalcanvas-skills

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

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

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

Interactive rig design and import for SignalCanvas: guides users through building signal flow diagrams from conversation, CSV/XLSX patch lists, or screenshots of Visio and handwritten diagrams. Pushes PatchLang to the canvas section-by-section via the MCP server.

Playwright-based VueFlow canvas inspector: extracts node positions, port handles, and edge routes from the live app and detects alignment errors, wire overlaps, node overlaps, and wires routing through nodes.

Automatically logs Claude Code session activity per project. Injects recent history into new sessions so you never re-explain context.

SignalCanvas test automation: run browser trace tests (Playwright), signal flow tests (Vitest), and label scanning on patch files

Builds, edits, and audits device templates in the SignalCanvas stock library (src/data/stdlib/). Covers manufacturer device patterns, channel counts, connector types, port definitions, and the physical-vs-virtual channel boundary.

Enforces the architecture boundary between PatchLang (.patch) and the JSON sidecar (.layout.json) in the SignalCanvas frontend. Use whenever writing or modifying code that touches device data, connections, the canvas scene store, the emitter, the loader, or the sidecar JSON.

SignalCanvas release packaging: cuts a new macOS .pkg installer (version bump, changelog, BETA-README, build) via the /scpkg slash command

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