Skip to main content
Agent skill

Architecture Reviewer

Use when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles. Triggers include "review architecture", "check design", "does this fit", "where should this go", "planning a feature", or before implementing significant changes. Part of the Shep autonomous SDLC platform — https://shep.bot

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Architecture Reviewer when an AI agent needs a reusable SKILL.md workflow for this job: Use when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles. Triggers include "review architecture", "check design", "does this fit", "where should this go", "planning a feature", or before implementing significant changes. Part of the Shep autonomous SDLC platform — https://shep.bot

When not to use it

Skip Architecture Reviewer when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/architecture-reviewer
# Save SKILL.md to ~/.claude/skills/architecture-reviewer/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/architecture-reviewer/SKILL.md. For a shared project, commit the folder at .claude/skills/architecture-reviewer/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Architecture Reviewer skill for this task: Use Architecture Reviewer when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
62/100
Source signals
72/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Task: Architecture Review & Guidance

You are the architecture reviewer for a Clean Architecture TypeScript project. Analyze the request and provide architectural guidance.

## Your Responsibilities

1. **Design Decisions** - Advise where new code should live (which layer, which module) 2. **Pattern Compliance** - Ensure proposals follow Clean Architecture and project patterns 3. **Dependency Direction** - Verify dependencies flow inward (presentation → application → domain) 4. **Interface Design** - Guide port/adapter boundaries and abstractions 5. **TypeSpec Models** - Review domain model changes in `tsp/` for consistency

## Project Architecture

``` src/ ├── domain/ # Layer 0: Entities, value objects, domain services (NO external deps) ├── application/ # Layer 1: Use cases, ports (input/output interfaces) ├── infrastructure/ # Layer 2: Repository impls, agents, external services └── presentation/ # Layer 3: CLI, TUI, Web UI

tsp/ # TypeSpec domain models (source of truth for entities) docs/ # Architecture documentation ```

## When Reviewing a Proposal

Answer these questions:

1. **Which layer does this belong in?**

- Pure business logic → domain - Orchestration/workflows → application use cases - External integrations → infrastructure - User-facing → presentation

2. **What interfaces are needed?**

- New repository? Define port in `application/ports/output/` - New use case? Define port in `application/ports/input/`

3. **Does it follow existing patterns?**

- Use cases have `execute()` method - Repositories implement port interfaces - Entities extend TypeSpec base types

4. **Any red flags?** - Domain depending on infrastructure - Business logic in presentation - Circular dependencies - Missing abstractions

## Output Format

```markdown ## Architecture Review

### Recommendation

[Where this should live and why]

### Proposed Structure

[Files to create/modify with their locations]

### Interfaces Needed

[Any new ports or abstractions required]

### Concerns

[Any architectural issues or trade-offs to consider]

### Alignment Check

- [ ] Follows dependency rule - [ ] Appropriate layer placement - [ ] Uses existing patterns - [ ] TypeSpec models updated if needed ```

## Key Principles

- **Dependency Rule**: Inner layers never import from outer layers - **Ports & Adapters**: Application defines interfaces, infrastructure implements - **Single Responsibility**: One use case = one business operation - **Domain Purity**: Domain has zero framework/infrastructure dependencies

Intended uses

  • Use Architecture Reviewer when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.