system-design-reviewer
Skill1 starsChanged 5 months agoMITView on GitHub
Use this to review a system or software design against scalability, reliability, security, and cost.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- alphasafal/production-agent-skillstheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- alphasafal/production-agent-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- a11y-auditorSkill
- aria-annotatorSkill
- color-contrast-fixerSkill
- keyboard-nav-checkerSkill
- agent-scaffoldSkill
- prompt-engineerSkill
- migration-plannerSkill
- tradeoff-analyzerSkill
- openapi-designerSkill
- rest-endpoint-scaffoldSkill
- cloud-resource-provisionerSkill
- index-advisorSkill
- migration-writerSkill
- query-optimizerSkill
- schema-designerSkill
- project-scaffolderSkill
- cd-deployment-builderSkill
- ci-pipeline-generatorSkill
- incident-runbook-builderSkill
- observability-instrumenterSkill
- release-automatorSkill
- changelog-generatorSkill
- doc-linterSkill
- doc-writerSkill
- client-perf-optimizerSkill
- component-scaffoldSkill
- code-review-coachSkill
- stakeholder-comms-writerSkill
- codebase-explorerSkill
- dependency-vuln-auditorSkill
- secret-scannerSkill
- security-headers-configurerSkill
- threat-modelerSkill
- coverage-gap-finderSkill
- load-test-designerSkill
- test-refactorerSkill
- unit-test-generatorSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 61
Note strengths: Call out what is sound and should be preserved.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
System Design Reviewer
Use this to review a system or software design against scalability, reliability, security, and cost.
Tech profile — Technology: any · Language: n/a · Stack: n/a · Toolchain: n/a · Domain: architecture (Pure-reasoning skill — reviews any design, from a microservice to a data platform.)
When to use this skill
- Reviewing a proposed design/RFC before implementation begins.
- Auditing an existing system for quality-attribute risks.
- Preparing input for an architecture decision or ADR.
When NOT to use this skill
- Choosing between design options — use
architecture/tradeoff-analyzer. - Planning a migration of an existing system — use
architecture/migration-planner. - Line-by-line code review — use a code-review workflow.
Prerequisites
- A described design (diagram, doc, or narrative) and its goals/constraints.
- The expected scale/load and any compliance requirements, if known.
Inputs
| Input | Required | Description |
design | yes | The design to review (doc, diagram, or description) |
goals | yes | What the system must achieve |
expected_scale | no | Load/growth expectations (assumed + stated if absent) |
constraints | no | Budget, compliance, team, deadline constraints |
Instructions
- Restate the design + goals. Summarize the design in your own words and the goals it serves. If the design is ambiguous, list the clarifying questions rather than guessing.
- Map the critical path. Identify the request/data flow that matters most and its dependencies.
- Review against quality attributes, each producing findings:
- Scalability — bottlenecks, statefulness, horizontal-scaling path.
- Reliability — single points of failure, failure modes, graceful degradation.
- Security — trust boundaries, authz, data protection (defer depth to
security-review, but flag here). - Cost & operability — cost drivers, observability, maintenance burden.
- Data — consistency model, growth, integrity.
- Severity-tag every finding 🔴 blocker / 🟠 major / 🟡 minor, each with a concrete recommendation (see /standards/review-process.md).
- Note strengths. Call out what is sound and should be preserved.
- Give a verdict — approve / approve-with-changes / needs-rework — driven by the highest open severity.
- List assumptions. Especially any assumed scale/constraints.
Output
A structured design review: restated design, critical-path map, severity-tagged findings per quality attribute (with recommendations), strengths, a verdict, and assumptions. Maps directly onto the architecture-review checklist.
Constraints & safety
- Evidence-based. Each finding cites a part of the design; no vague criticism.
- No rewrite. Recommend; do not silently redesign the system.
- Defer deep security to
security-audit/security-reviewbut never skip flagging. - Conforms to /standards/prompt-engineering.md.
Examples
Minimal below; full reviews in EXAMPLES.md.
Given: a single-instance API + single-DB design expecting 50× growth. Produces: findings incl. 🔴 single point of failure (DB), 🟠 stateful API blocks horizontal scaling, with recommendations, plus a verdict of needs-rework.
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.

