Basinfy/Basinfy-SaaS-Studio / .claude/skills/saas-create-architecture
saas-create-architecture
VerifiedAuthor the master SaaS system architecture blueprint, C4 layers, and DB boundaries.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.7 KB |
| references/0-load-context.md | markdown | 10.7 KB |
| references/1-layers.md | markdown | 2.6 KB |
| references/2-module-ownership.md | markdown | 1.1 KB |
| references/3-data-flow.md | markdown | 1009 B |
| references/4-api-boundaries.md | markdown | 1.0 KB |
| references/5-adr-audit.md | markdown | 1.9 KB |
| references/6-missing-adrs.md | markdown | 782 B |
| references/7-write.md | markdown | 4.8 KB |
| references/8-handoff.md | markdown | 2.5 KB |
references/1-layers.md
View on GitHub# /saas-create-architecture — Phase 1: System Layer Mapping
> Part of `/saas-create-architecture`. `SKILL.md` names when to read this file; the settings it
> resolved and the rules under its later headings still apply here.
## Phase 1: System Layer Mapping
Map every system from `features-modules-index.md` into an architecture layer. The standard
SaaS architecture layers are:
```
┌─────────────────────────────────────────────┐
│ PRESENTATION LAYER │ ← UI, App Shell, menus, VFX, audio
├─────────────────────────────────────────────┤
│ FEATURE LAYER │ ← core business workflows, background workers, AI pipelines
├─────────────────────────────────────────────┤
│ CORE DOMAIN LAYER │ ← business logic, services, domain models
├─────────────────────────────────────────────┤
│ FOUNDATION LAYER │ ← engine integration, save/load,
│ │ scene management, event bus
├─────────────────────────────────────────────┤
│ PLATFORM LAYER │ ← OS, hardware, engine API surface
└─────────────────────────────────────────────┘
```
The Platform layer is the engine and cloud platform the application runs on, not code the project
writes. No PRD system goes in it, so it has no epic, stories or control-manifest
rules: a system that wraps a platform or engine API belongs in Foundation.
For each PRD system, ask:
- Which layer does it belong to?
- What are its module boundaries?
- What does it own exclusively? (data, state, behaviour)
Present the proposed layer assignment and ask for approval before proceeding to
the next section. Record the approved layer map in
`production/session-state/active.md`; it goes into the document at Phase 7.
**Engine awareness check**: For each system assigned to the Core and Foundation
layers, flag if it touches a HIGH or MEDIUM risk engine domain. Show the relevant
stack reference excerpt inline.
---
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |