skills.rest
iancleary
ianclearyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Breadboard Analysis

Analyze breadboard diagrams to detect design smells and wiring inconsistencies.

1|Updated Jan 17, 2026
Search Tags:#debugging#design analysis#code implementation#breadboard#affordances#workflow refinement
One-click install
npx skills add https://github.com/iancleary/dotfiles --skill breadboard-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Breadboard Analysis
Source: https://github.com/iancleary/dotfiles/tree/main/.claude/skills/breadboard-reflection
Command: npx skills add https://github.com/iancleary/dotfiles --skill breadboard-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and fix inconsistencies, redundancies, and logical flaws within your breadboard designs, ensuring they accurately reflect your intended workflows and code.

Core Features & Use Cases

  • Smell Detection: Identifies common issues like incoherent wiring, missing paths, diagram-only nodes, naming resistance, stale affordances, wrong causality, and implementation mismatches.
  • Affordance Naming: Guides you through the "Naming Test" to ensure each affordance is named with a single, idiomatic verb from the caller's perspective.
  • Fixing Wiring: Provides a systematic approach to correcting causality errors by comparing the breadboard diagram to the actual code implementation.
  • Use Case: You've built a complex breadboard for a new feature, but the implemented logic doesn't behave as expected. Use this Skill to trace user stories through the wiring, identify where the breadboard deviates from the code's logic, and correct the design.

Quick Start

Use the breadboard reflection skill to find design smells in the attached breadboard diagram.

Frequently Asked Questions about Breadboard Analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug wiring inconsistencies in my breadboard design?▼

Debugging wiring inconsistencies involves analyzing your breadboard diagram against the actual code implementation to identify incoherent wiring, missing paths, and wrong causality, then systematically rectifying these design smells.

What is the Naming Test for affordance naming conventions?▼

The Naming Test for affordance naming conventions ensures each affordance is named with a single, idiomatic verb from the caller's perspective, preventing naming resistance and improving workflow clarity.

How do I fix implementation mismatches between my breadboard and code?▼

Fixing implementation mismatches requires comparing your breadboard diagram to the actual code implementation to trace user stories through the wiring, identify where the breadboard deviates from the code's logic, and correct the design.

What are common design smells in complex breadboard workflows?▼

Common design smells in complex breadboard workflows include incoherent wiring, missing paths, diagram-only nodes, naming resistance, stale affordances, wrong causality, and implementation mismatches.

When should I analyze my breadboard for design smells?▼

You should analyze your breadboard for design smells when you have built a complex breadboard for a new feature but the implemented logic does not behave as expected, requiring you to trace user stories through the wiring.

Related Skills

Explore More Software Engineering Skills→
CygnusfearCygnusfear
5

file-name-wizard

Audit filenames and naming conventions against CLAUDE.md standards.

Community
Basic
igor1309igor1309

doc-drift-audit

Detect factual mismatches between markdown documentation and code in a repository.

Community
Advanced
IvcotaIvcota
2

bear-hunter-system

Generate a causal GRINDE map with a Mermaid diagram from complex material.

Community
Advanced
ricardoquesadaricardoquesada
163

code-review

Review code changes for bugs, style inconsistencies, and best practices.

Community
Intermediate