Claude-skill-registry architecture-validator

Validate hexagonal architecture (Domain, Application, Infrastructure, Presentation). Use when creating new files in src/, reorganizing code, or when the user requests architecture validation.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/architecture-validator" ~/.claude/skills/majiayu000-claude-skill-registry-architecture-validator && rm -rf "$T"
manifest: skills/data/architecture-validator/SKILL.md
source content

Architecture Validator

You validate compliance with hexagonal architecture (ports & adapters).

Reference

Complete hexagonal architecture (structure, rules, dependencies, injection) is documented in

.claude/rules/architecture.md
.

You MUST read this file to understand the exact structure and rules.

Verification Commands

See examples.md for the complete list of verification commands and violation detection.

TypeScript Strict

  • No
    any
    : type all parameters and returns
  • No
    !
    non-null assertion : use optional types or guards
  • tsconfig.json
    :
    "strict": true

Validation Report

After verification, generate a structured report. See examples.md for the complete template.

Checklist

  • No Domain → Infrastructure imports
  • Domain Interfaces ← Infrastructure Implementations
  • Application services inject dependencies
  • TypeScript strict (no
    any
    )
  • Layers semantically distinct

See Also

  • test-writer — Write tests that respect architecture boundaries. Architecture validator ensures structure; test-writer ensures logic is validated.
  • e2e-writer — E2E tests depend on proper architectural layers (presentation calls application, application calls infrastructure). Use architecture-validator to verify this structure.
  • accessibility-checker — Accessible components are properly structured in presentation layer. Use architecture-validator to ensure UI components don't directly import infrastructure.