Agent skill · software engineering · jeremylongshore
documenso-reference-architecture
Implement Documenso reference architecture with best-practice project
Why this skill is useful
Provides a detailed project structure and best practices for integrating with the Documenso SDK that the AI wouldn't reliably generate on its own.
What it needs
Requires docker installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Documenso Reference Architecture Instructions 1. Map document producers, templates, recipients, signing actions, audit records, webhooks, and retention boundaries to named owners. 2. Enforce least-privilege identity and separate development/staging/production workspaces and credentials. 3. Define idempotent lifecycle transitions, signed callbacks, redacted observability, and a rollback/incident path before production exposure. 4. Review architecture changes through normal security, data, and change-control processes. Output A documented document/signing architecture with trust boundaries, ownership, and reversible integration points. Examples Route a synthetic development document through a scoped service identity, role-limited signer, validated webhook, and redacted audit metric. Promote the same versioned workflow through staging before a production canary; preserve a disabled/rollback path and do not include document URLs or signer identity in diagrams or logs. Overview Production-ready architecture for Documenso document signing integrations. Covers project layout, layered service architecture, webhook processing, and data flow. Prerequisites Understanding of layered architecture principles Documenso SDK knowledge (see documenso-sdk-patterns) TypeScript project with Node.js 18+ Recommended Project Structure Layer Architecture Rules: Controllers never call Documenso directly -- always go through services Services never import @documenso/sdk-typescript directly -- use the client wrapper Webhook processors are isolated -- one file per event type Error handling happens at the client layer, not in controllers Data Flow Setup Script Key Design Decisions Decision Rationale ---------- ----------- Singleton client Avoids re-initialization overhead per request Service layer Separates business logic from API details One processor per webhook event Isolates side effects, easy to test Mock client for tests Fast unit tests without API calls Template-first approach Fewer API c …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/documenso-reference-architecture