architecture-diagram
Skill2 starsChanged 17 days agoApache-2.0View on GitHub
Create or update architecture and flow diagrams for agent-desktop's docs site in apps/docs. Use when a docs page needs a diagram of components, data flow, or a command pipeline, or when an existing diagram in apps/docs/public/desktop/diagrams changes.
48 other projects use a version of this; 2 new projects in the last 4 weeks, against 0 the 4 before.
Adopted by
Surging: 2 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- bharathgnana/archdiagramtheir own version, first seen Nov 16, 2026
- rodos4312/Meu-Agenttheir own version, first seen Nov 15, 2026
- ottuck/diagram-polishtheir own version, first seen Nov 15, 2026
- incredible404-rgb/zstacktheir own version, first seen Nov 15, 2026
- NousResearch/hermes-agenttheir own version, first seen Nov 13, 2026
- nohemi20231/design-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use teams-meeting-pipeline, touchdesigner-mcp and 5 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.
john-data-chenSkillteams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
Also in 8 projects that use this
john-data-chenSkilltouchdesigner-mcp
Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.
Also in 5 projects that use this
Tommy-ywSkillsongwriting-and-ai-music
Songwriting craft, AI music generation prompts (Suno focus), parody/adaptation techniques, phonetic tricks, and lessons learned. These are tools and ideas, not rules. Break any of them when the art calls for it.
Also in 9 projects that use this
mae616Skillp5js
p5.js(クリエイティブコーディング)のProcessing由来「コードでスケッチ」思想を軸に、setup/drawループ・座標系・インタラクション・パフォーマンス最適化を整理する。p5.js、Processing、クリエイティブコーディング、ジェネラティブアート、インタラクティブ表現、ビジュアルプログラミング、Canvas描画、パーティクル、フラクタル、ノイズ表現に関する相談で必ず使うこと。ユーザーが「コードでアート」「動くビジュアル」「インタラクティブな描画」と言った場合にも適用する。
Also in 9 projects that use this
Tommy-ywSkillpopular-web-designs
54 production-quality design systems extracted from real websites. Load a template to generate HTML/CSS that matches the visual identity of sites like Stripe, Linear, Vercel, Notion, Airbnb, and more. Each template includes colors, typography, components, layout rules, and ready-to-use CSS values.
Also in 9 projects that use this
math-incSkillfindmy
Track Apple devices and AirTags via FindMy.app on macOS using AppleScript and screen capture.
Also in 9 projects that use this
- +1 more from Tommy-yw
Other versions48 projects use a version of this.
Word for word · 2
- lahfir/agent-desktop★ 24k100% same
- vercel-labs/agent-desktop★ 24k100% same
Edited · 0
None found.
Wrote their own version · 46
- NousResearch/hermes-agent★ 264ksame name
- Cocoon-AI/architecture-diagram-generator★ 7.4ksame name
- Tommy-yw/RunbookHermes★ 546same name
- Mathews-Tom/armory★ 340same name
- konraddzbik/architecture-diagram-skill★ 143same name
- proyecto26/system-design-skills★ 118same name
- microsoft/github-copilot-modernization★ 48same name
- wundercorp/loki★ 28same name
- ulises-jeremias/agent-toolkit★ 20same name
- Nanford/Nanford-skills★ 18same name
36 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- technical-writerSkill
- agent-desktop-ffiSkill
- agent-desktop-linuxSkill
- agent-desktop-macosSkill
- agent-desktopSkill
- agent-desktop-windowsSkill
- jev-desktopSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 43 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Read the code before drawing.
- Very specific: line 24
Use the identifiers from the code as labels (PlatformAdapter, RefStore) and put the mechanism in the gray second line (AX API, UI …
- Very specific: line 40
If apps/docs has no Diagram component yet, add components/geistdocs/diagram.tsx: a client component that renders the file in a lazy iframe …
- Very specific: line 44
Keep a text version of the flow next to the diagram on the page, such as a short list or code block with the same components and order.
- Very specific: line 51
Run pnpm build in apps/docs.
- Distinctive: line 52
Stop the dev server and the proxy, and close the browser session.
“Common” is measured: kept by at least 6 in 10 of the 43 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.
Files
Architecture diagram
Diagrams are standalone HTML files that the docs embed with the Diagram component. Follow the technical-writer skill for any prose.
Folder convention
- One folder per diagram:
apps/docs/public/desktop/diagrams/<name>/index.html, served at/desktop/diagrams/<name>/index.html.<name>is a short kebab-case slug. Keep it under/desktop: agent-browser.dev routes only/desktoppaths to this app. apps/docs/proxy.tsreturns 404 for/desktoppaths that are not docs pages, so its matcher must excludedesktop/diagrams/, as it does fordesktop/favicon.ico.- The file is standalone: inline CSS, one inline SVG, no external requests. Start from references/template.html.
- The visual tokens are in references/style.md. Reuse them so every diagram looks the same.
- The theme comes from
?theme=lightor?theme=dark. Without the parameter the diagram followsprefers-color-schemeand defaults to dark. - Give the SVG a
<title>and a<desc>that states the whole flow in words.
Draw the real mechanism
- Read the code before drawing. For observation and refs, read
crates/core/src/snapshot/,crates/core/src/refs/, and the command incrates/core/src/commands/. For platforms, read thePlatformAdaptertrait incrates/core/src/adapter/and the platform crate. Draw only components, names, and directions you can point to in source. - Use the identifiers from the code as labels (
PlatformAdapter,RefStore) and put the mechanism in the gray second line (AX API,UI Automation). - Draw one arrow per real data path. Label arrows that cross a boundary with the command, flag, or call (
snapshot --root). - Group components by where they run: an outer dashed container for a machine, a nested panel for a process. Put the calling agent outside.
- Lay the flow out top to bottom: the entry point at the top, then each layer or step on its own row below the one that calls it, so arrows point down. Put branches side by side on one row (the three platform crates, the error outcomes of a step) and route loops back up along the right side. Use left-to-right only for a before-and-after comparison of state, such as the re-drill panels.
- Mark the entry point of the flow with the highlighted circle node, at the top. Use it once, and give it the icon of what starts the flow (
robotfor the calling agent,linkfor a ref,refresh-counter-clockwisefor a re-drill), never a generic globe. - Give every node and container header an icon that names what it is. Use the Geist icon set and the OS marks listed in references/style.md. Do not draw your own icons or reuse one icon for unrelated nodes.
- Lay it out for the 720px docs column at 1:1 scale (see style.md) and keep it to 12 nodes or fewer. Move detail to the page text.
Embed it
<Diagram name="snapshot-drill-down" title="Skeleton snapshot and drill-down" aspectRatio="720 / 448" />aspectRatio is the SVG viewBox width and height. The component passes the site theme to the iframe.
If apps/docs has no Diagram component yet, add components/geistdocs/diagram.tsx: a client component that renders the file in a lazy iframe from /desktop/diagrams/<name>/index.html and appends ?theme= from next-themes. Register it in components/geistdocs/mdx-components.tsx.
Text version
Keep a text version of the flow next to the diagram on the page, such as a short list or code block with the same components and order. Readers of the .md route, agents, and screen readers depend on it.
Check it
- In
apps/docs, runpnpm devand, in a second terminal,pnpm exec microfrontends proxy microfrontends.json --local-apps agent-desktop. - Open
http://localhost:3024/desktop/diagrams/<name>/index.htmland the same URL with?theme=lightat 1440x900. Look for clipped text, labels that run past their node, overlapping labels, arrows that miss their node, icons that do not match their node, and unreadable gray text. Labels that fit in Geist can overflow in a fallback font, so leave at least 20 of room after the longest label. - Open the docs page and check the diagram in both site themes.
- Run
pnpm buildinapps/docs. - Stop the dev server and the proxy, and close the browser session.
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
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.

