Skip to content
Skills Library
Programming · Planning

system-design-interview-framework

/system-design-interview-framework

Use this skill when structuring system design discussions: scoping requirements, estimating QPS/storage, and mapping data flows.

Licence
MIT
Last repository change
28.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this skill when structuring system design discussions: scoping requirements, estimating QPS/storage, and mapping data flows.

Original author description

Use this skill when structuring system design discussions: scoping requirements, estimating QPS/storage, and mapping data flows.

How it works

  1. When to use
  2. Prerequisites
  3. Step-by-step workflow
  4. Commands / code examples
  5. Common mistakes & pitfalls
  6. Verification checklist
  7. Related skills
Original SKILL.md headings · 39 lines, 240 words
SKILL.md preview
---
name: system-design-interview-framework
description: Use this skill when structuring system design discussions: scoping requirements, estimating QPS/storage, and mapping data flows.
---
# System Design Interview Architecture Framework

## When to use
Use this skill when you need to structuring system design discussions: scoping requirements, estimating QPS/storage, and mapping data flows.

## Prerequisites
- Deep familiarity with relevant domain standards, developer tooling, or testing frameworks.
- Access to testing repository, mobile simulator, or operational workspace.

## Step-by-step workflow
1. **Analyze requirements and constraints**: Review code quality gates, mobile runtime targets, or architecture patterns.
2. **Design implementation strategy**: Draft explicit interfaces, test cases, or declarative configurations.
3. **Execute implementation**: Build and integrate components according to domain best practices.
4. **Validate correctness**: Run automated test suites, verify build outputs, and inspect diagnostic logs.
5. **Establish maintenance guardrails**: Configure CI/CD quality checks, alerts, and documentation.

## Commands / code examples
```bash
# Operational command and verification workflow for system-design-interview-framework
echo "Executing verification check for system-design-interview-framework"
```

## Common mistakes & pitfalls
- Bypassing automated testing or linting checks under delivery pressure.
- Neglecting to isolate side effects, leading to flaky tests or fragile architectures.
- Introducing tight coupling between distinct architectural domains or deployment units.

## Verification checklist
- [ ] Implementations adhere strictly to domain conventions and standards.
- [ ] Automated verification passes cleanly with zero warnings or errors.
- [ ] Edge cases, error paths, and resource lifecycles are explicitly handled.
- [ ] Documentation and architectural decision records are updated.

## Related skills
- unit-testing-principles-aaa-pattern
- domain-driven-design-bounded-contexts
- ci-cd-github-actions-workflows
- git-interactive-rebase-squash-clean-history

Versions

The database has no other skills named system-design-interview-framework.

Database snapshot: 13.11.2026 · package version 5545bf3c30b6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100system-design-interview-capacity-estimation-qps
    Use this skill when conducting back-of-the-envelope calculations for queries per second, network bandwidth, and multi-year storage sizing.
  • 100back-of-the-envelope
    This skill should be used when the user needs to "estimate QPS", "back-of-the-envelope" (BOTEC) numbers, "how much storage / bandwidth", "how many servers", "peak load", "capacity planning", or wants the standard latency / throughput / availability numbers to ground a design…
  • 100system-design-estimation
    Compute defensible capacity numbers before architecture: average and peak QPS, storage growth, bandwidth, working-set memory, latency and availability budgets. Use when sizing a service, provisioning infrastructure, or checking that a design survives peak load.
  • 100system-design-estimation
    Compute defensible capacity numbers before architecture: average and peak QPS, storage growth, bandwidth, working-set memory, latency and availability budgets. Use when sizing a service, provisioning infrastructure, or checking that a design survives peak load.
  • 95qdrant-scaling-qps
    Guides Qdrant query throughput (QPS) scaling. Use when someone asks 'how to increase QPS', 'need more throughput', 'queries per second too low', 'batch search', 'read replicas', or 'how to handle more concurrent queries'.
  • 95qdrant-scaling-qps
    Guides Qdrant query throughput (QPS) scaling. Use when someone asks 'how to increase QPS', 'need more throughput', 'queries per second too low', 'batch search', 'read replicas', or 'how to handle more concurrent queries'.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.