メニュー
Build affordance and wiring maps for existing or proposed systems before carding. Use when implementation planning needs a concrete mechanism view across UI and code boundaries.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Read and write a Petri net (SDCPN) document by Automerge URL. Use when creating, editing, or querying Petri nets — adding or removing places, transitions, arcs, color types, differential equations, and parameters.
Create and maintain an Assumption Ledger — a persistent record of assumptions, their confidence, and validation status. Use when starting a new slice, resuming work in a new context window, or when implicit assumptions risk causing drift. Tracks requirements, architecture, and implementation assumptions.
Create or update a concept capsule — the conceptual anchor for a project or feature area. Use before writing code on a new project or feature, or when terms and boundaries feel unclear. Defines glossary, invariants, happy-path scenario, and non-goals.
Write a tracer-bullet card — a precise specification for one thin end-to-end slice of work. Use when scoping a new slice, defining what to build next, or breaking a feature into provable increments. Covers target behavior, boundary crossings, risks, and definition of done.
Create characterization tests (Golden Master) for existing code so you can refactor or replace safely. Use before refactoring, strangler-replacing, or modifying code with unclear behavior. Captures observable behavior with a minimal harness, producing tests, fixtures, and a coverage report.
Methodology triage consultant for tracer-bullet development. Use when unsure which pragma skill to run next, when starting a new project, or when the current approach feels stuck. Interviews the user, assesses state, and recommends the next pragma skill.
| name | shaping-breadboard |
| description | Build affordance and wiring maps for existing or proposed systems before carding. Use when implementation planning needs a concrete mechanism view across UI and code boundaries. |
| argument-hint | [workflow or shaped direction to map] |
Map system behavior using affordance tables and wiring so the next card is grounded in concrete mechanism understanding.
Adopted from rjs/shaping-skills (breadboarding) and adapted for this repository.
Modifications:
pragma:shaping-*## Breadboard
- Places table
- UI affordances table
- Code affordances table
- Data stores table
## Handoff To Pragma
- Candidate cards: [vertical behaviors ready to card]
- Capsule impacts: [new terms or invariants discovered]
- Open uncertainty: [items requiring `/pragma:spike`]
- Next command: [`/pragma:card`]
/pragma:slice.planning/pragma:card/pragma:consult