breadboardingTransform a workflow description into affordance tables showing UI and Code affordances with their wiring. Use to map existing systems or design new ones fro...
Install via ClawdBot CLI:
clawdbot install morpheis/breadboardingGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 23, 2026
Use breadboarding to reverse-engineer an existing customer onboarding system. By analyzing the codebase and operator workflows, create affordance tables that reveal hidden dependencies and UI flow.
When shaping a new payment mechanism, use breadboarding to detail how UI affordances like 'Pay Now' button and code affordances like 'Charge API' interact, ensuring clear wiring and data flow.
Breadboard the existing login workflow and the new OAuth provider as shaped parts. Map both affordance tables together to show how UI login and token exchange wire across systems.
Use breadboarding to create affordance tables for a legacy ERP's order-to-cash process. This provides a shared understanding for the team before refactoring into microservices.
Before coding, breadboard a multi-step form where user inputs affect subsequent fields. Tables capture place navigation, conditional branches, and data dependencies across steps.
Offer breadboarding as a service to map and document internal workflows within organizations, reducing knowledge silos and onboarding time.
Build a collaborative platform where teams can create Breadboard-style affordance tables and diagrams, with integrations to code repos and issue trackers.
Embed breadboarding into design sprints for product teams to rapidly translate shaped parts into concrete interaction specs, reducing handoff friction.
💬 Integration Tip
Start by creating affordance tables for a single workflow that spans UI and backend. Use the 'Blocking Test' to identify places, and ensure every arrow has a clear origin and destination in the tables.
Scored May 23, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.