Architecture Check — Development skill for Claude Code
Architecture reviewer step 2 — verify dependency direction, crate boundaries, type placement.
How to install Architecture Check
Installs to ~/.claude/commands/effortlessmetrics-perl-lsp-architecture-check.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/EffortlessMetrics/perl-lsp/HEAD/.claude/commands/architecture-check.md -o ~/.claude/commands/effortlessmetrics-perl-lsp-architecture-check.md Restart Claude Code, or start a new session, for it to be picked up.
What Architecture Check does
description: Architecture reviewer step 2 — verify dependency direction, crate boundaries, type placement user-invocable: false
Architecture: Check
Verify the proposed design respects the codebase's structural contracts.
Synthesize with prior agents (do this BEFORE running structural checks)
You run after accuracy, research, oppositional, and diaboli. Their comments are on the issue. Your verdict must *engage* with theirs — your job is to add the structural-alignment lens, not e
Alternatives in Development
- Dependency Health Check — Execute the deps-health-inline skill for inline orchestration 172 ★
- Clean Architecture Skills — Claude Code skill for reviewing and designing code based on Clean Architecture principles (Dependency Rule, La 84 ★
- Close Review — Month-end close / GL compliance check — invokes accounting-reviewer to produce TM-accounting-{slug}.md with do 83 ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Module Boundaries
Restructure module boundaries and dependency direction so change cost becomes local and predictable
Architecture Comment
Architecture reviewer step 3 — post alignment findings as issue comment
Architecture Read
Architecture reviewer step 1 — read the issue and understand proposed structural changes
Check Layers
Verify that the DDD layer boundaries are intact — domain never imports impl. Reports any violations.
Hatch3r Codebase Map
Reverse-engineer a brownfield codebase into current-state module boundaries, integration-point inventory, tech
Step Back
Circuit breaker — stop, diagnose why attempts are failing, propose a fundamentally new direction before trying
Related Agents
Architecture Guardian
Use to verify MacMagazine module boundaries and system compliance are intact after adding/moving code or editi
Architect Reviewer
Architecture reviewer. Analyzes module boundaries, dependency direction, coupling, and pattern consistency.
iOS Architect
Tier 1 — Strategy. Owns module boundaries, layering, and technology decisions. Use for architecture design, Cl