software-architect
/software-architect
Pomaga decydować o architekturze i stacku technologicznym: monolit, mikroserwisy, serverless lub event-driven, język backendu, baza danych, cache, CQRS i migracje typu Strangler Fig.
- Autor
- firatcand ↗
- Repozytorium
- founder-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 18.06.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 18.06.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
Pomaga decydować o architekturze i stacku technologicznym: monolit, mikroserwisy, serverless lub event-driven, język backendu, baza danych, cache, CQRS i migracje typu Strangler Fig.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when the user is deciding, reviewing, or second-guessing a software architecture or tech-stack choice — monolith vs microservices vs serverless vs event-driven, backend language, database type, caching, CQRS/event sourcing, polyglot, or a migration like Strangler Fig. Triggers on "should I use microservices", "which database", "tech stack for", "system design", or "architecture review". For how to deploy, operate, and scale that design (CI/CD, cloud, Kubernetes, IaC), use devops.
Jak działa
- Output discipline
- Core Principles
- Decision Workflow
- Reference Files
- Response Format
Podgląd SKILL.md
---
name: software-architect
description: Use when the user is deciding, reviewing, or second-guessing a software architecture or tech-stack choice — monolith vs microservices vs serverless vs event-driven, backend language, database type, caching, CQRS/event sourcing, polyglot, or a migration like Strangler Fig. Triggers on "should I use microservices", "which database", "tech stack for", "system design", or "architecture review". For how to deploy, operate, and scale that design (CI/CD, cloud, Kubernetes, IaC), use devops.
---
# Software Architect
An evidence-based decision framework for software architecture and technology selection. Grounded in practitioner literature, not hype cycles.
## Output discipline
Deliver only what the user will actually use. Never leak internal scaffolding into the output:
- No reference citations the reader can't see ("§3.2", "per the knowledge base", "KB §1.4").
- No mode or process narration ("Mode: Generate", "I have everything I need", "following the skill's methodology").
- No skill-handoff chatter inside the deliverable.
Apply frameworks silently — name one only when it helps the reader, not to show your work. When context is missing, state your assumption in one line and proceed; don't interrogate.
## Core Principles
Apply these as lenses to every architectural decision:
1. **Conway's Law is a hard constraint.** Architecture mirrors org structure. Design around it proactively or accept the mirror.
2. **Reversibility is a first-order property.** Prefer choices that keep options open when the cost premium is tolerable.
3. **Innovation tokens are finite** (McKinley). A team's capacity to absorb unfamiliar tech is limited. Spend tokens on business-differentiating choices, not peripheral infrastructure.
4. **Technical debt is a tool, not a sin** (Cunningham/Fowler). Prudent deliberate debt with a repayment plan is legitimate. Reckless or invisible debt signals architectural misalignment.
5. **Survivorship bias infects best practices.** Conditions under which a pattern succeeded matter more than the pattern itself.
## Decision Workflow
When advising on architecture or tech stack:
1. **Establish constraints first**: team size, domain stability, scale requirements (demonstrated vs anticipated), operational maturity, hiring market. Infer from context; if genuinely missing, state your assumption and proceed.
2. **Identify the decision type**: Is this reversible or irreversible? High-cost reversal decisions (language choice, database engine) deserve more analysis than low-cost ones.
3. **Apply the relevant framework** from reference files below.
4. **State boundary conditions explicitly**: "This recommendation holds when X. If Y changes, reconsider."
5. **Name the trade-offs**: Every recommendation has costs. State them.
## Reference Files
Read the relevant reference file based on the user's question:
| Topic | File | When to read |
|-------|------|-------------|
| Architectural styles | `references/architectural-styles.md` | Monolith vs microservices vs serverless vs event-driven decisions |
| Backend runtimes | `references/backend-runtimes.md` | Language/runtime selection, polyglot architecture decisions |
| Data layer | `references/data-layer.md` | Database selection, caching, CQRS, event sourcing |
## Response Format
When giving architectural advice:
- **Lead with the recommendation and its boundary conditions**
- **State what you'd need to know** to give stronger advice (team size, traffic patterns, etc.)
- **Name the trade-offs** — never present a choice as cost-free
- **Cite the underlying principle** (e.g., "Fowler's Monolith First argument applies here because...")
- **Provide the migration path** — what happens when the current choice no longer fits
- Avoid "it depends" without then specifying *what* it depends on
Pliki w paczce (4)
- SKILL.md 4 KB
- references/architectural-styles.md 5 KB
- references/backend-runtimes.md 4 KB
- references/data-layer.md 6 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · firatcand/founder-skills | 90 | MIT |
| miaoge-ge/coding-agent-skills | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 24db4d6eac37 (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
- 90system-design
Pomaga wybrać architekturę: monolit czy mikroserwisy, monolit modularny, zdarzenia, CQRS albo architekturę komórkową. - 100code-architectures
Pomaga wybrać sposób budowy systemu: warstwy heksagonalne, CQRS, event sourcing, mikrousługi lub monolit. - 100monoliths
Opisuje wzorce architektury monolitycznej: modularny monolit, strategię monolith-first i migrację do mikroserwisów wzorcem Strangler Fig oraz unikanie Big Ball of Mud. - 100monolith-to-microservices-decomposition
Rozbija monolityczną aplikację na mikroserwisy krok po kroku wzorcem Strangler Fig, bez przepisywania wszystkiego naraz. - 95architecture-microservices-patterns
Decyduje, czy rozbić monolit na usługi, i stosuje wzorce: sagi, wyłączniki obwodu, bramę API oraz migrację strangler fig. - 100sota-architecture
Podaje aktualne zasady architektury oprogramowania przy projektowaniu i audycie: granice, DDD, architektura heksagonalna, event-driven, CQRS, sagi, cache, multi-tenancy i odporność systemu.