skills.rest
FoundationForge
FoundationForgeOFFICIAL
Explore all skills by this author →
GitHub

system-design

Identifies architectural needs and generates a documented system design plan.

Updated Apr 12, 2026
Search Tags:#architecture#scalability#reliability#trade-offs#data-modeling#api-design#system-design
One-click install
npx skills add https://github.com/FoundationForge/cowork-plugins --skill system-design-foundationforge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-design
Source: https://github.com/FoundationForge/cowork-plugins/tree/main/plugins/engineering/skills/system-design
Command: npx skills add https://github.com/FoundationForge/cowork-plugins --skill system-design-foundationforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing systems and architectures can be error-prone and slow without a structured approach. This skill helps teams capture requirements, evaluate trade-offs, and produce actionable design plans.

Core Features & Use Cases

  • Requirements gathering, high-level design, deep-dive modeling, API contracts, and scalability analysis.
  • Use Case: When starting a new service, guide architects to define components, data flows, interfaces, and nonfunctional considerations.

Quick Start

Describe your system goal and constraints, and I will generate a high-level architecture outline.

Frequently Asked Questions about system-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure system design for a new web-scale service?▼

System design for a new web-scale service requires structured requirements gathering, high-level design, deep-dive data modeling, and trade-off analysis to produce a documented implementation plan.

What is the best way to evaluate architecture trade-offs for scalability planning?▼

Evaluating architecture trade-offs for scalability planning involves analyzing nonfunctional considerations and service boundaries to ensure reliability across web-scale projects.

How do I define API contracts and data modeling during high-level design?▼

Defining API contracts and data modeling during high-level design requires deep-dive modeling to establish structured interfaces, component definitions, and data flows.

Can I use this system design approach for API design and service boundaries?▼

Yes, you can use this approach for API design and service boundaries, as it enforces structured requirements gathering and deep-dive modeling across web-scale projects.

What are the limitations of unstructured system design without trade-off analysis?▼

Without structured trade-off analysis, system design becomes error-prone and slow, failing to capture requirements or produce actionable architectural design plans.

Related Skills

Explore More Software Engineering Skills→
MysMonMysMon
2

interview

Extract goals, constraints, and success criteria through structured interview phases.

Community
Advanced
susantosantosusantosanto

superpowers-writing-plans

Translate approved specs into structured implementation plans with tasks and architecture.

Community
Intermediate
cosmixcosmix
53

crossplane

Provision and manage cloud infrastructure declaratively using Crossplane.

Community
Advanced
notquenotque
415

feature-design

Facilitate collaborative feature design discussions and generate design documents.

Community
Intermediate