agentleFS
roughboy99roughboy99/aiautobase-claude-skills/skills/go-diagrams/SKILL.md

go-diagrams

Skill2 starsChanged 3 months agoMITView on GitHub

Generate system architecture diagrams using the Go go-diagrams library. Outputs DOT files rendered to PNG via Graphviz. Best for infrastructure, microservices, and network topology diagrams.

  • Installs packages

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Create a file diagram.go:

    line 18
  2. Distinctive:

    Write the Go code

    line 77
  3. Distinctive:

    If go-diagrams is not installed, generate the equivalent Python diagrams or Mermaid code instead as a fallback — both achieve the same …

    line 83

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

GO-Diagrams Skill

The go-diagrams library (github.com/blushft/go-diagrams) creates architecture diagrams in Go.

Setup

go install github.com/blushft/go-diagrams@latest
# Also requires Graphviz for rendering

Basic Example

Create a file diagram.go:

package main

import (
    "github.com/blushft/go-diagrams/diagram"
    "github.com/blushft/go-diagrams/nodes/apps"
    "github.com/blushft/go-diagrams/nodes/gcp"
)

func main() {
    d, _ := diagram.New(diagram.Filename("ai-stack"), diagram.Label("AI Creator Stack"))

    claude := apps.ML.Pytorch("Claude Code")
    n8n    := apps.Network.Internet("n8n")
    ghost  := apps.Network.Internet("Ghost Blog")

    d.Connect(claude, n8n)
    d.Connect(claude, ghost)
    d.Render()
}
go run diagram.go
# Outputs: ai-stack.png

Microservices Example

package main

import (
    "github.com/blushft/go-diagrams/diagram"
    "github.com/blushft/go-diagrams/nodes/apps"
    "github.com/blushft/go-diagrams/nodes/aws"
)

func main() {
    d, _ := diagram.New(diagram.Filename("microservices"), diagram.Label("Video Pipeline"))

    intake   := apps.Network.Internet("API Gateway")
    ingest   := aws.Compute.Lambda("Ingest Service")
    render   := aws.Compute.Lambda("Render Service")
    publish  := aws.Compute.Lambda("Publish Service")
    storage  := aws.Storage.S3("Media Store")
    queue    := aws.Integration.Sqs("Job Queue")

    d.Connect(intake, ingest)
    d.Connect(ingest, queue)
    d.Connect(queue, render)
    d.Connect(render, storage)
    d.Connect(storage, publish)
    d.Render()
}

Workflow

  1. Understand the system/infrastructure the user wants to diagram
  2. Write the Go code
  3. Run: go run diagram.go
  4. The PNG renders automatically via Graphviz
  5. Show the user the result and iterate

Note

If go-diagrams is not installed, generate the equivalent Python diagrams or Mermaid code instead as a fallback — both achieve the same visual result.

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.