agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/architecture-fit-check/SKILL.md

architecture-fit-check

Skill1 starsChanged 25 days agoMITView on GitHub

Tests solution architecture fitness when a design decision needs structured challenge before approval or build.

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 at design gates, before major commitments, or when an existing platform struggles with changing demand.

    line 9
  2. Distinctive:

    Test fit across capacity, resilience, security, maintainability and interoperability.

    line 20
  3. Distinctive:

    Run scenario checks for peak demand, component failure, recovery and future change.

    line 21

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

Architecture Fit Check

When to use it

Use at design gates, before major commitments, or when an existing platform struggles with changing demand.

What Claude needs

  • client-context.md for business background
  • Business outcomes and functional requirements
  • Architecture diagrams, interfaces and data flows
  • Non-functional needs, constraints and design principles

Method

  1. Translate outcomes into measurable functional and non-functional requirements.
  2. Map components, trust boundaries, integrations, data stores and failure paths.
  3. Test fit across capacity, resilience, security, maintainability and interoperability.
  4. Run scenario checks for peak demand, component failure, recovery and future change.
  5. Record trade-offs and gaps in an architecture decision log.
  6. Recommend accept, amend, prototype or reject with conditions and evidence needs.

Output format

Provide a fit scorecard, scenario findings, gap register and decision record. Include conditions, owners and evidence required before the next gate.

Quality checks

  • Requirements are testable and linked to business outcomes.
  • Failure modes and operational support are examined.
  • Trade-offs are explicit rather than hidden in an overall score.

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.