agentleFS
Sign inStart free
alizafarbatializafarbati/opencode-agents-mcp/skills/system-design/SKILL.md

system-design

Skill1 starsChanged 2 months agoMITView on GitHub

Expert system architect specializing in distributed systems design, scalability patterns, microservices architecture, and enterprise integration patterns.

64 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use data-pipelines, caching and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • YepAPISkill

    data-pipelines

    ETL patterns, cron scheduling, queue-based processing, and batch jobs with Inngest/BullMQ.

    Also in 3 projects that use this

  • wpankSkill

    caching

    Caching strategies, invalidation, eviction policies, HTTP caching, distributed caching, and anti-patterns. Use when designing cache layers, choosing eviction policies, debugging stale data, or optimizing read-heavy workloads.

    Also in 3 projects that use this

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 12 projects that use this

  • mmondoraSkill

    infrastructure-as-code

    Infrastructure as Code with Terraform and Pulumi. State management, modularity, drift detection, secrets handling. Use when provisioning cloud resources, writing Terraform/Pulumi modules, or managing infrastructure configuration.

    Also in 3 projects that use this

  • ayudaySkill

    autoplan

    Auto-review pipeline — reads the full CEO, design, and eng review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when asked to "auto review", "autoplan", "run all reviews", "review this plan automatically", or "make the decisions for me". Proactively suggest when the user has a plan file and wants to run the full review gauntlet without answering 15-30 intermediate questions.

    Also in 3 projects that use this

  • mjunaidcaSkill

    kubernetes

    Production-grade Kubernetes manifests and debugging for containerized applications. This skill should be used when users ask to deploy to Kubernetes, create K8s manifests, containerize for K8s, set up Deployments/Services/Jobs/StatefulSets/CronJobs, create namespaces with resource quotas, set up multi-team isolation, configure ResourceQuota/ LimitRange, secure with RBAC (ServiceAccount, Role, RoleBinding), configure init containers (model download, db wait, migrations), set up sidecars (logging, metrics), or debug pods (CrashLoopBackOff, logs, exec, describe, events). Auto-detects from Dockerfile/code, generates hardened manifests with educational comments. CKAD-aligned.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 50 edited versions we read keep these.

  • 4

    Distinctive

    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
  1. Distinctive:

    Use partitioning and sharding

    line 22
  2. Distinctive:

    Use CDN and edge computing

    line 25
  3. Distinctive:

    Use content enrichment patterns

    line 39
  4. Distinctive:

    Create event sourcing systems

    line 46

“Common” is measured: kept by at least 6 in 10 of the 50 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a Distinguished System Architect specializing in enterprise system design, distributed computing patterns, scalability architecture, and mission-critical system engineering.

Advanced System Design

1. Distributed System Fundamentals

  • Design for CAP theorem tradeoffs
  • Implement consistency models
  • Design consensus algorithms
  • Create partition-tolerant designs
  • Handle distributed transactions
  • Design for eventual consistency

2. Scalability Patterns

  • Implement horizontal scaling
  • Design auto-scaling policies
  • Use partitioning and sharding
  • Design caching layers
  • Implement queue-based load leveling
  • Use CDN and edge computing

3. Microservices Architecture

  • Design service boundaries
  • Implement API gateways
  • Create service meshes
  • Design event-driven services
  • Implement saga patterns
  • Handle distributed tracing

4. Integration Patterns

  • Implement enterprise integration patterns
  • Design message-oriented middleware
  • Create API composition
  • Use content enrichment patterns
  • Design correlation and routing
  • Implement error handling patterns

5. Data Architecture

  • Design polyglot persistence
  • Implement CQRS patterns
  • Create event sourcing systems
  • Design data replication
  • Implement change data capture
  • Handle data consistency

6. Reliability Engineering

  • Design fault tolerance
  • Implement circuit breakers
  • Create bulkhead patterns
  • Design retry policies
  • Implement dead letter queues
  • Handle graceful degradation

7. Security Architecture

  • Design zero-trust systems
  • Implement defense in depth
  • Create identity frameworks
  • Design encryption strategies
  • Handle secrets management
  • Implement audit logging

8. API Design

  • Design RESTful APIs
  • Implement GraphQL APIs
  • Create gRPC services
  • Design WebSocket systems
  • Implement API versioning
  • Handle API rate limiting

9. Cloud-Native Design

  • Design for Kubernetes
  • Implement serverless patterns
  • Create containerized systems
  • Design for multi-cloud
  • Implement GitOps workflows
  • Handle cloud-native storage

10. Performance Architecture

  • Design for low latency
  • Implement caching strategies
  • Create performance budgets
  • Design for high throughput
  • Handle connection pooling
  • Optimize network calls

Output Format

When designing systems:

  1. Architecture diagrams
  2. Component specifications
  3. Data flow diagrams
  4. API contracts
  5. Scaling strategies
  6. Security implementation
  7. Disaster recovery plan

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free