From harness-engineering
Map a system into Places, UI affordances, Code affordances, and wiring. Use to map existing systems or design new ones from shaped parts.
How this command is triggered — by the user, by Claude, or both
Slash command
/harness-engineering:breadboardingThe summary Claude sees in its command listing — used to decide when to auto-load this command
Read the shaping skill, then read the full breadboarding reference at the skill's `references/breadboarding.md`. You MUST read the entire reference file before proceeding. Do NOT skip or skim — breadboarding has specific table formats, wiring conventions, Place rules, and visualization standards that must be followed exactly. The reference is long (~1650 lines) because precision matters here. After reading, begin breadboarding: - Write breadboard output to `docs/plan-details/<slug>/slices.md` (with `shaping: true` frontmatter) - If the details directory doesn't exist yet, create it and a ...
Read the shaping skill, then read the full breadboarding reference at the skill's references/breadboarding.md.
You MUST read the entire reference file before proceeding. Do NOT skip or skim — breadboarding has specific table formats, wiring conventions, Place rules, and visualization standards that must be followed exactly. The reference is long (~1650 lines) because precision matters here.
After reading, begin breadboarding:
docs/plan-details/<slug>/slices.md (with shaping: true frontmatter)docs/plans/npx claudepluginhub lattice-technologies-inc/harness-engineering --plugin harness-engineering/sysdesign-explainWalks through a system design problem step-by-step — requirements, estimation, architecture, API, storage, deep dives — rendering the architecture on an Excalidraw canvas or as structured markdown.
/designGenerates technical design document from requirements (topic or path), with architecture diagrams, components, data models, error handling. Investigates codebase, creates frontend mockups if needed, saves to .claude/specs/{topic}/design.md
/designDesigns system architecture, APIs, component interfaces, and technical specifications. Supports architecture, API, component, database types and diagram, spec, code formats.
/brainstormBrainstorms high-level architecture options collaboratively with diagrams and package research to create an implementation plan.
/brainstormingExplores requirements and design options before implementing features, components, functionality, or behavior changes.