Home / wst2002 / claude-code-skills · GitHub

architecture-diagram SKILL.md skillA

architecture-diagram from wst2002/claude-code-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add wst2002/claude-code-skills/architecture-diagram@git:20261016.55bd98a

Pins git:20261016.55bd98a in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: wst2002/claude-code-skills
Path: skills/architecture-diagram/SKILL.md
Versions recorded: 2
Latest version: git:20261016.55bd98a, committed Oct 16, 2026
First version recorded: Oct 16, 2026
Size: 2,896 bytes
Repository stars: 3
License: MIT

Use when asked to draw, diagram or visualize a system, codebase, architecture, data flow, request flow, database ERD, deployment or sequence of calls, or to explain how a project fits together for onboarding or documentation.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Architecture Diagram

## Overview

Draw diagrams from the code, not from imagination. Pick the one view that answers the reader's question, keep it to what fits on a screen, and render it as Mermaid so it lives in the repo and shows on GitHub.

## Method

1. **Ask what question the diagram answers** (or infer it): "what are the parts?", "what happens when a user checks out?", "how is data stored?", "where does it run?".
2. **Pick the view:**

| Question | Diagram | Mermaid type |
|---|---|---|
| What are the main parts and how do they talk? | Container / component | `flowchart LR` |
| What happens step by step in one request? | Sequence | `sequenceDiagram` |
| What does the data look like? | ERD | `erDiagram` |
| Which states can an object be in? | State | `stateDiagram-v2` |
| Where does it run? | Deployment | `flowchart TB` with subgraphs per environment |

3. **Collect facts:** entry points, services and packages, external systems (databases, queues, third-party APIs) from config, `docker-compose`, infrastructure files, imports and HTTP clients. For a sequence, follow one real request through the code.
4. **Draw** with the rules below.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add wst2002/claude-code-skills/architecture-diagram@sha256:cec0b3958ef26887

The line at the top of this page pins the label git:20261016.55bd98a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_j7s5dfyewlnanvbk.svg)](https://markdownregistry.com/a/art_j7s5dfyewlnanvbk)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, all committed on Oct 16, 2026.

version	committed	commit	size	audit
git:20261016.55bd98a latest	2026-10-16	55bd98a	2,896 B	A	view · diff
git:20261016.bf68d6a	2026-10-16	bf68d6a	2,694 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (2896 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

wst2002/claude-code-skills · 3 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_j7s5dfyewlnanvbk
GET https://markdownregistry.com/api/v1/resolve?ref=wst2002/claude-code-skills/architecture-diagram
GET https://markdownregistry.com/api/v1/blob/cec0b3958ef26887f0ac1158cfa518e8149ecaffa8d43f6584cd0d43ad6253be

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from wst2002/claude-code-skills

proof-of-done SKILL.md skill

wst2002/claude-code-skills · plugins/proof-of-done/skills/proof-of-done/SKILL.md · Use before saying work is done, fixed, or complete after changing code. Run the project's checks, show their results…