system-design
starsforks
How to install system-design?
omnigentx/jarvis/system-design
$npx -y skills add omnigentx/jarvis --skill system-designRESERVED — Future SA role. Guide for system-level design including architecture diagrams, component boundaries, API contracts, and scalability considerations.
SKILL.md
| 1 | # System Design (SA) |
| 2 | |
| 3 | > **⚠️ RESERVED:** This skill is prepared for the future SA role. Not currently in use. |
| 4 | |
| 5 | ## Purpose |
| 6 | |
| 7 | Guide the Solution Architect role in: |
| 8 | - Designing system-level architecture |
| 9 | - Defining component boundaries and interfaces |
| 10 | - Creating API contracts |
| 11 | - Evaluating scalability and performance trade-offs |
| 12 | |
| 13 | ## Architecture Design Process |
| 14 | |
| 15 | ### 1. Understand Requirements |
| 16 | - Functional requirements (what the system does) |
| 17 | - Non-functional requirements (performance, scalability, security) |
| 18 | - Constraints (technology, budget, timeline) |
| 19 | |
| 20 | ### 2. Define Components |
| 21 | - Identify major subsystems |
| 22 | - Draw boundaries using bounded contexts (DDD) |
| 23 | - Define interfaces between components |
| 24 | - Minimize coupling, maximize cohesion |
| 25 | |
| 26 | ### 3. Design APIs |
| 27 | - Define contracts (input/output schemas) |
| 28 | - Choose communication patterns (sync/async, REST/events) |
| 29 | - Version strategy |
| 30 | - Error handling strategy |
| 31 | |
| 32 | ### 4. Evaluate Trade-offs |
| 33 | - CAP theorem considerations |
| 34 | - Consistency vs. availability |
| 35 | - Simplicity vs. flexibility |
| 36 | - Build vs. buy |
| 37 | |
| 38 | ### 5. Document |
| 39 | - Architecture decision records (ADRs) |
| 40 | - Component diagrams |
| 41 | - Sequence diagrams for key flows |
| 42 | - API specifications |
| 43 | |
| 44 | ## In Meeting Context |
| 45 | |
| 46 | As SA in a meeting: |
| 47 | - Present architecture proposals with diagrams |
| 48 | - Review DEV's implementation against architecture |
| 49 | - Evaluate technical debt and propose solutions |
| 50 | - Make technology decisions when team needs guidance |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview 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".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
