Automated summary
Guides the agent in analyzing, recommending, and documenting software system architecture and trade-offs.
Strengths
- Provides a structured method to break down system components.
- Makes trade-offs explicit between performance, scalability, reliability, and security.
- Recommends architectural patterns that fit the context.
Limitations
- Requires clear performance constraints to be effective.
- May produce complex diagrams for very large systems.
- Does not replace validation through prototyping or load testing.
Use this skill when you need to design a system architecture or evaluate trade-offs between non-functional qualities.
Avoid this skill for purely algorithmic or low-level tasks (e.g., optimizing a single function).
Security analysis
SafeThis skill only provides textual guidance on system design analysis and documentation. It uses only Read and Write tools, and does not instruct or imply any code execution, system modification, or dangerous operations.
No concerns found
How this analysis is madeExamples
Design a scalable document search system for 10M users with sub-second queries and secure access controls.Evaluate architectural trade-offs for an e-commerce platform handling flash sales, considering cost, performance, and consistency.name: system-design description: Guides the agent in analyzing, recommending, and documenting software system architecture and trade-offs. Use this skill for high-level design tasks such as component breakdowns, performance constraints, and architectural patterns. license: Apache-2.0 metadata: category: engineering version: "1.0" allowed-tools: Read Write
System Design Skill
Overview
This skill enables the agent to perform robust system design reasoning with explicit attention to quality attributes: performance, scalability, reliability, and security.
When to use
Activate this skill when the task involves:
- Designing a system architecture
- Evaluating design trade-offs (performance vs cost vs complexity)
- Recommending architectural patterns
- Identifying non-functional requirements
Instructions
- Start by identifying the contextual constraints (scale, latency, consistency, security requirements).
- Enumerate system components and interactions.
- For each major quality attribute (performance, reliability, security), provide explicit reasoning on trade-offs.
- Recommend patterns (e.g., microservices, event-driven, caching strategies) and justify selection.
- Produce a structured design document (sections: Overview, Requirements, Components, Quality Attribute Analysis, Diagrams/References).
Examples
Input: “Design a scalable document search system for 10M users with sub-second queries and secure access controls.”
Output:
- Requirements breakdown
- Quality attribute analysis
- Suggested architecture pattern
- Estimated throughput/latency
Edge Cases
- Conflicting non-functional requirements
- Undefined performance constraints
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/system-design-architecture-mm5t8bay/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/system-design-architecture-mm5t8bay' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/system-design-architecture-mm5t8bay/download' --output '.skill-downloads/system-design-architecture-mm5t8bay/SKILL.md.part' && mv '.skill-downloads/system-design-architecture-mm5t8bay/SKILL.md.part' '.skill-downloads/system-design-architecture-mm5t8bay/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read Write
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/system-design-architecture-mm5t8bay/SKILL.md' && test -s '.skill-downloads/system-design-architecture-mm5t8bay/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/system-design' && cp -R '.skill-downloads/system-design-architecture-mm5t8bay' '.claude/skills/system-design'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/system-design-architecture-mm5t8bay'openskills read 'system-design-architecture-mm5t8bay'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/system-design-architecture-mm5t8bay/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.