agentsclimarketplace

Architecture review

Skill ntaffzii/Skill-Agents/skills/engineering/architecture-review

Personal AI-agent skills, workflows, prompts, and setup guides for local LLMs and MCP-powered assistants.

Install
npx -y skills add ntaffzii/Skill-Agents --skill architecture-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Architecture review skill for evaluating codebase design, module boundaries, coupling, test seams, domain language, and simplification opportunities. Use when the user asks to improve architecture, zoom out, reduce complexity, untangle code, or review a design.

SKILL.md

1.8 KB, as published. Nobody here has run it

Architecture Review

Use this skill to reason about structure before proposing broad changes.

Workflow

  1. Map the system

    • Identify the relevant modules, entry points, data flow, and ownership boundaries.
    • Read local docs, domain glossary, ADRs, and tests if present.

  2. Locate design pressure

    • Look for repeated conditionals, hidden coupling, unclear ownership, duplicated concepts, awkward test seams, and high-change files.
    • Distinguish annoying code from code that blocks future work.

  3. Name the domain concepts

    • Use existing project language when available.
    • Flag mismatches where code names do not match business or product concepts.

  4. Propose changes

    • Prefer small boundary improvements over sweeping rewrites.
    • Give options when tradeoffs are meaningful.
    • Identify the first reversible step.

  5. Validate

    • Explain what tests or probes would prove the architecture change preserved behavior.
    • Avoid recommending refactors without a verification path.

Output Format

Current Shape
What the code is doing now.

Pressure Points
Specific issues with file references.

Recommended Move
The smallest valuable design improvement.

Validation
How to prove the change is safe.

Rules

  • Do not propose a rewrite unless incremental steps are impossible.
  • Do not introduce abstractions just because two blocks look similar.
  • Prefer deeper modules with simple interfaces over shallow layers that move complexity around.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.