Agent skill

Architecture Reviewer

by shep-ai in shep-ai/shep

A skill your agent uses when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles.

MITAuto-check passedDevelopment

Install Architecture Reviewer

skills CLI
$ npx skills add shep-ai/shep --skill architecture-reviewer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install shep-ai/shep architecture-reviewer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/shep-ai/shep.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/architecture-reviewer .claude/skills/architecture-reviewer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
architecture-reviewer
GitHub stars
264
Token cost
~808 tokens
SKILL.md length
195 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles.

  • Works in 5 steps: Design Decisions - Advise where new code… → Pattern Compliance - Ensure proposals… → Dependency Direction - Verify… → …
  • Making architectural decisions
  • SKILL.md covers Your Responsibilities, Project Architecture, When Reviewing a Proposal and Output Format, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Architecture Reviewer is an agent skill from shep-ai/shep. 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

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Design patterns. It works with TypeScript. The repository describes itself as: Ship features 10x faster. Built In Auto: Memory, K8S Agent & Security (SDD+SDLC) . 😇. The licence is MIT.

When your agent uses it

  • Making architectural decisions
  • Planning features
  • Designing new components
  • Validating that proposed changes align with Clean Architecture principles

Example prompts

  • “review architecture”
  • “check design”
  • “does this fit”
  • “/architecture-reviewer”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit 0304cfc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Architecture Reviewer loads about 808 tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 195 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~106
When it runs · the whole SKILL.md, loaded when a task matches
~808

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from shep-ai/shep at commit 0304cfc, republished under its MIT licence (© shep-ai). 195 words, ~808 tokens.

Download SKILL.mdSave it as .claude/skills/architecture-reviewer/SKILL.md (or your agent's skills folder).
name
architecture-reviewer
description
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
metadata.version
1.0.0
metadata.author
Shep AI (https://shep.bot)
metadata.homepage
https://shep.bot
metadata.repository
https://github.com/shep-ai/shep
metadata.context
fork

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

© shep-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/architecture-reviewer of shep-ai/shep.

Open the folder on GitHubat commit 0304cfc

Compare with similar skills

Architecture Reviewer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Architecture Reviewer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architecture Reviewer this skillshep-ai/shep264—~808Automated safety check: PassMIT
AST Visitor Pattern for Unionsprisma/orm48k—~830Automated safety check: PassApache-2.0
Effect TSmattiacerutti/supernova185—~2.8kAutomated safety check: PassMIT
sfdx-hardis Architecture Guidehardisgroupcom/sfdx-hardis404—~2.1kAutomated safety check: PassAGPL-3.0
New Pattern Authoring WorkflowTotoro-jam/battle-tested-patterns345—~1.5kAutomated safety check: PassMIT
JavaScript IO Effects With Sagasparalleldrive/aidd384—~587Automated safety check: PassMIT

Similar skills

  • Official

    Replaces a plain TypeScript union plus switch statements with frozen subclasses and a visitor interface when several places dispatch on the same variants.

    48k GitHub stars~830 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Effect TS

    mattiacerutti/supernova

    Write idiomatic Effect v4 TypeScript following official best practices from effect-solutions and the Effect source.

    185 GitHub stars~2.8k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • sfdx-hardis Architecture Guide

    hardisgroupcom/sfdx-hardis

    Explains how the sfdx-hardis Salesforce CLI plugin is built: its TypeScript and Oclif stack, command layout, agent-mode flag and provider classes for git, notifications and AI.

    404 GitHub stars~2.1k tokensUpdated today
    DevelopmentAuto-check passed
  • New Pattern Authoring Workflow

    Totoro-jam/battle-tested-patterns

    Step-by-step workflow for adding a new pattern to the battle-tested-patterns repo: validate the topic, verify sources, write the doc, code and exercises.

    345 GitHub stars~1.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Teaches the saga pattern with call and put so network requests and side effects stay out of the logic and sagas can be tested without mocks.

    384 GitHub stars~587 tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Angular Cop

    fmflurry/settings-opencode

    Pre-merge code review for Angular + TypeScript pull requests.

    171 GitHub stars~1.4k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

More from shep-ai/shep

  • React Flow

    shep-ai/shep

    React Flow (@xyflow/react) for workflow visualization with custom nodes and edges.

    264 GitHub stars~2.8k tokensUpdated 2 days ago
    Auto-check passed
  • Shep Workstreams

    shep-ai/shep

    A skill your agent uses when a large body of work (a version milestone, an epic, a roadmap, a set of PRDs/design docs) needs to be broken into parallel workstreams and executed with the shep CLI.

    264 GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed
  • Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions.

    264 GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • Tsp Model

    shep-ai/shep

    A skill your agent uses when creating, modifying, or documenting TypeSpec domain models.

    264 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Architecture Reviewer

What does Architecture Reviewer do?

A skill your agent uses when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles. Architecture Reviewer is an agent skill from shep-ai/shep. Use when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles.

When should I use Architecture Reviewer?

Architecture Reviewer fits situations like: making architectural decisions; planning features; designing new components; validating that proposed changes align with Clean Architecture principles.

How do I install Architecture Reviewer in Claude Code?

Run `npx skills add shep-ai/shep --skill architecture-reviewer -a claude-code`. Or copy the skill folder (.claude/skills/architecture-reviewer in shep-ai/shep) into .claude/skills/architecture-reviewer in your project. Claude Code loads it when a task matches its description.

How do I install Architecture Reviewer in Codex?

Run `npx skills add shep-ai/shep --skill architecture-reviewer -a codex`. Or copy the skill folder (.claude/skills/architecture-reviewer in shep-ai/shep) into .agents/skills/architecture-reviewer in your project. Codex loads it when a task matches its description.

Can I use Architecture Reviewer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shep-ai/shep --skill architecture-reviewer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-reviewer, .gemini/skills/architecture-reviewer, .github/skills/architecture-reviewer and .opencode/skills/architecture-reviewer in your project.

What does Architecture Reviewer need to run?

SKILL.md names no scripts, command-line tools or credentials: Architecture Reviewer is instructions for the agent only.

Does Architecture Reviewer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Architecture Reviewer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Architecture Reviewer use?

Architecture Reviewer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Architecture Reviewer use?

About 808 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Architecture Reviewer?

Skills that share tags, products or a category with Architecture Reviewer: AST Visitor Pattern for Unions (prisma/orm, 48k stars), Effect TS (mattiacerutti/supernova, 185 stars), sfdx-hardis Architecture Guide (hardisgroupcom/sfdx-hardis, 404 stars) and New Pattern Authoring Workflow (Totoro-jam/battle-tested-patterns, 345 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architecture Reviewer?

shep-ai (a GitHub organization) maintains it in shep-ai/shep, which has 264 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.

Source: shep-ai/shep on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.