707-technologies-hexagonal-architecture — Claude Code skill
707-technologies-hexagonal-architecture is a Claude Code skill that reviews and improves Hexagonal architecture boundaries in Java projects without coupling to Spring Boot, Quarkus, or Micronaut.
Apache-2.0 174 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 707-technologies-hexagonal-architecture -a claude-codeWhat 707-technologies-hexagonal-architecture does
This skill analyzes Java codebases to ensure the domain stays independent from frameworks, persistence, web adapters, and infrastructure. It checks that application code coordinates through inbound and outbound ports, adapters depend on the core, and no cross-layer dependencies break the structure.
It reads package layout, imports, and Maven modules to find concrete boundary violations and proposes fixes aligned with your project structure. When ArchUnit fits your workflow, the skill suggests architecture test rules. Maven dependency additions are delegated to 111-java-maven-dependencies; framework runtime wiring is routed to the appropriate framework skill.
No ArchUnit or architecture tests are required to start. The skill reviews boundaries by inspecting code structure directly, and every finding points to specific classes, imports, and packages.
What it helps with
- Verify domain is free of framework and infrastructure dependencies
- Find and fix dependency direction violations between ports and adapters
- Ensure application orchestration flows through ports, not direct adapter calls
- Add ArchUnit rules to enforce architecture boundary compliance
- Eliminate infrastructure leakage into domain packages
Example prompts for the agent
- Review Hexagonal architecture boundaries in my Java project
- Find infrastructure leakage in domain code and suggest fixes
- Add ArchUnit rules to verify ports and adapters dependency direction
How to install 707-technologies-hexagonal-architecture
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 707-technologies-hexagonal-architecture -a claude-code2Manually: put the files in place
~/.claude/skills/707-technologies-hexagonal-architecture/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/707-technologies-hexagonal-architecture/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 707-technologies-hexagonal-architecture -a codex2Manually: put the files in place
.agents/skills/707-technologies-hexagonal-architecture/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 707-technologies-hexagonal-architecture -a cursor2Manually: put the files in place
.cursor/skills/707-technologies-hexagonal-architecture/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/707-technologies-hexagonal-architecture2Manually: put the files in place
.github/skills/707-technologies-hexagonal-architecture/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 707-technologies-hexagonal-architecture -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/707-technologies-hexagonal-architectureManually: put the files in place
.devin/skills/707-technologies-hexagonal-architecture/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 707-technologies-hexagonal-architecture -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 707-technologies-hexagonal-architecture
How do I install 707-technologies-hexagonal-architecture in Claude Code?
Run npx skills add jabrena/plinth --skill 707-technologies-hexagonal-architecture -a claude-code, then open ~/.claude/skills/707-technologies-hexagonal-architecture/SKILL.md.
What does 707-technologies-hexagonal-architecture do?
Analyzes Java projects for Hexagonal architecture violations: ensures domain is independent from frameworks and infrastructure, adapters depend on the core, and no leakage occurs between layers. Provides specific remediation steps.
Do I need to use ArchUnit already to work with this skill?
No. The skill works with any Java project by examining package structure and imports. If your architecture is ready, it suggests how to add ArchUnit tests for continuous boundary verification.
Source text
SKILL.md · Apache-2.0
--- name: 707-technologies-hexagonal-architecture description: Use when you need framework-agnostic Hexagonal architecture guidance for Java projects - ports and adapters boundaries, application core independence, driving and driven adapters, dependency direction, infrastructure leakage detection, optional architecture tests, and evidence-backed remediation. This should trigger for requests such as Review Hexagonal architecture; Review ports and adapters boundaries; Enforce dependency direction; Add ArchUnit architecture tests; Detect infrastructure leakage in domain code; Improve ports and adapters boundaries. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # Java Hexagonal architecture boundary review Help teams review and improve **Hexagonal architecture** boundaries in Java applications without coupling the guidance to Spring Boot, Quarkus, or Micronaut runtime wiring. **What is covered in this Skill?** - Domain independence: entities, value objects, domain services, and domain policies stay free of framework, persistence, web, messaging, and infrastructure APIs - Application/use-case orchestration: use cases coordinate domain behavior through inbound or outbound ports without taking dependencies on concrete adapters - Adapter and infrastructure boundaries: driving adapters call inbound ports, and driven adapters implement outbound ports - Dependency direction checks: package, module, import, Maven module, and test evidence that adapters depend on the core rather than the core depending on adapters - Optional architecture verification: ArchUnit-style rules for Hexagonal boundaries when architecture tests fit the project - Evidence-backed remediation: findings cite concrete classes, imports, dependencies, packages, or tests and propose small boundary-preserving changes **Scope:** Framework-agnostic architecture boundary review for Java projects. For Spring Boot, Quarkus, or Micronaut runtime wiring, defer to the matching framework skill. For adding ArchUnit or other Maven dependencies, defer to `111-java-maven-dependencies`. ## Constraints Keep recommendations focused on architecture boundaries and dependency direction unless the user explicitly asks for framework runtime implementation. After editing this repository's XML sources, regenerate skills and verify the build. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before proposing Java or Maven changes in the same change set - **BOUNDARIES**: Domain packages must not depend on application, adapter, infrastructure, framework, persistence, web, messaging, or dependency-injection APIs - **USE CASES**: Application/use-case code may orchestrate domain behavior and depend on inbound/outbound ports, but must not depend on concrete adapter implementations - **ADAPTERS**: Driving adapters call inbound ports and driven adapters implement outbound ports; adapters must not become shared domain logic or depend on each other unnecessarily - **ARCHUNIT OPTIONAL**: Treat ArchUnit as an optional verification approach selected when it fits the project; do not require adding it before Hexagonal architecture guidance is useful - **DEPENDENCIES**: Route Maven dependency evaluation, including ArchUnit dependency additions, to `111-java-maven-dependencies` - **FRAMEWORK ROUTING**: Defer Spring Boot, Quarkus, and Micronaut runtime wiring to the matching framework-specific skill without embedding direct framework skill links in this guidance - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` before promoting changes - **EDGE CASE**: If package layout, module boundaries, framework ownership, or persistence strategy is ambiguous and affects the review, ask a clarifying question before editing architecture-sensitive code - **EDGE CASE**: Distinguish confirmed boundary violations from assumptions, conventions inferred from naming, and missing context ## When to use this skill - Review Hexagonal architecture - Review ports and adapters boundaries - Review architecture boundaries - Enforce dependency direction - Add ArchUnit architecture tests - Detect infrastructure leakage in domain code - Improve ports and adapters boundaries ## Workflow 1. **Read reference and map the codebase** Read `references/707-technologies-hexagonal-architecture.md` and inspect packages, modules, imports, Maven modules, tests, and framework entry points before making claims about architecture boundaries. 2. **Identify ports, adapters, and dependency direction** Map domain, application/use-case, inbound ports, outbound ports, driving adapters, driven adapters, and infrastructure responsibilities; record the evidence used and mark unclear areas as assumptions. 3. **Review violations and propose boundary-preserving changes** Report concrete core-to-adapter dependency violations, framework or infrastructure leakage, adapter coupling, and misplaced behavior with small remediation steps aligned to the existing project structure. 4. **Recommend optional verification and route out-of-scope work** Suggest ArchUnit-style tests when useful, route dependency additions to `111-java-maven-dependencies`, route framework runtime wiring to the matching framework skill, and summarize verification results. ## Reference For detailed guidance, examples, and constraints, see [references/707-technologies-hexagonal-architecture.md](references/707-technologies-hexagonal-architecture.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth