architecture-wireframes
description (verbatim frontmatter)
CRUD operations on the family's architecture diagram / wireframe set across TWO render targets — Figma/FigJam (via the official Figma MCP server) and, since 2026-07-05, the native Swift `FleetGraphView` in src/coworkers (the coworker-PLUGIN dependency layer: which cwc-* plugin depends on which, generated from plugins/cwc-*/DEPENDENCIES.json into schemas/fleet-graph.json — see schemas/FLEET-GRAPH.md). Use when the user wants an architecture diagram, system visualization, wireframe, or FigJam board created, read back, updated, or retired — "diagram the fleet", "visualize the plugin architecture", "update the architecture board", "screenshot the wireframe", "add the new primitive to the diagram" — or when a Swift change touches FleetGraphView and needs a design-system QA sign-off before it ships (8-token conformance, Liquid Glass conventions, GlassEffectContainer grouping, WCAG contrast) — or pastes a figma.com URL for one of this family's boards. Pairs with cwc-engineering (system facts: workers, crates, schema; also owns fleet-graph-build.py) and cwc-data (warehouse facts) as the sources of what to draw. Do NOT use for the 8-token Hardware Buddy character-pack loop (that's the sibling design-playbook skill), and do NOT invent architecture — every box and edge must be a real worker, plugin, coworker, or API that exists in the repo.
summary
CRUD operations on the family's architecture diagram / wireframe set across TWO render targets — Figma/FigJam (via the official Figma MCP server) and, since 2026-07-05, the native Swift `FleetGraphView` in src/coworkers (the coworker-PLUGIN dependency layer: which cwc-* plugin depends on which, g...
source
plugins/cwc-design/skills/architecture-wireframes/SKILL.md
provenance
created 2026-07-10 18:13:13 · JSON