DEDUPED We read 1,000+ AI sources. You read one email. Subscribe free

AI USE CASES

How to draw the plan before your agent writes the code with diagram-design

Ask for a flow or sequence diagram of a proposed change and approve the design first.

Seen in the wild

Evidence: Reddit

Similar to what people reported. The steps and prompt below are AI written, not copied from those posts.

Who it is forDeveloper about to hand a multi-step feature to a coding agent who wants to catch design mistakes early

The problemAgents start coding from a vague plan and the wrong design only shows up after many files change.

The outcomeA sequence or flow diagram of the planned change that you read, correct and approve before any code is written.

What you need first

  • An Agent Skills compatible host such as Claude Code, Codex, Cursor, Qoder, GitHub Copilot, Gemini CLI, Cline, Windsurf or Amp
  • Node.js for the npx install command
  • A browser to open the generated HTML file
  • Optional: a public website URL for brand onboarding

Steps

  1. Install the skill with: npx skills add cathrynlavery/diagram-design
  2. Describe the feature, for example: Give me a sequence of a bearer call with token refresh on 401.
  3. Read the diagram and fix any wrong step by telling the agent what to change.
  4. Once the diagram matches your intent, ask the agent to implement it.

Prompt for your agent

Before writing code for <feature>, use the diagram-design skill to draw the planned flow as one HTML diagram. Wait for my approval of the diagram, and flag any step where you made an assumption.

Caveat. The diagram only helps if you actually read it before the agent continues. Tell the agent explicitly to stop and wait for approval.

About diagram-design

An agent skill that draws clean diagrams as a single HTML and SVG file in your brand. Part of this week's top 10 repos: ranked #8 on Repo Radar. View cathrynlavery/diagram-design on GitHub.

More with diagram-design

See all use cases for cathrynlavery/diagram-design

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page