orchimada
UserA Claude skill for minimalist technical diagrams and explorable explanations — illustration-led technical design distilled into rules + verified interactive examples.
Categories
Indexed Skills (2)
technical-explanatory-minimalism
Create concise, minimalist technical diagrams, schematics, and explanatory illustrations (SVG-first), and design clean minimalist web/interface design systems. Use when the user wants to explain a mechanism or system visually, make an exploded view / cutaway / flow diagram / annotated figure, illustrate how something works, or build a restrained, information-dense UI / design tokens in the style of ciechanow.ski, makingsoftware.com, diode.computer, or mechanical-pencil.com.
judgment-over-velocity
A structured product-judgment engine for deciding what NOT to build — faster. Applies the "spreadsheet test" (discipline problem in a tooling costume, or genuinely needs heavy machinery?), 80/20 structural analysis, figure/ground reading, and an adversarial evidence loop ending in the cheapest disconfirming test. Use whenever a user asks whether to build something, evaluates a feature/product/tool idea, asks "should we buy a tool or fix our process," brings a roadmap or backlog to prioritize, asks how to solve a product-team or CPO-level problem, proposes an AI initiative, or wants a verdict on where to invest effort. Also trigger on "is this worth building," "what should we cut," "help me prioritize," "do we need a tool for this," "evaluate this idea," or any request to assess an identified product opportunity. Trigger even when the user just describes a business problem and asks for a solution — the first move is always classifying the problem before solving it.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.