arbe-diagram-first

Draws a 5-10 line ASCII pipeline of the user's verb before writing prose or code.

Updated May 16, 2026
One-click install
npx skills add https://github.com/oskarrough/robots --skill arbe-diagram-first-oskarrough
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arbe-diagram-first
Source: https://github.com/oskarrough/robots/tree/main/skills/diagram-first
Command: npx skills add https://github.com/oskarrough/robots --skill arbe-diagram-first-oskarrough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Detailed specs and design asks often bake in the wrong structure because the author is too close to existing code. This Skill forces a verb-first ASCII pipeline diagram before any prose or code, so the shape of a design gets challenged while it is still cheap to change. ## Core Features & Use Cases - Verb-first diagramming: Pins the user's core action and renders it as a 5-10 line tree-shaped ASCII pipeline, with branches instead of parallel copies when surfaces share one backend flow. - Noun audit: Lists the nouns under the diagram and flags duplicate names or implementation-flavored naming that hides user intent. - Forced pause: Ends with a concrete claim or proposal and stops, waiting for the user's reaction before continuing. - Use Case: A user pastes a multi-paragraph feature spec and asks how it should be structured; the Skill responds with a compact pipeline diagram, a noun list, and one pointed claim, then waits for agreement before designing further. ## Quick Start Ask the assistant to diagram the core verb of your pasted design spec as a short ASCII pipeline before discussing any implementation details.

Frequently Asked Questions about arbe-diagram-first

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

FAQPage Schema
How do I validate a software design before writing code?▼

Draw a short ASCII pipeline of the user's core verb first, then stop and wait for agreement. This Skill renders a 5-10 line tree diagram, lists the nouns involved, and ends with one claim or proposal so the shape can be challenged before implementation begins.

What is a verb-first architecture diagram?▼

A verb-first diagram starts from what the user is trying to do rather than module or route names. The first line states the user's goal, and branches show shared backend flows instead of parallel copies for each surface.

When should I not use a diagram-first design approach?▼

Skip it for bug reports, UX complaints, user frustration that is not a design ask, tiny single-file fixes, and features whose verb is already pinned. It targets explicit structure or architecture questions only.

How do I handle multiple UI surfaces sharing one backend flow?▼

Show one pipeline with branches rather than parallel copies of the same flow. Drawing duplicate pipelines per surface is an explicit anti-pattern because it hides the shared verb and invites divergent implementations.

Why does the skill stop after drawing the diagram?▼

The pause is the point: it gives the user a chance to reject or reshape the structure before prose or code locks it in. The diagram closes with a claim or proposal so the user has something concrete to push against.