[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ZHK35185SWQ58917K279V":3,"skill-same:01M78ZHK35185SWQ58917K279V":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M78ZHK35185SWQ58917K279V","documenso-reference-architecture",null,"Implement Documenso reference architecture with best-practice project layout.\nUse when designing new Documenso integrations, reviewing project structure,\nor establishing architecture standards for document signing applications.\nTrigger with phrases like \"documenso architecture\", \"documenso best practices\",\n\"documenso project structure\", \"how to organize documenso\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--documenso-pack--documenso-reference-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: documenso-reference-architecture\ndescription: |\n  Implement Documenso reference architecture with best-practice project layout.\n  Use when designing new Documenso integrations, reviewing project structure,\n  or establishing architecture standards for document signing applications.\n  Trigger with phrases like \"documenso architecture\", \"documenso best practices\",\n  \"documenso project structure\", \"how to organize documenso\".\nallowed-tools: Read, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, documenso, documenso-reference]\n---\n# Documenso Reference Architecture\n\n## Overview\n\nProduction-ready architecture for Documenso document signing integrations. Covers project layout, layered service architecture, webhook processing, and data flow.\n\n## Prerequisites\n\n- Understanding of layered architecture principles\n- Documenso SDK knowledge (see `documenso-sdk-patterns`)\n- TypeScript project with Node.js 18+\n\n## Recommended Project Structure\n\n```\nmy-signing-app\u002F\n├── src\u002F\n│   ├── documenso\u002F\n│   │   ├── client.ts              # Singleton SDK client\n│   │   ├── errors.ts              # Custom error classes\n│   │   ├── retry.ts               # Retry\u002Fbackoff logic\n│   │   └── types.ts               # Shared types\n│   ├── services\u002F\n│   │   ├── document-service.ts    # Document CRUD operations\n│   │   ├── template-service.ts    # Template-based workflows\n│   │   └── signing-service.ts     # Orchestrates signing flows\n│   ├── webhooks\u002F\n│   │   ├── handler.ts             # Express webhook router\n│   │   ├── verify.ts              # Secret verification\n│   │   └── processors\u002F\n│   │       ├── document-completed.ts\n│   │       ├── document-signed.ts\n│   │       └── document-rejected.ts\n│   ├── api\u002F\n│   │   ├── health.ts              # Health check endpoint\n│   │   └── routes.ts              # API routes\n│   └── config\u002F\n│       └── index.ts               # Environment configuration\n├── scripts\u002F\n│   ├── verify-connection.ts       # Quick health check\n│   ├── create-test-doc.ts         # Test document generator\n│   └── cleanup-test-docs.ts       # Test data cleanup\n├── tests\u002F\n│   ├── unit\u002F\n│   │   └── document-service.test.ts\n│   ├── integration\u002F\n│   │   └── document-lifecycle.test.ts\n│   └── mocks\u002F\n│       └── documenso.ts           # Mock client factory\n├── .env.development\n├── .env.production\n├── docker-compose.yml             # Self-hosted Documenso (dev)\n└── package.json\n```\n\n## Layer Architecture\n\n```\n┌─────────────────────────────────────────────────────────┐\n│  API \u002F Controllers                                       │\n│  Routes, request validation, response formatting         │\n├─────────────────────────────────────────────────────────┤\n│  Service Layer                                           │\n│  Business logic, orchestration, authorization            │\n│  (document-service, template-service, signing-service)   │\n├─────────────────────────────────────────────────────────┤\n│  Documenso Client Layer                                  │\n│  SDK wrapper, retry, error handling, caching             │\n│  (client.ts, retry.ts, errors.ts)                       │\n├─────────────────────────────────────────────────────────┤\n│  External Services                                       │\n│  Documenso API, S3\u002FGCS storage, email, database         │\n└─────────────────────────────────────────────────────────┘\n```\n\n**Rules:**\n- Controllers never call Documenso directly -- always go through services\n- Services never import `@documenso\u002Fsdk-typescript` directly -- use the client wrapper\n- Webhook processors are isolated -- one file per event type\n- Error handling happens at the client layer, not in controllers\n\n## Data Flow\n\n```\nUser Request\n     │\n     ▼\n┌──────────┐   POST \u002Fapi\u002Fsign\n│   API    │──────────────────────────────┐\n│  Router  │                              │\n└──────────┘                              ▼\n                                   ┌──────────────┐\n                                   │   Signing    │\n                                   │   Service    │\n                                   └──────┬───────┘\n                                          │\n                    ┌─────────────────────┼─────────────────────┐\n                    ▼                     ▼                     ▼\n             ┌──────────┐         ┌──────────┐          ┌──────────┐\n             │ Template │         │ Document │          │   Your   │\n             │ Service  │         │ Service  │          │    DB    │\n             └────┬─────┘         └────┬─────┘          └──────────┘\n                  │                    │\n                  └────────┬───────────┘\n                           ▼\n                    ┌──────────────┐\n                    │  Documenso   │\n                    │  Client      │──→ Documenso API\n                    │  (singleton) │\n                    └──────────────┘\n\nWebhook Flow:\nDocumenso API ──POST──→ \u002Fwebhooks\u002Fdocumenso\n                             │\n                        ┌────▼────┐\n                        │ Verify  │──→ Check X-Documenso-Secret\n                        │ Secret  │\n                        └────┬────┘\n                             │\n                        ┌────▼────┐\n                        │ Router  │──→ Route by event type\n                        └────┬────┘\n                             │\n              ┌──────────────┼──────────────┐\n              ▼              ▼              ▼\n        completed.ts    signed.ts     rejected.ts\n        (archive PDF)  (update DB)  (alert sender)\n```\n\n## Setup Script\n\n```bash\n#!\u002Fbin\u002Fbash\nset -euo pipefail\n\nmkdir -p src\u002F{documenso,services,webhooks\u002Fprocessors,api,config}\nmkdir -p scripts tests\u002F{unit,integration,mocks}\n\n# Create .env.example\ncat > .env.example \u003C\u003C 'EOF'\nDOCUMENSO_API_KEY=\nDOCUMENSO_BASE_URL=https:\u002F\u002Fapp.documenso.com\u002Fapi\u002Fv2\nDOCUMENSO_WEBHOOK_SECRET=\nLOG_LEVEL=info\nNODE_ENV=development\nEOF\n\necho \"Project scaffolded. Copy .env.example to .env and fill in values.\"\n```\n\n## Key Design Decisions\n\n| Decision | Rationale |\n|----------|-----------|\n| Singleton client | Avoids re-initialization overhead per request |\n| Service layer | Separates business logic from API details |\n| One processor per webhook event | Isolates side effects, easy to test |\n| Mock client for tests | Fast unit tests without API calls |\n| Template-first approach | Fewer API calls, consistent field placement |\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Circular dependencies | Wrong layering | Services import client, never the reverse |\n| Config not loading | Wrong env file | Verify `NODE_ENV` matches config loader |\n| Webhook processor crash | Unhandled error in processor | Wrap each processor in try\u002Fcatch |\n| Test isolation | Shared client state | Call `resetClient()` in `beforeEach` |\n\n## Resources\n\n- [Clean Architecture](https:\u002F\u002Fblog.cleancoder.com\u002Funcle-bob\u002F2012\u002F08\u002F13\u002Fthe-clean-architecture.html)\n- [Documenso SDK](https:\u002F\u002Fgithub.com\u002Fdocumenso\u002Fsdk-typescript)\n- [12-Factor App](https:\u002F\u002F12factor.net\u002F)\n\n## Next Steps\n\nFor multi-environment setup, see `documenso-multi-env-setup`.\n","# Documenso Reference Architecture\n\n## Overview\n\nProduction-ready architecture for Documenso document signing integrations. Covers project layout, layered service architecture, webhook processing, and data flow.\n\n## Prerequisites\n\n- Understanding of layered architecture principles\n- Documenso SDK knowledge (see `documenso-sdk-patterns`)\n- TypeScript project with Node.js 18+\n\n## Recommended Project Structure\n\n```\nmy-signing-app\u002F\n├── src\u002F\n│   ├── documenso\u002F\n│   │   ├── client.ts              # Singleton SDK client\n│   │   ├── errors.ts              # Custom error classes\n│   │   ├── retry.ts               # Retry\u002Fbackoff logic\n│   │   └── types.ts               # Shared types\n│   ├── services\u002F\n│   │   ├── document-service.ts    # Document CRUD operations\n│   │   ├── template-service.ts    # Template-based workflows\n│   │   └── signing-service.ts     # Orchestrates signing flows\n│   ├── webhooks\u002F\n│   │   ├── handler.ts             # Express webhook router\n│   │   ├── verify.ts              # Secret verification\n│   │   └── processors\u002F\n│   │       ├── document-completed.ts\n│   │       ├── document-signed.ts\n│   │       └── document-rejected.ts\n│   ├── api\u002F\n│   │   ├── health.ts              # Health check endpoint\n│   │   └── routes.ts              # API routes\n│   └── config\u002F\n│       └── index.ts               # Environment configuration\n├── scripts\u002F\n│   ├── verify-connection.ts       # Quick health check\n│   ├── create-test-doc.ts         # Test document generator\n│   └── cleanup-test-docs.ts       # Test data cleanup\n├── tests\u002F\n│   ├── unit\u002F\n│   │   └── document-service.test.ts\n│   ├── integration\u002F\n│   │   └── document-lifecycle.test.ts\n│   └── mocks\u002F\n│       └── documenso.ts           # Mock client factory\n├── .env.development\n├── .env.production\n├── docker-compose.yml             # Self-hosted Documenso (dev)\n└── package.json\n```\n\n## Layer Architecture\n\n```\n┌─────────────────────────────────────────────────────────┐\n│  API \u002F Controllers                                       │\n│  Routes, request validation, response formatting         │\n├─────────────────────────────────────────────────────────┤\n│  Service Layer                                           │\n│  Business logic, orchestration, authorization            │\n│  (document-service, template-service, signing-service)   │\n├─────────────────────────────────────────────────────────┤\n│  Documenso Client Layer                                  │\n│  SDK wrapper, retry, error handling, caching             │\n│  (client.ts, retry.ts, errors.ts)                       │\n├─────────────────────────────────────────────────────────┤\n│  External Services                                       │\n│  Documenso API, S3\u002FGCS storage, email, database         │\n└─────────────────────────────────────────────────────────┘\n```\n\n**Rules:**\n- Controllers never call Documenso directly -- always go through services\n- Services never import `@documenso\u002Fsdk-typescript` directly -- use the client wrapper\n- Webhook processors are isolated -- one file per event type\n- Error handling happens at the client layer, not in controllers\n\n## Data Flow\n\n```\nUser Request\n     │\n     ▼\n┌──────────┐   POST \u002Fapi\u002Fsign\n│   API    │──────────────────────────────┐\n│  Router  │                              │\n└──────────┘                              ▼\n                                   ┌──────────────┐\n                                   │   Signing    │\n                                   │   Service    │\n                                   └──────┬───────┘\n                                          │\n                    ┌─────────────────────┼─────────────────────┐\n                    ▼                     ▼                     ▼\n             ┌──────────┐         ┌──────────┐          ┌──────────┐\n             │ Template │         │ Document │          │   Your   │\n             │ Service  │         │ Service  │          │    DB    │\n             └────┬─────┘         └────┬─────┘          └──────────┘\n                  │                    │\n                  └────────┬───────────┘\n                           ▼\n                    ┌──────────────┐\n                    │  Documenso   │\n                    │  Client      │──→ Documenso API\n                    │  (singleton) │\n                    └──────────────┘\n\nWebhook Flow:\nDocumenso API ──POST──→ \u002Fwebhooks\u002Fdocumenso\n                             │\n                        ┌────▼────┐\n                        │ Verify  │──→ Check X-Documenso-Secret\n                        │ Secret  │\n                        └────┬────┘\n                             │\n                        ┌────▼────┐\n                        │ Router  │──→ Route by event type\n                        └────┬────┘\n                             │\n              ┌──────────────┼──────────────┐\n              ▼              ▼              ▼\n        completed.ts    signed.ts     rejected.ts\n        (archive PDF)  (update DB)  (alert sender)\n```\n\n## Setup Script\n\n```bash\n#!\u002Fbin\u002Fbash\nset -euo pipefail\n\nmkdir -p src\u002F{documenso,services,webhooks\u002Fprocessors,api,config}\nmkdir -p scripts tests\u002F{unit,integration,mocks}\n\n# Create .env.example\ncat > .env.example \u003C\u003C 'EOF'\nDOCUMENSO_API_KEY=\nDOCUMENSO_BASE_URL=https:\u002F\u002Fapp.documenso.com\u002Fapi\u002Fv2\nDOCUMENSO_WEBHOOK_SECRET=\nLOG_LEVEL=info\nNODE_ENV=development\nEOF\n\necho \"Project scaffolded. Copy .env.example to .env and fill in values.\"\n```\n\n## Key Design Decisions\n\n| Decision | Rationale |\n|----------|-----------|\n| Singleton client | Avoids re-initialization overhead per request |\n| Service layer | Separates business logic from API details |\n| One processor per webhook event | Isolates side effects, easy to test |\n| Mock client for tests | Fast unit tests without API calls |\n| Template-first approach | Fewer API calls, consistent field placement |\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Circular dependencies | Wrong layering | Services import client, never the reverse |\n| Config not loading | Wrong env file | Verify `NODE_ENV` matches config loader |\n| Webhook processor crash | Unhandled error in processor | Wrap each processor in try\u002Fcatch |\n| Test isolation | Shared client state | Call `resetClient()` in `beforeEach` |\n\n## Resources\n\n- [Clean Architecture](https:\u002F\u002Fblog.cleancoder.com\u002Funcle-bob\u002F2012\u002F08\u002F13\u002Fthe-clean-architecture.html)\n- [Documenso SDK](https:\u002F\u002Fgithub.com\u002Fdocumenso\u002Fsdk-typescript)\n- [12-Factor App](https:\u002F\u002F12factor.net\u002F)\n\n## Next Steps\n\nFor multi-environment setup, see `documenso-multi-env-setup`.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","documenso","documenso-reference","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Implement Documenso reference architecture with best-practice project layout.\nUse when designing new Documenso integrations, reviewing project structure,\nor establishing architecture standards for document signing applications.\nTrigger with phrases like \"documenso architecture\", \"documenso best practices\",\n\"documenso project structure\", \"how to organize documenso\".\n","Read, Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--documenso-pack--documenso-reference-architecture",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill documenso-reference-architecture",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill documenso-reference-architecture",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill documenso-reference-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--documenso-pack--documenso-reference-architecture\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]