system-design
/system-design
Zadaje obowiązkowe pytania projektowe w trzech rundach, zapisuje decyzje i tworzy SYSTEM-DESIGN.md wraz z AUTH.md oraz rejestrem terminów realizacji.
- Autor
- Marwan-G ↗
- Repozytorium
- pavedline ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zadaje obowiązkowe pytania projektowe w trzech rundach, zapisuje decyzje i tworzy SYSTEM-DESIGN.md wraz z AUTH.md oraz rejestrem terminów realizacji.
Oryginalny opis (EN)
Step 4 of Pavedline. Asks the mandatory system-design questions in three short rounds (platform, behaviour, reach), records one decision per answer, and writes SYSTEM-DESIGN.md with numbers, AUTH.md, TENANCY-LIFECYCLE.md and the lead-time register. Use when STATE.md says STEP 4 and the founder says go.
Jak działa
- 1. Read first, in order
- 2. How to ask
- 3. Write the outputs
- 4. Close step 4
Podgląd SKILL.md
---
name: system-design
description: Step 4 of Pavedline. Asks the mandatory system-design questions in three short rounds (platform, behaviour, reach), records one decision per answer, and writes SYSTEM-DESIGN.md with numbers, AUTH.md, TENANCY-LIFECYCLE.md and the lead-time register. Use when STATE.md says STEP 4 and the founder says go.
---
# system-design
Step 4. Output: `docs/architecture/SYSTEM-DESIGN.md` (with numbers), `docs/architecture/AUTH.md`, `docs/architecture/TENANCY-LIFECYCLE.md`, `docs/production/LEAD-TIME.md`, items in `WAITING.md`, and one decision per answered area. Create `docs/architecture/` and `docs/production/` when missing (a project started with v0.1 has neither); never fail on their absence.
Follow the shared step rules in `${CLAUDE_PLUGIN_ROOT}/skills/state/references/step-rules.md`.
## 1. Read first, in order
After the records of the shared rules, read `docs/spec/SPEC.md` and `docs/business/BRIEF.md`. Take tenancy from decision 0002, compliance from decision 0003 and surfaces from decision 0005. Never re-ask a step-0 or step-2 question. Continue when `STATE.md` says `STEP: 4 — System design`.
Surfaces: per decision 0005, questions for a dropped surface are skipped (no mobile: no Mobile offline, no push, no store lead times; no website or blog: no Website, blog and SEO; no web app: no real-time screens). Record "skipped: surface dropped (decision 0005)" in `SYSTEM-DESIGN.md`.
## 2. How to ask
Rounds, not one long session. In each round, take the areas of `${CLAUDE_SKILL_DIR}/references/questions.md` in order, **one area at a time**, as the shared rules say. Costs are checked on the web (see `${CLAUDE_SKILL_DIR}/references/sources.md`) at expected user counts. A choice the founder already named is checked, not compared (see the top of `questions.md`).
### Round 1: platform
Backend (run the `backend-evaluate` skill; the founder decides) · Auth (`${CLAUDE_SKILL_DIR}/references/auth-contract.md`) · tenancy lifecycle (`${CLAUDE_SKILL_DIR}/references/tenancy-lifecycle.md`) · Security and compliance. **Next.js is frontend only:** no business logic, only a pass-through auth-cookie proxy, checked by a CI boundary check.
### Round 2: behaviour
Concurrency · Time and scheduling · Scheduled jobs · Performance · Images and files · Generated documents · Real-time · Notifications · Payments taken by tenants · Billing · AI and models.
### Round 3: reach
Accessibility (**WCAG 2.2 AA** default) · Languages and right-to-left · Mobile offline · Multi-region · Service mesh · Website, blog and SEO · Search · Availability and recovery.
## 3. Write the outputs
Before writing outputs, do the one fill-in turn of the shared rules.
- `SYSTEM-DESIGN.md`: one section per area, each with the decision number, the answer and **numbers** (users, requests per second, p95, RPO, RTO, sizes). No "TBD": an unknown number is written as a labelled assumption with the way to measure it.
- `AUTH.md`: the auth contract and the chosen provider's implementation.
- `TENANCY-LIFECYCLE.md`: the eight stages. Single-tenant (decision 0002): write "not applicable (decision 0002)" and nothing else.
- `LEAD-TIME.md` and `WAITING.md`: every item that takes days or weeks outside our control (payment provider verification, SMS sender registration, Apple and Google developer accounts and store review, processor agreements, domain verification), each with what, who, how long and what it blocks, written to both files now so it is finished by step 12.
Check: every area has a decision or a recorded reason; every number has a unit; every new service is in `SERVICES.md`.
## 4. Close step 4
Records-consistency pass first: dispatch the `reviewer` agent (subagent type `pavedline:reviewer`), blind, once, on the decisions and the step-4 outputs (`SYSTEM-DESIGN.md`, `AUTH.md`, `TENANCY-LIFECYCLE.md`, `LEAD-TIME.md`) for contradictions. `VERDICT: REJECT` means rework and a narrow re-review; only `VERDICT: APPROVE` lets `STATE.md` move on. Write the verdict and every finding to `docs/reviews/04-system-design-review.md` (create `docs/reviews/` when missing); on REJECT the file lists the findings to rework, so a fresh session resumes from it.
Edit `STATE.md` (see the `state` skill), time from `date "+%Y-%m-%d %H:%M"`:
```
STEP: 5 — Data and API
LAST: <timestamp> — step 4 done: SYSTEM-DESIGN.md, AUTH.md, TENANCY-LIFECYCLE.md, LEAD-TIME.md written; verdict in docs/reviews/04-system-design-review.md
NEXT: step 5 — domain model, schema, API contract
```
Commit and close as in the shared rules.
Pliki w paczce (5)
- SKILL.md 4 KB
- references/auth-contract.md 2 KB
- references/questions.md 7 KB
- references/sources.md 1 KB
- references/tenancy-lifecycle.md 2 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Marwan-G/pavedline | 100 | MIT |
| proyecto26/system-design-skills | 100 | MIT |
| DaraBoth/skilljmskill | 100 | MIT |
| nimadorostkar/Claude-Skills-collection | 100 | MIT |
| pinchen147/system-design-skill | 100 | MIT |
| reddygopalkrishna/developer-agent-skills | 100 | MIT |
| sudeeppatgar/fullstack-skills | 100 | MIT |
| rmsaitam/skill-system-design | 100 | MIT |
| wondelai/skills | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki c0d39aed71c0 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 85domain-model
Zamienia specyfikację i projekt systemu w model domeny z encjami, regułami, stanami i słownikiem pojęć, pytając wyłącznie o nierozstrzygnięte dane. - 90architecture-intake
Zadaje pytania o platformę: wielodostępność, zespół, powierzchnie, bazę danych i środowisko lokalne, z domyślnymi wartościami. - 90decision-records
Zapisuje decyzje projektowe jako ADR z klasyfikacją, cyklem życia i obowiązkową sekcją rozważanych alternatyw. - 100godot-grill
Przepytuje autora o otwarte decyzje projektowe nowego systemu w Godot, partiami, od zakresu, z zalecaną odpowiedzią do każdego pytania, i zapisuje odpowiedzi przed projektem lub kodem. - 84design
Rozstrzyga decyzje projektowe (typy, kontrakty, topologię pakietów, granice modułów) w rundach dyskusji przed planowaniem, zapisując je jako artefakty projektowe. - 100pm-scope
Rozstrzyga kolejne decyzje projektowe, pytanie po pytaniu, i zapisuje numerowane decyzje, otwarte pytania oraz zakres.