Interactive architecture diagrams in Simform's brand, with official Azure icons, ready to embed in SharePoint.
Current stable version: v3.2.0 (upstream Archify 3.2.0 plus the Simform changes below). See Changelog.
Describe a system to your AI agent. Simform Archify turns it into one checked, self-contained HTML file you can explore (click a node, trace a route, switch light and dark) and export as an image. It is Simform's fork of Archify by tt-a1i.
| Upstream Archify | Simform Archify | |
|---|---|---|
| Look | Slate and neon, JetBrains Mono | Simform design system: lavender canvas, plum text, Inter, one red accent. Light by default, dark available. |
| Icons | 107 brand marks (AWS, GitHub, ...) | 118 brand marks (adds Qdrant, LangChain, LangGraph, LlamaIndex, Agno, CrewAI, Milvus, Neo4j, NGINX, GraphQL, Celery), 1,097 official Microsoft icons (Azure, Microsoft 365, Entra, Fabric, Dynamics 365) and 49 generic icons for API servers, queues, users and the like |
| SharePoint | Not addressed | Embed guide and a tested iframe mode |
| Skill name | archify |
simform-archify |
| Update notices | Point at upstream releases | Off by default |
Everything else (ten diagram types, validation, layout repair, the interactive viewer, exports) is upstream's. Each choice and how to reverse it is in DECISIONS.md.
Simform Archify is an agent skill. It needs Node 18 or later (and Chrome for its browser check) and works with Claude Code, Claude Desktop, Cursor, Codex CLI and OpenCode.
This repository is also a Claude plugin marketplace. In Claude Code:
/plugin marketplace add SimformSolutionsPvtLtd/simform-archify
/plugin install simform-archify@simform-archify
In Claude Desktop (Cowork and claude.ai), open Customize > Plugins > Add > Add marketplace, enter SimformSolutionsPvtLtd/simform-archify, then install simform-archify. Update the plugin from the same place. Then ask for a diagram, or run the skill by name.
npx -y skills@latest add SimformSolutionsPvtLtd/simform-archify --list --full-depthCheck that the list shows exactly one skill named simform-archify, then install it for your agent (drop --global for this project only):
npx -y skills@latest add SimformSolutionsPvtLtd/simform-archify --skill simform-archify --agent claude-code --global --copy --yesIf the repository is private and the installer cannot clone it, clone it yourself and install from the checkout:
git clone git@github.com:SimformSolutionsPvtLtd/simform-archify.git
npx -y skills@latest add ./simform-archify --skill simform-archify --agent claude-code --global --copy --yesUse --copy for a local checkout so the install does not point into a folder you might move. Verify the install (the path is where the installer put the skill):
node <installed-path>/bin/archify.mjs doctorAsk your agent in plain language:
Use Simform Archify to diagram our web platform on Azure: users reach Front Door,
which routes to App Service; the app reads Key Vault secrets, queries Azure SQL
and queues jobs on Service Bus, drained by Functions. Entra ID signs users in.
For an architecture diagram the agent first asks which style to follow: Microservices (the default), N-tier, Web-queue-worker, Event-driven, Big data, Big compute, or "work it out from the codebase", where it reads your repository and picks the best style or a combination. The styles are the ones in the Azure Architecture Center guide.
The agent writes a JSON description, runs finalize (validation, layout checks, a real-browser check) and gives you an HTML file. Continue in conversation: "add Cosmos DB", "highlight the sign-in path", "show it dark".
Try the bundled example without an agent:
node archify/bin/archify.mjs render architecture archify/examples/azure-web-platform.architecture.json azure-web-platform.html --quality showcasePut an icon on a node with the brand field, by service name or alias:
{ "id": "kv", "type": "security", "label": "Key Vault", "sublabel": "secrets",
"brand": "key vault", "pos": [490, 120], "size": [210, 76] }| Pack | Prefix | Icons | Examples |
|---|---|---|---|
| Azure | azure- |
639 | App Services, Kubernetes Services, SQL Database, Front Door |
| Microsoft 365 | m365- |
360 | SharePoint, Teams, Project and Planner glyphs |
| Microsoft Entra | entra- |
7 | Entra ID, Verified ID, Private Access |
| Microsoft Fabric | fabric- |
75 | Lakehouse, Pipeline, Power BI, OneLake |
| Dynamics 365 | d365- |
16 | Sales, Finance, Business Central |
| Generic (Lucide) | generic- |
49 | API server, Queue, Cache, Worker, User, Browser, Gateway |
Named technologies (PostgreSQL, Redis, MongoDB, Qdrant, React, Python, TypeScript, LangChain, LlamaIndex, Agno ...) use their built-in brand mark, for example "brand": "qdrant", drawn at the same size as the Azure icons. Components that are not Microsoft services or a named technology (users, API servers, queues, caches, workers, gateways, agents) use the generic pack, for example "brand": "queue". In an architecture diagram that already shows Azure icons, a node with no brand gets a generic icon inferred from its label and type; set SIMFORM_GENERIC_ICONS=off to switch that off. Generic icons are Lucide line art (ISC licence) drawn in the node's colour. The Microsoft icons are never recoloured.
Find an id with node archify/bin/archify.mjs brands "service bus". Aliases such as aks, app service, azure sql, front door and entra work too. An unknown name fails validation and lists the closest icons; it never falls back to a lookalike.
Rules (also in references/azure-icons.md, which the skill reads):
- Label the node with the service name. Microsoft's terms ask for the name beside the icon.
- Microsoft icons are never recoloured, cropped or reshaped, and must not stand for a non-Microsoft product. Use a generic icon for those.
- Architecture diagrams draw the icon at 48px in a left gutter with the label beside it. Size icon nodes about 210×76 or larger; narrower nodes fail validation rather than clip the label.
- Workflow, sequence, data-flow and lifecycle diagrams keep a 24px corner icon, so give those nodes at least 160px of width.
- Icons work on architecture, workflow, sequence, data-flow and lifecycle diagrams.
The icons are unmodified copies of Microsoft's downloads. Sources, archive hashes and licence terms are in archify/icon-packs/SOURCES.md. To refresh them:
npm --prefix archify run sync:icon-packs # fetch latest from Microsoft's pages, rewrite icon-packs/
npm --prefix archify run check:icon-packs # verify hashes and SVG safety, offlineThe default theme applies the Simform design system: canvas #f4f1fb, white panels, text #1a1024, Inter, and brand red #e0314c for the one emphasised flow (coral #ef5366 in dark mode). Node categories use the purple, teal, orange and neutral ramp, never red. DECISIONS.md D-04 lists every colour.
To change the look, edit the token blocks at the top of viewer/viewer.css, then regenerate the viewer template and re-render the examples:
node scripts/generate-viewer.mjs
npm --prefix archify run render:examplesarchify/assets/template.html is generated; never edit it by hand.
A diagram is one self-contained HTML file with no network requests. SharePoint will not run it from a document library, so host it on an HTTPS site (an Azure Storage static website or Static Web Apps works) and embed it with the Embed web part:
<iframe src="https://YOUR-HOST/azure-web-platform.html?present=1&theme=light"
title="Azure web platform architecture" width="100%" height="680"
style="border:0" loading="lazy" allow="fullscreen"></iframe>?present=1 keeps the diagram interactive and fills the frame; ?embed=1 shows the bare diagram. The host must allow framing by your SharePoint origin, and a site admin must allow the host under HTML Field Security. Full steps, parameters and caveats: archify/references/sharepoint-embed.md. This was checked in a sandboxed iframe in headless Chrome, not in a live tenant.
npm ci
npm --prefix archify ci
npm test # core smoke: ten diagram types through the public CLI
npm run test:focus -- test/icon-packs.test.mjs
npm run test:generated # viewer, brand marks, icon packs, validators, golden examples
npm run test:full # everythingRead CONTRIBUTING.md before changing shared behaviour. After changing anything under viewer/, run node scripts/generate-viewer.mjs. After changing the skill's files, rebuild the package archive with scripts/build-zip.sh (it needs Node 22).
Layout of what this fork added:
| Path | Purpose |
|---|---|
archify/icon-packs/ |
Curated Microsoft SVGs, catalog.json, aliases.json, SOURCES.md, terms files |
archify/scripts/sync-icon-packs.mjs |
Download, curate and verify the icon packs |
archify/renderers/shared/icon-packs.mjs |
Catalogue lookup, SVG safety check, id namespacing |
archify/renderers/shared/generic-icons.mjs |
Picks a generic icon from a node's label and type |
archify/references/architecture-styles.md |
The style question and how each style is drawn |
archify/references/azure-icons.md, sharepoint-embed.md |
Skill instructions for icons and embedding |
archify/examples/azure-web-platform.architecture.json |
Azure sample |
DECISIONS.md |
Every fork decision, with how to reverse it |
git remote add upstream https://github.com/tt-a1i/archify.git
git fetch upstream
git merge upstream/mainExpect conflicts in viewer/viewer.css, viewer/template.source.html, archify/SKILL.md and archify/renderers/shared/brand-marks.mjs. Resolve them, run node scripts/generate-viewer.mjs rather than merging archify/assets/template.html, re-render the examples, and rerun npm run test:generated. See D-16 in DECISIONS.md.
Simform Archify is distributed under the Apache License 2.0 (LICENSE, NOTICE). It is derived from tt-a1i/archify, which originated from Cocoon-AI/architecture-diagram-generator; their copyright notices are preserved. Changes by Simform are recorded in git history and DECISIONS.md.
Third-party material: Inter (SIL Open Font License 1.1, archify/assets/Inter-OFL.txt), Simple Icons marks (see THIRD_PARTY_NOTICES.md), and Microsoft icons under Microsoft's terms (architecture diagrams, training material and documentation; not to be altered). Microsoft, Azure, Entra, Fabric, Dynamics 365 and Microsoft 365 are trademarks of Microsoft Corporation; their use here does not imply endorsement.
