saas-platform-patterns
Skill34 starsChanged 9 days agoMITView on GitHub
SaaS monetization patterns for NestJS. Use when designing free, trial and paid tiers, license keys, subscription state machines, checkout and customer portal flows, or pricing configuration. Not for webhook plumbing — use webhook-architecture.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Hive-Academy/ptah-extensionword for word, first seen Nov 3, 2026
Other versions1 project uses a version of this.
Word for word · 1
- Hive-Academy/ptah-extension★ 34100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-lanesSkill
- angular-3d-scene-crafterSkill
- angular-frontend-patternsSkill
- angular-gsap-animation-crafterSkill
- ddd-architectureSkill
- execute-phase-gated-taskSkill
- frontend-designSkill
- humanize-librarySkill
- nestjs-backend-patternsSkill
- nestjs-deploymentSkill
- nx-workspace-architectSkill
- orchestrationSkill
- ptah-surface-authoringSkill
- resilient-nestjs-patternsSkill
- saas-workspace-initializerSkill
- session-handoffSkill
- skill-creatorSkill
- technical-content-writerSkill
- tribunalSkill
- ui-ux-designerSkill
- webhook-architectureSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Treat subscription state as authoritative for access decisions.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SaaS Platform Patterns
Apply
- Activate per Stage B monetization task; use discovery and the roadmap to choose the business model before implementing plans or entitlements.
- Treat subscription state as authoritative for access decisions. Make billing event processing idempotent and reconcile state with the provider.
- Separate license issuance and validation from checkout and portal flows. Keep provider credentials and webhook verification at integration boundaries.
Model and integration decisions
| Model | Pricing need and fit | Complexity | Route |
| Freemium | Free tier with paid gates; developer tools and productivity apps | Medium | Freemium model |
| Trial-to-paid | Time-limited full access; B2B and enterprise software | Low | Freemium model for trial handling |
| Usage-based | API calls, storage, or compute; APIs and infrastructure | High | Define metering before provider integration |
| Seat-based | Per-user team pricing; collaboration and project management | Medium | Count active seats in the domain model |
Models can be combined; start with the simplest model that validates pricing. Keep plan definitions in static configuration, enforce feature gates on the server, and use locally synchronized subscription state instead of calling the payment API on every request.
The webhook architecture skill owns the HTTP and verification layers; this skill's subscription service is its domain handler. The backend patterns skill owns the abstract payment client and provider adapters. Use the workspace architect for placement: licensing in shared/licensing, payment adapters in shared/payments.
Deduplicate payment events before issuing licenses or changing subscriptions. Keep business rules behind the payment client interface so changing provider does not change domain logic.
Load by task
- For plan tiers, feature limits, and upgrades, load freemium model.
- For issuing, validating, renewing, and revoking licenses, load license lifecycle.
- For subscription transitions and provider events, load subscription state machine.
- For hosted checkout and customer self-service, load checkout and portal.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.