agentleFS
imMamdouhaboammarimMamdouhaboammar/dokion/skills/archify/SKILL.md

archify

Skill1 starsChanged 3 months agoMITView on GitHub

Generates clean, interactive, self-contained system architecture, data-flow, sequence, and component diagrams in HTML, SVG, PNG, and WebP formats. Use when analyzing repository architecture, mapping trust boundaries, documenting data flow, or generating visual evidence for Dokion hardening reports.

39 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use archify-review and hyperframes.

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

    archify-review

    Review Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions. Use for issue triage, change reviews, and code quality assessments.

    Also in 3 projects that use this

  • OpenAISkill

    hyperframes

    Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions in HyperFrames HTML. Use when asked to build any HTML-based video content, add captions or subtitles synced to audio, generate text-to-speech narration, create audio-reactive animation (beat sync, glow, pulse driven by music), add animated text highlighting (marker sweeps, hand-drawn circles, burst lines, scribble, sketchout), or add transitions between scenes (crossfades, wipes, reveals, shader transitions). Covers composition authoring, timing, media, and the full video production workflow. For CLI commands (init, lint, preview, render, transcribe, tts) see the hyperframes-cli skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 37 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    When running within a Dokion Playbook, archify produces visual evidence artifacts saved to .dokion/evidence/ or .dokion/reports/ to support …

    line 10
  2. Very specific:

    When executing a stage in .dokion/playbook.json that invokes archify:

    line 35
  3. Very specific:

    Read package manifests (package.json, Cargo.toml, go.mod, pyproject.toml, etc.).

    line 38
  4. Very specific:

    Write the HTML diagram file to .dokion/evidence/architecture.html or .dokion/reports/architecture.html.

    line 43
  5. Distinctive:

    Ensure the diagram includes:

    line 44

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

Archify - Interactive System Architecture & Diagram Engine

archify is an agent-native skill designed to produce interactive, animated, self-contained architecture diagrams directly from codebase analysis or system specifications.

When running within a Dokion Playbook, archify produces visual evidence artifacts saved to .dokion/evidence/ or .dokion/reports/ to support audit and hardening evidence.


Capabilities & Output Formats

  1. Interactive HTML Diagrams:
    • Animated node flows, hover states, and expandable details.
    • Built-in Dark / Light theme toggle.
    • Zero external runtime dependencies (self-contained HTML).
  2. Static & Vector Exports:
    • SVG (vector format for documentation & READMEs).
    • PNG / WebP / JPEG (high-DPI renders for presentation).
  3. Diagram Types:
    • System Topology: Services, databases, queues, external APIs, and gateways.
    • Data Flow & Trust Boundaries: Untrusted boundaries, auth layers, DB access patterns.
    • Sequence & Workflow: Step-by-step API interactions, event queues, and state machines.
    • Dokion Playbook Pipelines: Visualizing stage sequences, sub-agent swarms, and release gates.

Execution Guidelines for Dokion Agents

When executing a stage in .dokion/playbook.json that invokes archify:

Step 1: Scan and Inspect Codebase

  • Read package manifests (package.json, Cargo.toml, go.mod, pyproject.toml, etc.).
  • Inspect main entry points, API routes, database schemas, and external integrations.
  • Identify component relationships, trust boundaries, and data flow pipelines.

Step 2: Generate Interactive Artifact

  • Write the HTML diagram file to .dokion/evidence/architecture.html or .dokion/reports/architecture.html.
  • Ensure the diagram includes:
    • Component nodes (Frontend, Backend, Database, Auth, External Services).
    • Data flow directional arrows with protocol labels (HTTP/REST, gRPC, WebSocket, SQL).
    • Theme toggling & interactive hover controls.

Step 3: Record Evidence in HARDENING.md

  • Record the generated artifact in .dokion/state.json and link it in HARDENING.md:
    ### Visual Architecture Evidence
    - Interactive Diagram: [.dokion/evidence/architecture.html](file://.dokion/evidence/architecture.html)
    - Vector SVG: [docs/architecture.svg](file://docs/architecture.svg)

Example Usage in Playbooks

{
  "id": "architecture-mapping-step",
  "capability": {
    "type": "skill",
    "id": "archify",
    "version": "1.0.0",
    "source": "tt-a1i/archify"
  },
  "responsibility": "Generate interactive architecture and data flow diagrams for repository audit.",
  "mode": "READ_WRITE",
  "permissions": {
    "read": ["**/*"],
    "write": [".dokion/evidence/architecture.html", "docs/architecture.svg", "HARDENING.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.