hashintel/shaping-breadboard-reflect
pocs/agent-plugins/claude-pragma/skills/shaping-breadboard-reflect/SKILL.md
Reflect on an existing breadboard by syncing it to code and surfacing structural smells before planning the next slice or refactor.
$ install --global
skillsauthnpx skillsauth add hashintel/labs shaping-breadboard-reflectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 15, 2026, 3:09 AM192.1s1 file scanned
SKILL.md
- name:
- shaping-breadboard-reflect
- description:
- Reflect on an existing breadboard by syncing it to code and surfacing structural smells before planning the next slice or refactor.
- argument-hint:
- [breadboard artifact and relevant code paths]
Shape Breadboard Reflection (Adjunct)
Use this adjunct skill to reconcile breadboard artifacts with implementation reality, then identify design smells that affect planning.
Source And Adaptation Note
Adopted from rjs/shaping-skills (breadboard-reflection) and adapted for this repository.
Modifications:
- Namespaced as
pragma:shaping-* - Added compatibility with
characterizesafety gate - Added mandatory pragma re-entry instructions
Procedure
- Sync the breadboard to current code first.
- Identify mismatches, missing nodes, and stale wires.
- Run smell checks on naming, boundaries, and causality.
- Classify findings as planning fixes vs. risky behavior changes.
- Route to the right pragma next step.
Required Output
## Reflection Findings
- Sync fixes: [breadboard updates required]
- Smells: [specific boundary/name/wiring issues]
## Handoff To Pragma
- Safe planning follow-up: [`/pragma:card` or `/pragma:refactor`]
- Behavior uncertainty gate: [use `/pragma:characterize` before refactor when behavior is unclear]
- Next command: [single recommended pragma command]
Constraints
- Do not refactor blindly when behavior is not yet characterized.
- If behavior is uncertain, route to
/pragma:characterizefirst. - Do not bypass carding for new behavior.
Lifecycle
- State:
stabilizing - Next:
/pragma:consult(or/pragma:characterizewhen required) - Loop:
/pragma:consult
Related Skills
hashintel/petrinaut
documentation
VerifiedTrustedCommunity
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.
34SKILL.mdUpdated May 15, 2026
hashintel/spike
development
VerifiedTrustedCommunity
Time-boxed throwaway investigation to answer one hard question. Use when facing technical uncertainty before a slice — the output is knowledge, not production code. Retires risk by producing a spike verdict with clear recommendations.
34SKILL.mdUpdated May 15, 2026
hashintel/slice
development
VerifiedTrustedCommunity
Implement one tracer-bullet slice following the inside-out methodology. Use when you have a tracer-bullet card ready to build. Implements functional core first, then imperative shell, then end-to-end wiring, then alignment refactor.
34SKILL.mdUpdated May 15, 2026
hashintel/skeleton
tools
VerifiedTrustedCommunity
Build a walking skeleton — the thinnest runnable system that proves build, test, and runtime work end-to-end. Use when starting a new project, before any feature work. Front-loads tooling and infrastructure so every subsequent slice is cheaper.
34SKILL.mdUpdated May 15, 2026