agentleFS
letscooktech-studioletscooktech-studio/outcomelab/skills/system-architect/SKILL.md

system-architect

Skill7 starsChanged 6 days agoMITView on GitHub

Design or review software system architectures with explicit requirements, trade-offs, failure modes, and validation plans. Use for new systems, major integrations, scaling plans, architecture decision records, and technical design reviews.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use webapp-testing, git-workflow and 3 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.
  • JetBrainsSkill

    webapp-testing

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 5 projects that use this

  • MicrosoftSkill

    mcp-builder

    Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 2

    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:

    No component exists without an owner, failure behavior, and operational signal.

    line 26
  2. Distinctive:

    No synchronous dependency is added without timeout, retry, idempotency, and fallback reasoning.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 27 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

System Architect

Apply the shared OutcomeLab skill standard for evidence, verification, risk, benchmarking, and improvement.

Produce an architecture a team can implement, operate, and reverse when assumptions change.

Workflow

  1. Extract functional requirements, quality attributes, constraints, growth assumptions, and non-goals.
  2. Model components, data flows, trust boundaries, dependencies, and ownership. Trace critical paths end-to-end.
  3. Compare at least two viable designs where the choice is material; quantify latency, reliability, consistency, cost, and delivery trade-offs.
  4. Design failure handling, observability, capacity limits, rollout/rollback, and data migration before selecting a path.
  5. Record decisions as reversible or hard-to-reverse, with triggers for revisiting them.

Output contract

Return a context diagram, component/data-flow design, interface contracts, ADR table, SLOs, capacity assumptions, threat considerations, delivery phases, and validation plan. Label estimates and unknowns.

Quality gates

  • No component exists without an owner, failure behavior, and operational signal.
  • No synchronous dependency is added without timeout, retry, idempotency, and fallback reasoning.
  • Include a rollback path for every stateful release.

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.