TypingMindTypingMindThe best frontend for AI
System Design Resilience Ops logo

System Design Resilience Ops

Community
HoangNguyen0403
system-design-resilience-ops

Make a design survivable and operable: eliminate single points of failure, pick failover topology, set RPO/RTO, define readiness signals and observability, choose a deployment and rollback strategy. Use when reviewing availability, planning DR, or deciding rollout mechanics.

Overview

PublisherHoangNguyen0403
Repositoryagent-skills-standard
Skill namesystem-design-resilience-ops
Stars
573
Forks
166
Bundled files
1
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by HoangNguyen0403 on GitHub. Read the source before you install it.

Installation

Install the System Design Resilience Ops AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/.agents/skills/system-design/system-design-resilience-ops
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git /tmp/agent-skills-standard
mkdir -p .claude/skills
cp -r /tmp/agent-skills-standard/.agents/skills/system-design/system-design-resilience-ops .claude/skills/system-design-resilience-ops
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable System Design Resilience Ops in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads System Design Resilience Ops on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so System Design Resilience Ops is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Resilience and Operations

Priority: P1 (HIGH)

A design is not done until its failure and its rollout are designed.

SPOF Elimination

  • Walk every component and ask what happens when exactly one instance dies, then when the whole zone dies.
  • Any component with one instance, one writer, or one shared config plane is a single point of failure. Name it or remove it.
  • Redundancy only helps when failure modes are independent: shared credentials, shared config, and a shared control plane cancel the benefit.
  • Blast radius: state which users or flows are affected per component failure, and cap it with cells, bulkheads, or per-tenant quotas.

Failover and Recovery

TopologyRecovery timeCostFits
Single region, multi-AZMinutes, automaticLowMost products
Active-passive across regionsMinutes to hours, drill-dependentMediumRegulated or high-value flows
Active-active across regionsSecondsHighGlobal low-latency, conflict-tolerant data
  • Set RPO (tolerable data loss) and RTO (tolerable downtime) as numbers before choosing a topology; the numbers pick the topology, not the reverse.
  • Untested failover is a hypothesis. Schedule a drill and record the measured RTO against the target.
  • Backups need a restore test. A backup that has never been restored is not a backup.

Observability

  • Instrument the four signals per service: traffic, error rate, latency percentiles, saturation.
  • Alert on user-visible symptoms and on error-budget burn rate, not on raw CPU.
  • Propagate a trace and correlation id across every hop, including queue messages.
  • Every alert needs an owner, a runbook link, and a defined next action; an alert nobody acts on is noise.

Rollout

StrategyBlast radiusRollbackCost
RollingGrows during the rollRoll forward or back, slowLow
Blue-greenFull switch at cutoverInstant switch backDouble capacity
CanarySmall cohort firstStop and drain the cohortNeeds routing plus metrics
Feature flagPer user or tenantInstant, no redeployFlag lifecycle debt
  • Schema and code deploy separately: expand, migrate, contract. Never ship a migration that only the new code can read.
  • Define the rollback trigger as a metric threshold and a time box before the deploy starts.

Anti-Patterns

  • No untested failover: no DR claim without a drill date and a measured RTO.
  • No unbounded retry: retries need budget, backoff with jitter, and a stop condition, or they amplify an outage.
  • No liveness probe on dependencies: a downstream outage must not restart the fleet.
  • No deploy without rollback: irreversible releases are outages waiting for a bad build.
  • No autoscaling without a floor and ceiling: unbounded scaling turns a bug into a bill.

References

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the System Design Resilience Ops AI skill do?

Make a design survivable and operable: eliminate single points of failure, pick failover topology, set RPO/RTO, define readiness signals and observability, choose a deployment and rollback strategy. Use when reviewing availability, planning DR, or deciding rollout mechanics.

Why use System Design Resilience Ops on TypingMind?

Because you install it once and use it with any model. System Design Resilience Ops is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install System Design Resilience Ops in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/.agents/skills/system-design/system-design-resilience-ops. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use System Design Resilience Ops?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with System Design Resilience Ops?

As many as you like. As long as a model supports skills, you can use System Design Resilience Ops with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the System Design Resilience Ops AI skill free?

Yes. It is published on GitHub by HoangNguyen0403 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
mattpocock logo

Wizard

mattpocock
CommunityPopular

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar…

22.3K
264.4K
2 files
View
affaan-m logo

Deployment Patterns

affaan-m
CommunityPopular

Flujos de trabajo de despliegue, patrones de pipeline CI/CD, contenedorización Docker, health checks, estrategias de rollback y listas de verificación de preparación para producción de aplicaciones…

39.1K
261.1K
Instructions
View
affaan-m logo

Docker Patterns

affaan-m
CommunityPopular

Patrones de Docker y Docker Compose para desarrollo local, seguridad de contenedores, networking, estrategias de volúmenes y orquestación de múltiples servicios.

39.1K
261.1K
Instructions
View
affaan-m logo

Architecture Decision Records

affaan-m
CommunityPopular

コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。

39.1K
261.1K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇