Hexagonal Clean Architecture

Apply Alistair Cockburn's Hexagonal Architecture (Ports and Adapters), Jeffrey Palermo's Onion Architecture, and Robert C. Martin's Clean Architecture — the family of architectural styles that put the domain at the center, push frameworks and I/O to the edges, and enforce inward-pointing dependencies. Use when structuring a non-trivial application, separating business logic from delivery and persistence, deciding where ports live and how adapters plug in, or testing domain logic without spinning up infrastructure.

5 stars 2 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill hexagonal-clean-architecture
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/hexagonal-clean-architecture ~/.claude/skills/hexagonal-clean-architecture

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Hexagonal / Clean Architecture

Apply this skill when structuring a non-trivial application that will have more than one delivery mechanism (HTTP, message queue, CLI), persistence target, or external integration — or simply when you want business logic that is independent of frameworks, testable in isolation, and resistant to infrastructure churn.

## Core Philosophy

**The domain is the center of the universe.** Frameworks, databases, UIs, and external services orbit it. The domain depends on nothing; everything depends on the domain.

**Dependencies point inward.** Outer layers know about inner layers; inner layers never know about outer layers. The compile-time / source-code dependency graph respects this rule absolutely.

**The application is independent of:**
- Frameworks (it can run without ASP.NET, Spring, Rails)
- UI (you can replace HTTP with CLI or message queue)
- Database (you can swap Postgres for an in-memory store for tests)
- External services (you can substitute fakes)
- Anything outside its own abstractions

**Three names, one idea.**
- **Hexagonal Architecture** (Alistair Cockburn, 2005) — "Ports and Adapters". The earliest name.
- **Onion Architecture** (Jeffrey Palermo, 2008) — concentric rings, dependencies inward.
- **Clean Architecture** (Robert C. Martin, 2017) — same structure, additional emphasis on Use Cases and the Dependency Rule.
Read the full skill on GitHub

Details

Skill name
hexagonal-clean-architecture
Path
plugins/engineering-practices/skills/hexagonal-clean-architecture/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Hexagonal Clean Architecture skill do?

Apply Alistair Cockburn's Hexagonal Architecture (Ports and Adapters), Jeffrey Palermo's Onion Architecture, and Robert C. Martin's Clean Architecture — the family of architectural styles that put the domain at the center, push frameworks and I/O to the edges, and enforce inward-pointing dependencies. Use when structuring a non-trivial application, separating business logic from delivery and persistence, deciding where ports live and how adapters plug in, or testing domain logic without spinning up infrastructure.

How do I install the Hexagonal Clean Architecture skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Hexagonal Clean Architecture popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

Heyreach Master

8

Freddy-CHEN-ux/00_claude_skills

Internal resource library for HeyReach integration. Contains shared API client, operation scripts, and reference documentation.

Software Development

Guardrails

5

bolasblack/claude-skills

Rendered guardrail framework: keep a repo's hard rules in one-rule-per-file GRL sources behind a compact router, and render only the rules a task needs. Use when gathering guardrail context before implementing or reviewing code, when creating, editing, retiring, or reviewing GRL rule files or .agents/guardrails/index.md, when running the guardrails CLI (validate, render, review-metadata, next-id), or when setting up, adopting, or bootstrapping a guardrail framework in a repo that does not have one yet. Do NOT use for ordinary lint rule authoring unless the lint rule backs a guardrail, for runt

Software Development

Hook Development

8

Freddy-CHEN-ux/00_claude_skills

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.