Run any Skill in Manus with one click

system-design

Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill system-design

Copy and paste this command into Claude Code to install the skill

Source

anthropics/knowledge-work-plugins

Stars19,014

Forks2,224

UpdatedFebruary 24, 2026 at 00:08

SKILL.md

readonly

name	system-design
description	Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.

System Design

Help design systems and evaluate architectural decisions.

Framework

1. Requirements Gathering

Functional requirements (what it does)
Non-functional requirements (scale, latency, availability, cost)
Constraints (team size, timeline, existing tech stack)

2. High-Level Design

Component diagram
Data flow
API contracts
Storage choices

3. Deep Dive

Data model design
API endpoint design (REST, GraphQL, gRPC)
Caching strategy
Queue/event design
Error handling and retry logic

4. Scale and Reliability

Load estimation
Horizontal vs. vertical scaling
Failover and redundancy
Monitoring and alerting

5. Trade-off Analysis

Every decision has trade-offs. Make them explicit.
Consider: complexity, cost, team familiarity, time to market, maintainability

Output

Produce clear, structured design documents with diagrams (ASCII or described), explicit assumptions, and trade-off analysis. Always identify what you'd revisit as the system grows.

More from this repository

same repository

smb-onboard

anthropics/knowledge-work-plugins

Claude as the trainer. Walks an SMB owner through connecting their first two tools, runs one recipe to prove immediate value, interviews them about their business (industry, size, top three headaches), stores that context persistently so every other skill benefits, and sets a weekly check-in cadence. Use when the owner is getting started or says any of: "set me up," "setup," "help me get set up," "get started," "help me get started," "get me started," "what can you do," "I'm new to this," or is in their first session.

2026-05-1319.0k

business-pulse

anthropics/knowledge-work-plugins

Produces a one-page cross-functional business snapshot for SMB owners — cash position (QuickBooks), sales trend (PayPal/Square), pipeline movement (HubSpot), this week's commitments (Calendar), urgent watch-list items (Gmail/Slack), and the single most important thing needing attention today. Proactively tries every available connector and gracefully scopes to whatever is connected — one connector gives a partial pulse; the full stack gives the full picture. Trigger when the user asks how the business is doing, wants a snapshot, a weekly summary, a Monday brief, or says anything like "what am I missing" or "catch me up on the business."

2026-05-1219.0k

call-list

anthropics/knowledge-work-plugins

Ranks the top-5 leads most worth calling today, supplies talking points from email history, blocks time on the calendar, and drafts follow-up messages. Accepts optional count and date arguments.

2026-05-1219.0k

canva-creator

anthropics/knowledge-work-plugins

Takes an approved content brief and executes a campaign end-to-end: builds the posting calendar, generates Canva designs for social posts, drafts caption and email copy, and stages social sends in HubSpot. Canva is used for social posts only (Instagram, Facebook, X, LinkedIn) — email content is drafted as plain text and surfaced inline for the owner to send from their own tool. Every step requires explicit owner approval. Use when the user says "make the content," "generate the posts," "create the assets," "turn this into a campaign," or hands off an approved brief for execution.

2026-05-1219.0k

cash-flow-snapshot

anthropics/knowledge-work-plugins

Reads AR/AP, historical cash timing, and known fixed costs from QuickBooks, PayPal, Stripe, or Square — or a CSV upload — and produces a 30/60/90-day cash flow forecast with percentage-variance confidence bands and named risk flags. Delivers a chat summary and a downloadable XLSX. Use when the user asks "forecast my cash flow," "will I make payroll," mentions "runway," or says "cash crunch." Falls back to CSV upload when no connector is live.

2026-05-1219.0k

close-month

anthropics/knowledge-work-plugins

Closes the month — reconciles QB vs payment processors, flags gaps, writes P&L narrative, exports close packet. Accepts optional month and save-to arguments.

2026-05-1219.0k

Source

anthropics

anthropics/knowledge-work-plugins

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	system-design
description	Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.

System Design

Help design systems and evaluate architectural decisions.

Framework

1. Requirements Gathering

Functional requirements (what it does)
Non-functional requirements (scale, latency, availability, cost)
Constraints (team size, timeline, existing tech stack)

2. High-Level Design

Component diagram
Data flow
API contracts
Storage choices

3. Deep Dive

Data model design
API endpoint design (REST, GraphQL, gRPC)
Caching strategy
Queue/event design
Error handling and retry logic

4. Scale and Reliability

Load estimation
Horizontal vs. vertical scaling
Failover and redundancy
Monitoring and alerting

5. Trade-off Analysis

Every decision has trade-offs. Make them explicit.
Consider: complexity, cost, team familiarity, time to market, maintainability

Output

Produce clear, structured design documents with diagrams (ASCII or described), explicit assumptions, and trade-off analysis. Always identify what you'd revisit as the system grows.