architecture-reviewer

Automate architecture review guidance for Clean Architecture TypeScript projects.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jrmatherly/shipit --skill architecture-reviewer-jrmatherly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-reviewer
Source: https://github.com/jrmatherly/shipit/tree/main/.claude/skills/architecture-reviewer
Command: npx skills add https://github.com/jrmatherly/shipit --skill architecture-reviewer-jrmatherly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides structured architectural guidance for Clean Architecture TypeScript projects, helping teams decide where code should live, how to design ports and adapters, and how to validate architecture against domain rules.

Core Features & Use Cases

  • Layer guidance determines whether logic belongs in domain, application, infrastructure, or presentation.
  • Interface & boundary design suggests ports, adapters, and repository patterns to enforce clean boundaries.
  • Conformance checks validates dependency direction and TypeSpec model updates to keep architecture coherent.

Quick Start

Request a full architecture review for a feature proposal, including layer placement, required ports, and dependency direction.

Frequently Asked Questions about architecture-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review TypeScript project architecture for clean architecture compliance?

Design ports and adapters in TypeScript by identifying infrastructure dependencies, defining interfaces in the application layer, and implementing adapters in the infrastructure layer to enforce clean boundaries.

How do I design ports and adapters in a TypeScript project?

Design ports and adapters in TypeScript by identifying infrastructure dependencies, defining interfaces in the application layer, and implementing adapters in the infrastructure layer to enforce clean boundaries.

How do I validate dependency direction in a domain-driven design TypeScript project?

Validate dependency direction in a domain-driven design project by checking that infrastructure and presentation layers depend on the application layer, ensuring the domain layer remains isolated and independent.

Where should business logic live when applying clean architecture to TypeScript?

Business logic should live in the domain layer when applying clean architecture to TypeScript, keeping it isolated from infrastructure and presentation concerns to maintain core rules and entity integrity.

Can I check TypeSpec model updates against my existing TypeScript architecture?

You can check TypeSpec model updates against your TypeScript architecture by running conformance checks that validate the updates against domain rules and existing design patterns to maintain architectural coherence.