feat(architecture): add Hexagonal (Ports & Adapters) reference + review checklist#5
Merged
Merged
Conversation
Add assets/architecture/hexagonal-architecture.md as a focused Ports & Adapters reference: driving/driven ports, primary/secondary adapters, the dependency direction, folder mapping, hard rules and anti-patterns. It cross-links ddd-architecture.md (which fills the core) rather than duplicating the tactical DDD building blocks. Wire it in: - README + CLAUDE.md architecture tables (8 → 9 references) - bootstrap Step 2 mapping for backend stacks (Go, Laravel) No code change needed — the installer reads architecture/ dynamically, so the new doc ships to all editors automatically. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
phuthuycoding
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a dedicated Hexagonal Architecture (Ports & Adapters) reference and wires it into the review skills so the boundary is audited, not just documented.
1. The reference doc
assets/architecture/hexagonal-architecture.md— focused on the structural boundary (cross-linksddd-architecture.mdinstead of duplicating tactical DDD):domain/application/infrastructure/folder mapping2. Review-skill coverage
/review:architect— loadshexagonal-architecture.mdin Phase 1; new 11th manual area "HX — Hexagonal Boundary" (HX1–HX8): dependency direction, port ownership, thin adapters, leaky-port detection; HX row added to the report table; triggers on "review hexagonal" / "ports and adapters review"./review:branch— new "3.4 Hexagonal boundary" mini-check for changed domain/adapter files./review:pr— hexagonal-boundary bullet in 3.1; deep audits routed to/review:architect.3. Wiring
bootstrap.mdStep 2: hexagonal added for backend stacks (Go, Laravel)/review:architecttrigger phrases syncedNo code change — the installer reads
architecture/dynamically, so the doc ships to all editors automatically.🤖 Generated with Claude Code