agentleFS
Sign inStart free
int2t05int2t05/engineering-skills/skills/03-design/architecture/SKILL.md

architecture

Skill3 starsChanged 30 days agoMITView on GitHub

Design or audit system boundaries and consequential technical decisions. Triggers on "system design", "架构设计".

136 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use intelligent-routing, bash-linux and 10 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.
  • SKB3002Skill

    intelligent-routing

    Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

    Also in 6 projects that use this

  • xenitV1Skill

    bash-linux

    Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

    Also in 8 projects that use this

  • xenitV1Skill

    red-team-tactics

    Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.

    Also in 8 projects that use this

  • SKB3002Skill

    nextjs-react-expert

    React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.

    Also in 3 projects that use this

  • +8 more from xenitV1

The file

Create a free account to mount
Files
SKILL.md

Architecture

When to use

  • Design or audit system boundaries and consequential technical decisions.

Not for: spec for behavior; codebase-design for existing module boundaries.

Steps

  1. Extract confirmed behavior, real constraints and operational context; do not invent quality thresholds.
  2. Investigate comparable implementations and current official docs for consequential choices; compare complexity, failure modes and operating costs.
  3. Define components, trust boundaries, ownership, contracts and recovery using the simplest adequate architecture.
  4. Record significant decisions and rejected alternatives; prepare TECH and risk-based human review before dependent implementation.

Output: Suggested paths, subject to human audit: docs/TECH.md; optionally docs/vX.Y/tech.md and docs/design/adr/NNNN-slug.md.

Verify

  • Boundaries and failure paths fit requirements; significant decisions have evidence, trade-offs and review criteria.

References

  • engineering-principles.md — shared decision boundaries, scope and verification.
  • mermaid-diagrams.md — Mermaid syntax for architecture diagrams
  • references/tech-audit-guide.md — reference-first discipline, the audit→confirm→revise→mature lifecycle, and the TECH-doc AUD catalog with table formats
  • references/nfr-checklist.md — NFR categories (scalability, performance, availability, security, reliability, cost) with targets
  • references/architecture-patterns.md — pattern comparison (monolith, microservices, event-driven, CQRS, serverless)
  • references/database-selection.md — database types and decision matrix
  • references/system-design.md — full system design template
  • references/adr-template.md — ADR format, example, and naming convention
  • references/error-resilience.md — throw-vs-return, error propagation, retry/circuit-breaker, idempotency, fallback UX, error-to-message mapping
  • Human audit — artifact consent and review.

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