achreftlili/architect/system-design
architect/system-design/SKILL.md
--- name: system-design description: Use this skill whenever the architect subagent is asked to design a system, propose an architecture, create a technical blueprint, or structure a new application. Triggers on: "design a system for", "architecture for", "how should we build", "technical design", "system blueprint", "design this platform", "architect a solution". Always use this skill before producing any architecture proposal — it enforces completeness, consistency, and the correct output form
$ install --global
skillsauthnpx skillsauth add achreftlili/deep-dev-skills architect/system-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 2:48 PM10.4s1 file scanned
SKILL.md
- name:
- system-design
- description:
- Use this skill whenever the architect subagent is asked to design a system, propose an architecture, create a technical blueprint, or structure a new application. Triggers on: "design a system for", "architecture for", "how should we build", "technical design", "system blueprint", "design this platform", "architect a solution". Always use this skill before producing any architecture proposal — it enforces completeness, consistency, and the correct output format including Mermaid diagrams.
- category:
- architect
- agent-type:
- architect
System Design Skill
Purpose
Produce complete, structured, opinionated architecture proposals that teams can act on immediately.
Output Format (always follow this structure)
1. Problem Restatement
One paragraph. Confirm what is being built, the scale expectations, and the main constraints. Forces clarity before designing.
2. Architecture Overview
A high-level Mermaid diagram showing all major components and their relationships.
graph TD
Client --> APIGateway
APIGateway --> ServiceA
APIGateway --> ServiceB
ServiceA --> DB[(Database)]
ServiceB --> Cache[(Cache)]
3. Component Breakdown
For each component:
- Role: what it does
- Technology choice: specific tool/language/framework with brief justification
- Interfaces: how it communicates (REST, gRPC, events, etc.)
- Scaling strategy: horizontal / vertical / stateless / etc.
4. Data Flow
Describe the main request/response flows (happy path + at least one failure path). Use a sequence diagram if helpful.
sequenceDiagram
User->>API: Request
API->>Service: Process
Service->>DB: Query
DB-->>Service: Result
Service-->>API: Response
API-->>User: Result
5. Key Design Decisions
A table of the most important trade-offs made:
| Decision | Chosen | Alternative | Reason | |----------|--------|-------------|--------| | Database | PostgreSQL | MongoDB | Strong consistency needed |
6. Non-Functional Requirements Coverage
Address explicitly:
- Scalability: how the system scales under load
- Availability: SLA target, redundancy approach
- Latency: expected p50/p99 for critical paths
- Security: auth, encryption, attack surface
- Observability: logging, metrics, tracing strategy
7. Risks & Open Questions
List 3–5 unresolved concerns or assumptions that need validation before implementation.
8. Next Steps
Ordered list of what the team should do first to begin implementation.
Design Principles to Always Apply
- Prefer boring technology for core infrastructure; reserve novelty for differentiating parts
- Design for failure: every external call can fail — show how the system handles it
- Explicit over implicit: no magic, no hidden coupling
- Start with data: model the data before the services
- Avoid premature optimization: design for current scale × 10, not × 1000
- Single responsibility: each component/service does one thing well
Scale Heuristics
| Users | Architecture Target | |-------|-------------------| | <10k DAU | Monolith + managed DB | | 10k–1M DAU | Modular monolith or 2–4 services | | >1M DAU | Microservices with dedicated data stores |
Always state the target scale and design accordingly. Do not over-architect.
Related Skills
achreftlili/vitest-testing-skill
testing
VerifiedTrustedCommunity
Set up Vitest 2.x with TypeScript for unit and component testing using test/describe/it, vi.fn/vi.mock/vi.spyOn, component testing with Testing Library, coverage (v8/istanbul), workspace config, and snapshot testing.
1SKILL.mdUpdated Apr 25, 2026
achreftlili/pytest-testing-skill
testing
VerifiedTrustedCommunity
Set up pytest 8.x with Python for unit and integration testing using fixtures (scope, autouse, parametrize), async tests (pytest-asyncio), mocking (unittest.mock, pytest-mock), coverage (pytest-cov), conftest.py patterns, and markers.
1SKILL.mdUpdated Apr 25, 2026
achreftlili/playwright-testing-skill
testing
VerifiedTrustedCommunity
Set up Playwright 1.49+ with TypeScript for E2E testing using page object model, fixtures, test.describe/test blocks, assertions, selectors, network mocking, CI configuration, and trace viewer.
1SKILL.mdUpdated Apr 25, 2026
achreftlili/jest-testing-skill
testing
VerifiedTrustedCommunity
Set up Jest 30+ with TypeScript for unit tests, integration tests, mocking (jest.fn, jest.mock, jest.spyOn), coverage configuration, custom matchers, snapshot testing, and setup/teardown patterns.
1SKILL.mdUpdated Apr 25, 2026