gitt510gitt510/agent-skills/skills/c4-sequence/SKILL.md

c4-sequence

Skill0 starsChanged 3 months agoMITView on GitHub

Rules for drawing a route through a system as a Mermaid sequence diagram, following the C4 dynamic diagram with responses and gating steps added. Use when drawing how a request travels between people, containers, and external systems.

In this repository11 other files it gives its agents.
- build-justfileSkill
- create-issueSkill
- create-prSkill
- create-repoSkill
- dadsSkill
- handoverSkill
- mouse-doctorSkill
- oss-bus-factorSkill
- ponytail-reviewSkill
- tmuxSkill
- writing-documentsSkill

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

Distinctive:
Keep every participant at one C4 level: people, containers, and external systems.
line 14
Distinctive:
Leave out what lives below the container level: header and cookie names, function names, libraries, and steps that never stop the route.
line 20
Very specific:
Write no prose and no Note blocks.
line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

c4-sequence

Draw the route under the following rules.

Rules

Draw one route per sequenceDiagram, under a heading that names the route.
Number every step with autonumber.
Keep every participant at one C4 level: people, containers, and external systems.
Name a person by role, such as User, never by a personal name.
Merge what deploys together into one container, such as a Worker and the static assets it serves.
Label a request ->> with what it does and its technology: Verb phrase [technology].
Label a response -->> with what comes back: status or data [format].
Draw a self-call X->>X only for a step that decides whether the route goes on, such as verifying a token or authorizing a user.
Leave out what lives below the container level: header and cookie names, function names, libraries, and steps that never stop the route.
Write no prose and no Note blocks.

Example

sequenceDiagram
  autonumber
  actor User
  participant SPA as Browser (Vue SPA)
  participant Access as Cloudflare Access
  participant Worker as Worker (bibles)
  participant Neon

  User->>SPA: Opens bibles
  SPA->>Access: Requests bibles [HTTPS/JSON]
  Access->>Access: Verifies the session
  Access->>Worker: Forwards the request [JWT]
  Worker->>Worker: Verifies the JWT (signature, iss, aud, exp)
  Worker->>Neon: Reads bibles [SQL/HTTPS]
  Neon-->>Worker: Rows
  Worker-->>SPA: 200 OK [JSON]

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.

Check your setup, free