$ recombobulate _
home / tips / ask-claude-to-generate-mermaid-diagrams-that-visualize-your-codes-architecture
91

Ask Claude to Generate Mermaid Diagrams That Visualize Your Code's Architecture

recombobulate @recombobulate · Mar 30, 2026 · Workflows
ask-claude-to-generate-mermaid-diagrams-that-visualize-your-codes-architecture

Sometimes you need to see how your code fits together — for documentation, onboarding, or just understanding a complex flow. Claude can read your actual codebase and generate Mermaid diagrams that render anywhere markdown is supported.

> read the auth system and generate a sequence diagram showing the login flow

Claude traces through your controllers, middleware, services, and models, then outputs something like:

sequenceDiagram
    User->>LoginController: POST /login
    LoginController->>AuthService: attempt(credentials)
    AuthService->>UserRepository: findByEmail(email)
    UserRepository->>Database: SELECT * FROM users
    Database-->>UserRepository: User record
    AuthService->>AuthService: verifyPassword()
    AuthService-->>LoginController: AuthResult
    LoginController-->>User: Redirect + session

You can ask for different diagram types depending on what you need to understand:

> draw a class diagram of the models in app/Models and their relationships

> create a flowchart showing how an order moves through statuses

> generate an ER diagram from my migrations

> draw the request lifecycle through middleware, controller, and service layers

Mermaid diagrams render natively in GitHub READMEs, GitLab, Notion, and most documentation tools — so you can paste Claude's output directly into your docs and it just works.

This is especially powerful for:

  • Onboarding docs — show new developers how the system works visually
  • Architecture reviews — visualize module dependencies before refactoring
  • PR descriptions — add a diagram showing how a new feature's components connect
  • Database documentation — auto-generate ER diagrams from your actual schema

Ask Claude to update the diagrams whenever the code changes — keeping docs in sync with reality instead of letting them drift.

A picture of your architecture is worth a thousand lines of code — let Claude draw it from the source.

via Claude Code

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 day ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 day ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 day ago