software-architecture
/software-architecture
Podaje sprawdzone zasady układu repozytorium, baz danych, kolejek, API i infrastruktury, z odniesieniami do źródeł.
- Autor
- TimothyVang ↗
- Repozytorium
- deepmodebot ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.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 12.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
Podaje sprawdzone zasady układu repozytorium, baz danych, kolejek, API i infrastruktury, z odniesieniami do źródeł.
Oryginalny opis (EN)
Cited guidance on repo layout and monorepo tooling, domain vocabulary and typed models, knowledge graphs, choosing and migrating databases, multi-tenancy, queues and durable workflows, API style, reliability, observability, deployment, and IaC. Use when designing or changing structure, data models, databases, or backend infrastructure.
Jak działa
- Rules for the agent
- Default stack for a solo dev or small team
Podgląd SKILL.md
--- name: software-architecture description: "Cited guidance on repo layout and monorepo tooling, domain vocabulary and typed models, knowledge graphs, choosing and migrating databases, multi-tenancy, queues and durable workflows, API style, reliability, observability, deployment, and IaC. Use when designing or changing structure, data models, databases, or backend infrastructure." metadata: as-of: "2026-11-11" --- # Architecture: monorepos, ontology, databases, backend infrastructure Read before designing or changing a project's shape: repo layout and workspace tooling, the domain vocabulary and data model, the database and its migrations, or the backend services, jobs, APIs, observability, and deployment. Researched 2026-11-11 from primary sources (official docs, specs, vendor pricing and engineering blogs, GitHub releases and licenses). Each claim carries its link; `[inference]` and `[unverified]` mean what they say. Versions, licenses, and free tiers move: recheck the one you pick. | File | Read when | |---|---| | `references/monorepos.md` | Monorepo or not; `apps/` and `packages/` layout; pnpm, Turborepo, Nx, uv, Go, Cargo, Bazel; enforced boundaries; affected-only CI and caching; nested `AGENTS.md`; worktrees for parallel agents | | `references/ontology.md` | Naming the domain: glossary, bounded contexts, ADRs; one typed model (Pydantic, Zod, LinkML) feeding API, DB, and agent tools; RDF, OWL, SHACL; property graphs; semantic layers; Palantir-style ontology for agent actions; GraphRAG and agent memory | | `references/databases.md` | Choosing a database or extension, hosted free tiers and branching, schema and migrations in the repo, ORMs, zero-downtime migrations, tenancy and RLS, IDs, backups, and letting agents near a database safely | | `references/backend-infrastructure.md` | Monolith or services, reliability (timeouts, retries, idempotency, SLOs, health checks), queues and durable workflows, caching, API style and errors, OpenTelemetry, deployment and IaC, capacity and cost | These files build on `skill://domain-rules/references/backend-system-design.md` (API naming, indexing, cache and queue basics) and deepmodebot's `model-the-domain` principle (`skill://deepmodebot/references/principles/model-the-domain.md`). Where they disagree, these primary-source files win: for example, retries follow the AWS Builders' Library token-bucket advice rather than a circuit breaker on every call. Cloud security and pipelines stay in `skill://cloud-devsecops`; secrets and auth in `skill://secrets-and-auth`. ## Rules for the agent 1. **Name before you build.** Add or reuse terms in `docs/GLOSSARY.md` and map each to one code, DB, API, and event name. Record a choice between real options as an ADR in `docs/adr/`. 2. **One source of truth for the domain model.** A typed model (Pydantic or Zod; LinkML when three or more artifacts or languages need it) feeds the API schema, DB mapping, and agent tool schemas. Never hand-maintain two copies. 3. **Start simple and say what would force a change.** Modular monolith, one Postgres, a Postgres-backed job queue, REST plus OpenAPI. Add a service, queue, graph, or vector store only when you can name the force (scale, isolation, ownership, query shape) and write it in the ADR. 4. **One repo, enforced boundaries.** `apps/*` and `packages/*`; one package owns each database's schema and migrations; boundaries checked in CI (`turbo boundaries` or dependency-cruiser, import-linter, Go `internal/`). 5. **Migrations are expand-contract and reviewed.** Lint them (Squawk), set `lock_timeout`, build indexes concurrently, and never run destructive commands (`DROP`, `TRUNCATE`, `migrate reset`, `push --force`) against shared data without the user's yes. 6. **Agents get least-privilege data access.** Separate owner, app, and read-only agent roles; a branch database per PR or agent; no production credentials for agents. Read-only still leaks: prompt injection can exfiltrate what the role can read. 7. **Every remote call has a timeout; retry at one layer** with capped exponential backoff and jitter, and only idempotent operations (`Idempotency-Key` on creates and payments). 8. **Observe from day one.** OpenTelemetry traces and JSON logs with trace IDs, liveness that checks nothing external, readiness that does, and one availability and one latency SLO per user-facing API. 9. **Check the license and release date before adopting a tool.** BSL, SSPL, FSL, and AGPL each carry different obligations; archived or unmaintained tools are not defaults. 10. **Prove it on the real thing.** Tests run against a real database (Testcontainers or PGlite) with migrations applied, not mocks; load-test before launch. ## Default stack for a solo dev or small team | Area | Default | Grows into | |---|---|---| | Repo | One repo: pnpm workspaces with catalogs, `apps/*` + `packages/*`, Turborepo with free Vercel Remote Cache; Python as a uv workspace, Go as one module | Nx when you want generators and a project graph; Bazel or Pants only when CI time is the bottleneck | | Agent context | Root `AGENTS.md` under ~200 lines with the package map and commands; a short `AGENTS.md` per app; one worktree per parallel agent under `.worktrees/` | Per-package skills and verify skills | | Domain | `docs/GLOSSARY.md`, ADRs, one Pydantic or Zod model; agents act through typed action tools, never raw write SQL | LinkML for multi-language models; Apache AGE on Postgres for graph traversal; Graphiti for agent memory | | Database | Postgres 18 (Neon Free for branching, or Supabase Free with auth and storage); `packages/db` owns schema, migrations, seeds, client, and types | Paid plan with PITR before real users; pgvector, FTS, and pg_partman before separate stores | | Data access | Drizzle (TS), SQLAlchemy 2 + Alembic (Python), sqlc + goose (Go); `uuidv7()` keys; `tenant_id` + RLS with `FORCE ROW LEVEL SECURITY` | db-per-tenant only for contractual isolation | | Backend | One container, `web` and `worker` processes, modules by domain with a public `index` | Split a service only for a named force | | Jobs and workflows | pg-boss or Graphile Worker (Node), River (Go), DBOS or pgmq (Python), enqueued in the business transaction | DBOS, Hatchet, or Temporal when flows run minutes or wait on humans | | API | REST + OpenAPI 3.1, RFC 9457 errors, cursor pagination, idempotency keys | gRPC for internal service-to-service; tRPC only for a TS-only frontend | | Observability | OpenTelemetry SDK and Collector to SigNoz self-hosted or a vendor free tier; Sentry free tier for errors | Grafana LGTM when you run your own stack | | Deploy | Render, Railway, or Fly for zero ops, or Kamal or Coolify on one VPS; preview deploy per PR; OpenFeature-compatible flags | OpenTofu once there are cloud resources beyond the PaaS; Kubernetes only when a team operates it |
Pliki w paczce (5)
- SKILL.md 7 KB
- references/backend-infrastructure.md 36 KB
- references/databases.md 38 KB
- references/monorepos.md 30 KB
- references/ontology.md 32 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · TimothyVang/deepmodebot | 100 | MIT |
| aeondave/malskill | 100 | MIT |
| Bbeierle12/Skill-MCP-Claude | 100 | MIT |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| rootcastleco/rei-skills | 100 | MIT |
| davila7/claude-code-templates | 100 | MIT |
| hybridlabor-api/aos | 100 | Apache-2.0 |
| thangchung/agent-engineering-experiment | 100 | MIT |
| vladolaru/claude-code-plugins | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 7cd8a4eaea46 (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
- 100backend-saas
Podaje wzorce backendu SaaS: projekt API, multi-tenancy, uwierzytelnianie i skalowalność, przy budowie usług, infrastruktury SaaS i architektury systemu. - 100create-a-backend
Doradza w architekturze backendu: planowanie i migracja API, wybór między Functions, Services, kontenerami, Workflow, kolejkami i bazami z Marketplace oraz dobór frameworka. - 100backend-engineer
Wspiera projektowanie API, pracę z bazami danych, mikroserwisy, uwierzytelnianie i autoryzację, optymalizację wydajności serwera, modele danych oraz architekturę systemów. - 100architecting-software
Projektuje architekturę oprogramowania na podstawie zatwierdzonego PRD, pisze ADR, dobiera styl architektury, technologie i bazy danych. - 95designing-architectures
Zbiera wiedzę o architekturze: projektowanie API, architektura bezpieczeństwa, wzorce cloud-native, cache, kolejki komunikatów i bezpieczeństwo danych. - 100backend
Prowadzi przez projektowanie i zmiany API, usług, baz danych, autoryzacji, zadań w tle i wdrożeń po stronie serwera.