saas-workspace-initializer
Skill34 starsChanged 9 days agoMITView on GitHub
Bootstraps a new SaaS workspace on Nx, NestJS and Angular or React — discovery, a phased roadmap and a foundation-only scaffold. Use when starting a new SaaS or multi-tenant project. Not for .NET stacks — use dotnet-solution-initializer.
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-platform-patternsSkill
- 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
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Verify the foundation and emit the handoff.
- Distinctive: line 17
Before discovery, design, roadmap writing, or foundation scaffolding, load Stage A workflow.
- Very specific: line 18
Before writing .ptah/roadmap.md, load roadmap format for the charter schema and dependency notation.
- Distinctive: line 42
After handoff, do not implement feature libraries, pre-create future task stubs, or run multiple roadmap items in this session.
≈ “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 Workspace Initializer
Stage A contract
- Complete discovery in two rounds: business first, then stack. Ask required unanswered questions and wait for answers before design or scaffolding. Use the available question tool or plain text when the tool is unavailable.
- Derive domain boundaries and Nx library layout from the answers. Write
.ptah/roadmap.mdusing the required schema, then scaffold only the foundation needed by the first Stage B tasks. - Verify the foundation and emit the handoff. Each unchecked roadmap item is a separate Stage B task in a new session; stop after the handoff.
- Per-stack initializers inherit the business discovery questions and roadmap schema here. Preserve this shared contract when changing either.
Load by task
- Before discovery, design, roadmap writing, or foundation scaffolding, load Stage A workflow. It contains the exact questions, conditional scaffold table, and verification gate.
- Before writing
.ptah/roadmap.md, load roadmap format for the charter schema and dependency notation.
Handoff and stop
Emit exactly this block, expanding only the next phase's items:
Foundation complete.
Roadmap written to .ptah/roadmap.md.
Scope decisions recorded in .ptah/scope-decisions.md.
Next tasks (run each in a NEW chat session, one at a time):
/orchestrate <slug-1> # <charter one-liner>
/orchestrate <slug-2> # <charter one-liner>
...
Each task will activate the relevant companion skill
(nx-workspace-architect, nestjs-backend-patterns, webhook-architecture,
resilient-nestjs-patterns, saas-platform-patterns, nestjs-deployment)
and pick up dependencies from the roadmap.After handoff, do not implement feature libraries, pre-create future task stubs, or run multiple roadmap items in this session.
Requires
ddd-architecture(ptah-core plugin) — Stage A uses it to name bounded contexts before the roadmap. If unavailable, tell the user to enable ptah-core before Step a2.dotnet-solution-initializer(ptah-dotnet plugin) — the .NET sibling that reuses this skill's Stage A contract and roadmap schema;references/roadmap-format.mdkeeps the schema stack-agnostic because of it. If it is not installed, the shared contract here still stands on its own.nx-workspace-architect— the Nx lib layoutreferences/stage-a-workflow.mdinvokes with the discovery answers before the roadmap is written. If it is not installed, tell the user to enable it before scaffolding the foundation.
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.