TWISTEdBRACKETS

Quality & review

SOLID

solid

A dual-mode skill grounded in the five SOLID principles. Architect mode shapes new or changed modules so the next feature has an obvious home — single responsibilities, extension points, explicit contracts, narrow interfaces, and inverted I/O dependencies. Critic mode reviews a diff or module against the same checklist and returns a scored report with principle IDs, evidence, blast-radius risk, and concrete fixes. Built for agent-heavy codebases where review time does not scale with output volume.

What it does

  • Runs in Architect mode while designing or implementing, and Critic mode when reviewing
  • Loads a maintained principles reference (smells, pass shapes, fixes) rather than inventing rules
  • Keeps extension points, contracts, and ports explicit so agents land the next change safely
  • Flags SRP, OCP, LSP, ISP, and DIP findings with location, evidence, risk, and a specific fix
  • Returns a principle scorecard and a priority-ordered change list without refactoring unless asked

Report shape

Excerpt of the critic report this skill returns. Principle IDs stay stable so you can re-run after edits.

markdown
# SOLID review — checkout route

**Mode:** Critic · **Scope:** touched · **Depth:** pragmatic

## Summary
The POST handler owns validation, persistence, and email. The next notification feature will land in the same file. Payment charging imports Stripe directly, so tests cannot fake the gateway.

## Blocking
- SRP · app/api/orders/route.js · POST validates, writes, and emails · Risk: unrelated product decisions edit one handler · Fix: extract validateOrder / createOrder / sendOrderConfirmation
- DIP · lib/charge-order.js · imports stripe and calls charges.create · Risk: provider swap and unit tests rewrite core logic · Fix: inject a { charge } gateway

## Principle scorecard
| Principle | Verdict |
| SRP | Fail |
| OCP | Pass |
| LSP | N/A |
| ISP | Pass |
| DIP | Fail |

How it flows

  1. 01Choose Architect or Critic from the request
  2. 02Read references/principles.md and resolve the target scope
  3. 03Architect: name responsibilities, contracts, and seams — then implement
  4. 04Critic: verdict each principle, score severity, write the report
  5. 05Offer to apply fixes or re-run after changes

Example prompt

“/solid Review the changes in this branch against SOLID and flag anything that widens blast radius.”

Install

sh
npx dot-skills add levi-putna/twistedbrackets.com/solid