agentleFS
callowayprojectcallowayproject/agent-skills/skills/arch-confirm/SKILL.md

arch-confirm

Skill2 starsChanged 3 months agoNo licenceView on GitHub

Turns an application team's cloud architecture doc into a structured, reviewable model and a fixed set of diagrams/tables *before* any Terraform is written, so the infra team can show the app team "is this what you said?" and catch misreadings early. Use when a new architecture doc arrives from an app team and needs translation into Terraform, when starting a new infra/Terraform project from a design doc, when the user says "confirm this architecture doc," "is this what you said," "generate architecture views for review," or wants a PR-based sign-off step before writing infrastructure-as-code. Also use when an app team sends a *revised* doc after an earlier confirmation round — this skill re-extracts and diffs against the existing model instead of starting over. Explicitly out of scope: generating the actual Terraform — this skill stops at a confirmed, approved model.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.