agentsclimarketplace

Arc design review

Skill onfire7777/universal-ai-skills-library/skills/arc-design-review

Three-phase architecture design review pipeline: Architect creates initial design, Refiner improves it, Critic challenges it. Then facilitated discussion produces an Architecture Decision Record. Use for system design, major refactors, new features, or any significant architectural decision. Triggers on: 'architecture review', 'design review', 'ADR', 'architecture decision', 'system design review', 'review this architecture', 'should we build it this way'.From its SKILL.md

Install
npx -y skills add onfire7777/universal-ai-skills-library --skill arc-design-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

  • 13 stars13 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.

SKILL.md

2.1 KB, 363 tokens by cl100k_base, as published. Nobody here has run it

Architect-Refine-Critique Design Review

Overview

A three-phase design review pipeline that produces an Architecture Decision Record.

Phase 1: Architect

  • Research the codebase and project conventions
  • Identify constraints, requirements, integration points
  • Create initial design with component diagrams
  • Document structural decisions with reasoning

Phase 2: Refine

  • Review the initial design for gaps
  • Improve based on best practices and current trends
  • Challenge assumptions, verify feasibility
  • Produce refined design document

Phase 3: Critique

  • Adversarial evaluation of the refined design
  • Rate findings by severity (Critical, High, Medium, Low)
  • Identify risks, failure modes, scaling concerns
  • Propose alternatives where design is weak

Phase 4: Review & ADR

Facilitated discussion with the user:

  1. Present initial design summary — discuss strengths/weaknesses
  2. Present refinements — discuss whether they addressed right issues
  3. Present critique findings one by one — user decides Accept/Reject/Defer
  4. Synthesize into ADR:
# ADR: [Title]
**Status:** Proposed | **Date:** [today]
## Context: [problem + constraints]
## Decision: [chosen architecture + reasoning]
## Consequences: [positive, negative, mitigations]
## Alternatives Considered: [rejected options + why]
## Process Improvements: [patterns identified during review]

Rules

🚨 Ground every decision in a named principle (SRP, DIP, separation-of-concerns, etc.) 🚨 Discuss ALL phases in order — don't skip. 🚨 Don't decide for the user. Present, discuss, let them choose.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,852. 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.