Draw Diagrams Using Agent Skills

Use the excalidraw-diagram-generator skill.

Analyze this repository:
https://github.com/codewalnut-labs/documenso

Create a high-level architecture diagram for Documenso.

Include only components that are actually present in the codebase.

Check the README, `apps/` folder, `packages/` folder, API-related code, Prisma schema, authentication code, background jobs, document/PDF handling, email handling, storage code, and external integrations before drawing.

Show Remix/Hono runtime, app entry points, API routes, domain packages, Prisma/Postgres, auth, jobs, document/PDF handling, email handling, storage, and verified external integrations only if they are present in the repository.

Use clear labels and arrows.

Save the diagram as:
docs/architecture.excalidraw

Use the mermaid-diagrams skill.

Repo: https://github.com/codewalnut-labs/documenso

Create a flowchart for the recipient signing page only.

Scope: open signing link, validate token, load document, fill required fields, submit signature, reject document, complete signing, invalid-token error.

Limit: medium-size diagram, max 10 nodes, max 3 decisions.

Style: Mermaid flowchart, top-to-bottom, light theme, blue steps, green success, red error.

Save: docs/recipient-signing-flow.mmd
Export: docs/recipient-signing-flow.png

Use the drawio skill.

Repo: https://github.com/codewalnut-labs/documenso

Create a Draw.io sequence diagram for the recipient signing submit flow only.

Scope: recipient, signing UI, tRPC recipient router, field signing handler, document completion handler, Prisma.

Limit: medium-size diagram, max 5 participants, max 10 messages.

Style: Draw.io sequence diagram, clean lifelines, white background, muted purple/gray palette, no sketch style.

Save: docs/recipient-signing-sequence.drawio
Export: docs/recipient-signing-sequence.png

Use the baoyu-diagram skill.

Repo: https://github.com/codewalnut-labs/documenso

Create a medium-size ER diagram from packages/prisma/schema.prisma.

Scope: Document or Envelope, Recipient, Field, Signature, DocumentData, and DocumentAuditLog only if directly related.

Limit: medium-size diagram, max 6 entities; show only PK, FK, and 1-2 important fields.

Style: self-contained SVG, database-card layout, teal headers, gray lines, no sketch style.

Save: docs/envelope-recipient-er.svg
Export: docs/envelope-recipient-er.png

Update the existing diagram with current codebase state.

Keep the same module, same style, and same complexity.
Remove stale parts.
Add only verified codebase components.
Do not expand it into the full system.