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.

Install

npx claudepluginhub srstomp/pokayokay --plugin pokayokay

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Analyze, audit, and improve project structure.

Supporting Assets

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

SKILL.md

Similar Skills

kotlin-ktor-patterns

Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.

everything-claude-code

163.2k

deep-research

Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.

everything-claude-code

163.2k

inventory-demand-planning

Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.

everything-claude-code

163.2k

Stats

Parent Repo Stars4

Parent Repo Forks0

Last CommitFeb 8, 2026

Actions

View Source View Plugin View on GitHub View README

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