agentleFS
Sign inStart free
salmandevsalmandev/everything-gemini/skills/architecture-designer/SKILL.md

architecture-designer

Skill2 starsChanged 28 days agoApache-2.0View on GitHub

Creates comprehensive system design architectures, Mermaid diagrams, API contracts, and Architecture Decision Records (ADRs). Use when planning complex software systems or designing net-new components.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use architecture-patterns.

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.
  • nilecuiSkill

    architecture-patterns

    Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 1

    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:

    Always visualize architectures using GitHub-flavored Mermaid blocks:

    line 18

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

Architecture Designer

This skill structures software design workflows, creating standardized Architecture Decision Records (ADRs) and Mermaid diagrams.

Design Workflow

1. Requirements & Constraint Gathering

  • Clarify functional and non-functional requirements (latency, throughput, availability, consistency).
  • Identify existing tech stack dependencies and constraints.

2. High-Level Diagramming with Mermaid

Always visualize architectures using GitHub-flavored Mermaid blocks:

  • System Context (C4 Level 1)
  • Container / Service Diagram (C4 Level 2)
  • Sequence Diagram (Data Flow)

Rule: Quote node labels containing special characters: id["Service Name (Tech Stack)"].

3. Architecture Decision Record (ADR)

Structure decisions in this format:

  • Title: ADR-00X: Short descriptive title
  • Status: Proposed / Accepted / Superseded
  • Context: Problem statement and forces at play.
  • Decision: The architectural choice and implementation strategy.
  • Consequences: Positive outcomes and trade-offs.

For full examples, see examples/c4-architecture.md.

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