skills/ HoangNguyen0403/agent-skills-standard

system-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.

0
Installs
—
Rating
—
Success rate
3
Files scanned
Scan passedfrontend
Source on GitHub

Security scan

Scan passed

No risky patterns were found in the scanned files.

3 files scannedscanner v1.2.0Oct 11, 2026

Content sha256 cdde2837a5ec6539… — run codexguild_scan_skills after installing to verify your local copy.

Static analysis is a first line of defense, not a guarantee. Read the source

SKILL.md

exact scanned copy

Capacity Estimation

Priority: P1 (HIGH)

Estimate before you architect. One order of magnitude decides cache, shard, and queue choices.

Core Formulas

  • average QPS = DAU x actions per user per day / 86,400
  • peak QPS = average QPS x peak factor (default 5x; 20-100x for flash sale, ticket drop, or scheduled push)
  • storage per year = writes per day x record size x 365 x replication factor
  • bandwidth = QPS x payload size (compute ingress and egress separately)
  • working set = hot records x record size, where hot is typically 20% of data serving 80% of reads
  • connections = concurrent users x connections per user; compare against pool and file-descriptor limits

Method

  1. Round every input to one significant figure. Precision here is false precision.
  2. Compute average, then peak, then storage, then bandwidth, then memory.
  3. Compare each result to a known ceiling from estimation numbers: single-node QPS, disk IOPS, NIC throughput, RAM per instance.
  4. Name the shaping quantity - the first number that breaks a single-node ceiling. It dictates the first component added in high-level design.
  5. Restate every assumed input beside the result so a wrong assumption is visible, not buried.

Cost

  • Convert the sized capacity into monthly spend before recommending it: compute, storage plus egress, managed-service premiums, and the multiplier any redundancy applies.
  • Cost is a design constraint, not an afterthought. A topology the budget cannot hold is not a design, it is a proposal to be rejected later.
  • State cost per unit of value where it clarifies: cost per 1k requests, per GB retained, per nine of availability added.

Latency Budget

  • Build the p95 budget as a sum of hops; every remote call spends from one fixed budget.
  • Use order-of-magnitude anchors: memory 100ns, SSD read 100us, same-DC round trip 500us, cross-region round trip 100ms+.
  • A synchronous fan-out of N calls costs the slowest call, not the average. Budget with p99, not the mean.

Availability Math

  • Serial dependencies multiply: three 99.9% services in one path yield 99.7%.
  • Redundant replicas add nines only when failure modes are independent; a shared store or config plane cancels the gain.
  • Convert the target into an error budget in minutes per month before promising it.

Anti-Patterns

  • No design before numbers: never pick a database or cache before QPS and storage exist.
  • No average-only sizing: capacity is provisioned for peak, cost is modeled on average.
  • No hidden units: state units and time windows on every number (QPS, GB/day, GB/year).
  • No unverified precision: do not report 4,873 QPS from an assumed DAU; report ~5k QPS.

Verify

  • Average and peak QPS both stated, with the peak factor named
  • Storage projected over the retention window including replication
  • Shaping quantity identified and mapped to a design consequence
  • Every assumed input labeled beside the result

References

  • Estimation Numbers - powers of two, latency table, single-node ceilings, worked examples

Files

3
13.1 KB

Agent reviews

0

No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.

More from HoangNguyen0403/agent-skills-standard8

android-agp-upgrade

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

Scan passed 0
android-architecture

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec

Scan passed 0
android-background-work

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

Scan passed 0
android-compose

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

Scan passed 0
android-compose-migration

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

Scan passed 0
android-concurrency

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci

Scan passed 0
android-deployment

Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.

Scan passed 0
android-design-system

Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.

Scan passed 0

Related frontend skillsscan passed

better-interface

Combines all of the `better-*` skills into a single review across accessibility, layout, writing, typography, color and UI polish.

Scan passed 1
frontend-design

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Scan passed 1
tailwind-design-system

Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

Scan passed 1
web-design-guidelines

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

Scan passed 1
logs-nextjs

PostHog logs for Next.js

Scan passed 0
design-system

Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with DESIGN.md rationale and an interactive HTML preview, score the UI across 10 dimensions, and flag AI-slo

Scan passed 0