Skill

architecture-review

Use when auditing project structure, planning refactors, improving code organization, analyzing dependencies and module boundaries, or identifying structural issues. TypeScript/JavaScript-primary with language-agnostic patterns.

npx claudepluginhub srstomp/pokayokay --plugin pokayokay

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/pokayokay:architecture-review

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Analyze, audit, and improve project structure.

Supporting Files

references/analysis-techniques.mdreferences/anti-rationalization.mdreferences/cleanup-strategies.mdreferences/dependency-management.mdreferences/refactoring-patterns.mdreferences/structural-patterns.md

SKILL.md

43 lines · ~562 tokens

Similar Skills

improve-codebase-architecture

Scans codebase for architectural friction: shallow modules, tight coupling, untestable seams. Produces an HTML report with before/after diagrams and refactoring candidates.

3 files

frontend-skills

improve-architecture

Improves architecture incrementally by fixing circular dependencies, high coupling, god files, boundary violations, and unclear module structures without full migration. Scans and measures before/after.

6 tools

specialist-agent

architecture-compass

109

Scans a codebase, conducts a structured interview, and produces a shareable architecture insights document. Use when assessing codebase architecture or direction.

1 file

lattice

Stats

LanguageShell

Parent stars7

Parent forks2

MaintenanceExcellent

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Architecture Review

Analyze, audit, and improve project structure.

Key Principles

Measure before changing — Map structure and identify concrete issues before proposing changes

Clear boundaries — Layers (UI, logic, data) separated with consistent dependency direction

Colocation — Related code together; easy to find, change, and delete features

Incremental migration — Refactor in phases, validate each step with tests

Quick Assessment

No circular dependencies

Consistent directory naming and grouping (by feature or by type)

Single responsibility per file/module, reasonable file sizes (<500 lines)

External dependencies isolated, shared code properly extracted

New developers can navigate and find code for any feature easily

Quick Start Checklist

Map current structure: directory tree, dependency graph, module boundaries

Identify issues: circular deps, god modules, leaky abstractions, deep nesting

Classify severity: critical (blocks dev), high (maintenance burden), medium/low (friction)

Propose target structure with migration plan

Execute incrementally, validating with tests after each move

References

Reference

Description

analysis-techniques.md

Dependency graphs, complexity metrics, code analysis

refactoring-patterns.md

Safe refactoring techniques, migration strategies

structural-patterns.md

Directory structures for different project types

dependency-management.md

Circular deps, coupling, module boundaries

cleanup-strategies.md

Dead code removal, consolidation, naming conventions

anti-rationalization.md

Iron Law, common rationalizations, red flag STOP list for architecture discipline