Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/documenso-reference-architecture
Implement Documenso reference architecture with best-practice project layout.
Passed 21 of 22 test cases with the skill, and 15 of 22 without it.
and 3 more in the full report
6 fixed15 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are building a new TypeScript backend to handle digital contract signing with Documenso. Could you outline a clean reference architecture for this system? I need a recommended project directory layout that separates the SDK wrapper, business services, and webhook event handlers, along with guidelines for layered data flow and controller restrictions.
| Checked | Without skill | With skill |
|---|---|---|
| Maps document producers, templates, recipients, signing actions, audit records, webhooks, and retention boundaries to named owners. | Missed | Passed |
| Requires API controllers to route requests through the service layer rather than calling the SDK directly. | Passed | Passed |
| Organizes webhook processors into individual event-specific files. | Passed | Passed |
The instructions your model reads when the skill loads.
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.
Production-ready architecture for Documenso document signing integrations. Covers project layout, layered service architecture, webhook processing, and data flow.
documenso-sdk-patterns)my-signing-app/
├── src/
│ ├── documenso/
│ │ ├── client.ts # Singleton SDK client
│ │ ├── errors.ts # Custom error classes
│ │ ├── retry.ts # Retry/backoff logic
│ │ └── types.ts # Shared types
│ ├── services/
│ │ ├── document-service.ts # Document CRUD operations
│ │ ├── template-service.ts # Template-based workflows
test cases passed, vs 15 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.