agentleFS
ontology-of-everythingontology-of-everything/SemanticSkills/skills/en/architect-4c/SKILL.md

architect-4c

Skill14 starsChanged 22 days agoApache-2.0View on GitHub

Use only when explicitly invoked. Core concepts, level definitions, principles, and common mistakes in Simon Brown's C4 model.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use hierarchical abstractions and expand through system, container, component, and code containment.

    line 33
  2. Distinctive:

    Keep the model independent of notation.

    line 35
  3. Distinctive:

    Keep the model independent of tooling.

    line 36

≈ “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

C4 software architecture model

Core concepts and definitions

C4 is Simon Brown's software architecture model. A software system contains containers, containers contain components, and code elements implement components.

LevelDefinition
ContextOne software system, its direct users, and external collaborators.
ContainerAn application or data store within a system, forming a runtime boundary for code execution or data storage.
ComponentA unit of functionality with an explicit interface inside one container, typically deployed with that container.
CodeThe classes, interfaces, functions, or data structures implementing one component.

A person represents a role interacting with the system. An external system is outside the current system boundary and may belong to the same organization.

A system landscape describes relationships across systems. A dynamic view describes interaction order within a scenario. A deployment view maps container instances to infrastructure in a particular environment. These are supporting views.

Principles

Based on the C4 website and its diagram definitions.

  • Use hierarchical abstractions and expand through system, container, component, and code containment.
  • Choose levels for the audience. There is no requirement to use all four.
  • Keep the model independent of notation.
  • Keep the model independent of tooling.

Avoiding mistakes

  • A C4 container is distinct from a Docker container, virtual machine, source folder, or library.
  • Identify components by responsibility and interface, rather than folder or class names alone.
  • Code is level four. Deployment and dynamic diagrams do not replace it.
  • Multiple deployed instances of one logical container still map to one container.
  • Distinguish runtime calls, source dependencies, and data flows.
  • Separate current state, target design, and inference. Leave unsupported structures and relationships unconfirmed.

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.