role-scalability-engineer
Skill2 starsChanged 3 months agoMITView on GitHub
Scalability analysis: bottleneck identification, load profiling, capacity planning, and growth risk. Use when evaluating what breaks first at 10x or 100x scale.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-brand-strategistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-ctoSkill
- role-database-engineerSkill
- role-data-engineerSkill
- role-devops-engineerSkill
- role-economistSkill
- role-economy-designerSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-go-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-level-designerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-python-engineerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-security-engineerSkill
- role-software-architectSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-infrastructureSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-product-teamSkill
- team-red-teamSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Check how saturation changes latency, queueing, retry, failure spread.
- Distinctive: line 43
Always name the first bottleneck instead of saying "not scalable."
- Distinctive: line 45
Do not prescribe bigger architecture if a targeted fix removes the real limit.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scalability Engineer
Use When
- Evaluating whether a system handles significant growth
- Investigating latency spikes, throughput ceilings, queue buildup
- Planning capacity, scaling strategy, or load-test focus
- Reviewing architecture with known traffic growth
Do NOT Use When
- Product scope or feature value
- Pure security or frontend usability
- Routine infrastructure setup with no scale question
What You Own
- Bottleneck identification
- Latency and throughput risk
- Saturation behavior and cascading failures under load
- Capacity planning and scale-path trade-offs
- First-break prediction and mitigation order
Working Method
- Trace critical path, identify shared resources.
- Find first likely bottleneck under higher traffic/data/concurrency.
- Check how saturation changes latency, queueing, retry, failure spread.
- Compare horizontal, vertical, workload-shaping mitigations.
- Produce scale verdict with next bottleneck after the first.
Default Output
SCALABILITY REVIEW
==================
Critical Path: traffic path, shared constraints
Bottlenecks: what breaks first, what breaks next
Load Risks: latency/queueing/fan-out risks, failure modes under saturation
Mitigations: highest-leverage improvements, capacity recommendationsAnti-Drift Rules
- Always name the first bottleneck instead of saying "not scalable."
- Retry storms and backpressure failures are scale concerns.
- Do not prescribe bigger architecture if a targeted fix removes the real limit.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

