agentleFS
bharathgnanabharathgnana/archdiagram/.claude/skills/architecture-diagram/SKILL.md

architecture-diagram

Skill1 starsChanged 18 days agoMITView on GitHub

Use for cloud system topology and service relationships where Azure, AWS, GCP, or Kubernetes vendor icons matter.

48 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use competitor-news-monitor, blocked-page-recovery 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.
  • Samin12Skill

    competitor-news-monitor

    Watch named companies for material news; cited digests.

    Also in 6 projects that use this

  • nobodyohm-webSkill

    blocked-page-recovery

    Recover blocked/paywalled/WAF'd pages via fallbacks.

    Also in 6 projects that use this

  • Samin12Skill

    document-to-action-items

    Extract cited obligations, deadlines, tasks from documents.

    Also in 6 projects that use this

  • VercelSkill

    agent-desktop-linux

    Linux platform guide for the agent-desktop CLI. Lists per command group what works on X11 and on Wayland, how to check the AT-SPI accessibility bus, the first-contact gotchas (app names, Chromium and Electron flags, headed focus, blocked key combos), and where to find lifecycle, screenshot, clipboard, tray, notification and troubleshooting details. Triggers on: "linux desktop automation", "AT-SPI tree", "automate GNOME app", "agent-desktop on Linux", "accessibility bus not available", "empty supported_surfaces", "wayland screenshot consent", or any Linux GUI interaction task.

    Also in 3 projects that use this

  • VercelSkill

    agent-desktop-macos

    macOS platform guide for the agent-desktop CLI. Use for desktop automation on macOS: granting Accessibility and Screen Recording permission (TCC), what headed mode does on macOS (physical-first click, type and scroll), surfaces (menu, menubar, sheet, popover, alert, dock, menu-bar-extras), menu bar apps and system panels with no window, Notification Center, Chromium and Electron apps including launch --cdp, and fixing PERM_DENIED, empty accessibility trees, ACTION_FAILED and APP_UNRESPONSIVE.

    Also in 3 projects that use this

  • michaellam26Skill

    sdlc-review

    Trigger stage-specific reviews for an SDLC project and save results to reviews/

    Also in 5 projects that use this

  • +2 more from vercel-labs
  • +1 more from Samin12

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill for systems and service topology.

    line 8
  2. Very specific:

    Use kind: "data" on an edge for a data transfer.

    line 15

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

Use this skill for systems and service topology. Choose a service from the catalog for each icon node. Use groups for platform boundaries and edges for dependencies or data transfer. Use process-flow for operational sequences.

Spec rules

  • Each node has a unique string id and exactly one service or shape.
  • A service may be a canonical ID such as azure.app_service, an alias, or an unambiguous name. Run catalog search and use --strict to reject unresolved services.
  • direction is LR, RL, TB, or BT. x and y pin a node. group must name a defined group.
  • Use kind: "data" on an edge for a data transfer. Give edges labels when the relationship needs explanation.
{"title":"Azure web app","direction":"LR","nodes":[{"id":"web","service":"azure.app_service","label":"Web app"},{"id":"storage","service":"azure.storage_account","label":"Storage"}],"edges":[{"source":"web","target":"storage","kind":"data","label":"uploads"}]}

Render and inspect

On first use run python -m tools.bootstrap --icons. Run python -m archdiagram.cli catalog search "app service", then python -m archdiagram.cli validate spec.json --strict. Render with python -m archdiagram.cli render spec.json -f drawio -o out/architecture.drawio; change -f to svg, html, pdf, pptx, or vsdx as needed. PDF needs python -m tools.bootstrap --pdf. Open the output, check labels, edges, and icons, revise the spec, and render again. Via MCP, use list_icons, validate_spec, then generate_diagram.

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.