Skip to content
Agentmart
Submit a tool

hexagonal-architecture

Preserve the project's hexagonal boundaries between CLI, application, domain, and infrastructure.

Skill by smaje99

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/smaje99-hexagonal-architecture

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Preserve the project's hexagonal boundaries between CLI, application, domain, and infrastructure. Use when adding orchestration, introducing adapters, or refactoring workflow code around ports and domain rules.

Use cases: devops, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/hexagonal-architecture

What's inside

Skill name
hexagonal-architecture
Description
Preserve the project's hexagonal boundaries between CLI, application, domain, and infrastructure. Use when adding orchestration, introducing adapters, or refactoring workflow code around ports and domain rules.
License
MIT
Instructions
31 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Hexagonal Architecture

## Goal

Keep domain rules isolated from CLI, filesystem, subprocess, and HTTP details.

## When To Use

- Adding new orchestration logic
- Introducing external integrations
- Refactoring workflow code

## Steps

1. Identify the port the use case needs.
2. Model the domain entities and errors first.
3. Keep orchestration in the application layer.
4. Implement adapters in infrastructure only.
5. Verify imports flow inward, not outward.

## Checklist

- Domain does not import Typer, Rich, subprocess, or httpx adapters
- Application depends on ports, not concrete integrations
- Infrastructure implements the ports

## Exit Criteria

The feature can be tested without invoking real external systems.

From smaje99/orgdoc, MIT.

More from smaje99/orgdoc

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jun 12, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from smaje99

Cite this page

hexagonal-architecture skill. Agent Mart. https://agentmart.dev/skills/smaje99-hexagonal-architecture (last updated 2026-10-24)