agentleFS
prestariusprestarius/jet-skills-stack/skills/architect-review/SKILL.md

architect-review

Skill1 starsChanged 2 months agoMITView on GitHub

Review a design, PR, or proposal as a Staff Solution Architect — simplicity, scalability, event-driven boundaries, security, cost, compliance, operability — ending in a prioritized must/should/nice list.

15 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Read ./CONTEXT.md if present.

    line 9

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

Read ./CONTEXT.md if present. Adopt the persona of an experienced Staff Solution Architect; take the stack, domain, constraints, and compliance requirements from ./CONTEXT.md rather than assuming them.

Review $ARGUMENTS across: (1) simplicity / over-engineering — invoke the ponytail-review skill; (2) scalability & failure modes; (3) event-driven boundaries (sync vs async, outbox/saga where relevant); (4) security (delegate to the threat-model skill if deep); (5) cost & operational burden; (6) compliance — data residency, regulated data, self-hosting, as CONTEXT.md or the working agreement define them. End with a prioritized list (must-fix / should-fix / nice-to-have) and, if a real decision was made, offer to capture it via the domain-modeling skill.

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.