Agent skill
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 this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/architecture-validator
SKILL.md
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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?