Agent skill

707 Technologies Hexagonal Architecture

by jabrena in jabrena/plinth

A skill your agent uses when you need framework-agnostic Hexagonal architecture guidance for Java projects - ports and adapters boundaries, application core independence, driving and driven…

Apache-2.0Auto-check passedDevelopment

Install 707 Technologies Hexagonal Architecture

skills CLI
$ npx skills add jabrena/plinth --skill 707-technologies-hexagonal-architecture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jabrena/plinth 707-technologies-hexagonal-architecture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/707-technologies-hexagonal-architecture .claude/skills/707-technologies-hexagonal-architecture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
707-technologies-hexagonal-architecture
GitHub stars
447
Token cost
~1.4k tokens
SKILL.md length
563 words
Files
2 (incl. references)
Skills in repo
124
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when you need framework-agnostic Hexagonal architecture guidance for Java projects - ports and adapters boundaries, application core independence, driving and driven…

  • You need framework-agnostic Hexagonal architecture guidance for Java projects - ports and adapters boundaries
  • SKILL.md covers Constraints, When to use this skill, Workflow and Reference
  • Calls mvn
  • Application core independence

What it does

707 Technologies Hexagonal Architecture is an agent skill from jabrena/plinth. 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…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/707-technologies-hexagonal-architecture.md`).

It sits in Development, covering Design patterns and Software architecture. It works with Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.

When your agent uses it

  • You need framework-agnostic Hexagonal architecture guidance for Java projects - ports and adapters boundaries
  • Application core independence
  • Driving and driven adapters
  • Dependency direction

Example prompts

  • “/707-technologies-hexagonal-architecture”

What it can do on your machine

Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • mvn

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

707 Technologies Hexagonal Architecture loads about 1.4k tokens when it runs, and up to ~6.7k if it reads all its reference files. Until then it costs about 155 tokens; SKILL.md has 563 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~155
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 563 words, ~1,367 tokens.

Download SKILL.mdSave it as .claude/skills/707-technologies-hexagonal-architecture/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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
metadata.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
Show full SKILL.md (164 more words)Show less

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.

  1. 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.

  1. 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.

  1. 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.

© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/707-technologies-hexagonal-architecture of jabrena/plinth.

  • SKILL.md
  • references/707-technologies-hexagonal-architecture.md

Open the folder on GitHubat commit dca88dc

Compare with similar skills

707 Technologies Hexagonal Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

707 Technologies Hexagonal Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
707 Technologies Hexagonal Architecture this skilljabrena/plinth447—~1.4kAutomated safety check: PassApache-2.0
Java Architecture Reviewdecebals/claude-code-java751—~2.2kAutomated safety check: PassMIT
Code Review Skillawesome-skills/code-review-skill2.1k—~2.8kAutomated safety check: NotesMIT
Architecture PatternsKartikLabhshetwar/better-shot2.4k2 repos~1.4kAutomated safety check: PassCustom licence
Java Design Patterns Referencedecebals/claude-code-java7511 repos~4.4kAutomated safety check: PassMIT
Brooks Audithyhmrright/brooks-lint1.5k1 repos~537Automated safety check: PassMIT

Similar skills

  • Java Architecture Review

    decebals/claude-code-java

    Reviews a Java project's architecture at the macro level: package structure, module boundaries, dependency direction and layering.

    751 GitHub stars~2.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Code Review Skill

    awesome-skills/code-review-skill

    Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…

    2.1k GitHub stars~2.8k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes
  • Architecture Patterns

    KartikLabhshetwar/better-shot

    Deep dive into software architecture for macOS. An agent skill from KartikLabhshetwar/better-shot.

    2.4k GitHub starsUsed in 2 repos~1.4k tokens
    DevelopmentAuto-check passed
  • Java Design Patterns Reference

    decebals/claude-code-java

    A practical Java reference for Builder, Factory, Singleton, Strategy, Observer and other patterns, with a table matching problems to patterns.

    751 GitHub starsUsed in 1 repo~4.4k tokens
    DevelopmentAuto-check passed
  • Brooks Audit

    hyhmrright/brooks-lint

    Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books.

    1.5k GitHub starsUsed in 1 repo~537 tokens
    DevelopmentAuto-check passed
  • Adopt a Design Pattern

    Totoro-jam/battle-tested-patterns

    Matches a coding problem to one of 46 documented systems patterns, checks that it really fits, then adapts it into your codebase with a test for its invariant.

    345 GitHub stars~4.9k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from jabrena/plinth

All 124 skills in this repo
  • A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…

    447 GitHub stars~874 tokensUpdated 2 days ago
    Auto-check passed
  • A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…

    447 GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check passed
  • A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…

    447 GitHub stars~3.2k tokensUpdated 2 days ago
    Auto-check passed
  • A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…

    447 GitHub stars~842 tokensUpdated 2 days ago
    Auto-check passed
  • A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…

    447 GitHub stars~903 tokensUpdated 2 days ago
    Auto-check passed
  • A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…

    447 GitHub stars~697 tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about 707 Technologies Hexagonal Architecture

What does 707 Technologies Hexagonal Architecture do?

A skill your agent uses when you need framework-agnostic Hexagonal architecture guidance for Java projects - ports and adapters boundaries, application core independence, driving and driven…. 707 Technologies Hexagonal Architecture is an agent skill from jabrena/plinth. 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.

When should I use 707 Technologies Hexagonal Architecture?

707 Technologies Hexagonal Architecture fits situations like: you need framework-agnostic Hexagonal architecture guidance for Java projects - ports and adapters boundaries; application core independence; driving and driven adapters; dependency direction.

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`. Or copy the skill folder (skills/707-technologies-hexagonal-architecture in jabrena/plinth) into .claude/skills/707-technologies-hexagonal-architecture in your project. Claude Code loads it when a task matches its description.

How do I install 707 Technologies Hexagonal Architecture in Codex?

Run `npx skills add jabrena/plinth --skill 707-technologies-hexagonal-architecture -a codex`. Or copy the skill folder (skills/707-technologies-hexagonal-architecture in jabrena/plinth) into .agents/skills/707-technologies-hexagonal-architecture in your project. Codex loads it when a task matches its description.

Can I use 707 Technologies Hexagonal Architecture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 707-technologies-hexagonal-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/707-technologies-hexagonal-architecture, .gemini/skills/707-technologies-hexagonal-architecture, .github/skills/707-technologies-hexagonal-architecture and .opencode/skills/707-technologies-hexagonal-architecture in your project.

What does 707 Technologies Hexagonal Architecture need to run?

Going by SKILL.md and its folder, 707 Technologies Hexagonal Architecture needs the command-line tools its instructions call (mvn).

Does 707 Technologies Hexagonal Architecture access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is 707 Technologies Hexagonal Architecture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does 707 Technologies Hexagonal Architecture use?

707 Technologies Hexagonal Architecture is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 707 Technologies Hexagonal Architecture use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.3k tokens, read only when the agent opens those files.

What are the alternatives to 707 Technologies Hexagonal Architecture?

Skills that share tags, products or a category with 707 Technologies Hexagonal Architecture: Java Architecture Review (decebals/claude-code-java, 751 stars), Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), Architecture Patterns (KartikLabhshetwar/better-shot, 2.4k stars) and Java Design Patterns Reference (decebals/claude-code-java, 751 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 707 Technologies Hexagonal Architecture?

jabrena (a GitHub user) maintains it in jabrena/plinth, which has 447 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.

Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.