Hexagonal Architecture Feature Scaffolder

Scaffold complete features across hexagonal architecture layers with dependency injection.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/svo/knowledge-matchmaker-corpus-indexer --skill hexagonal-architecture-feature-scaffolder-svo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Hexagonal Architecture Feature Scaffolder
Source: https://github.com/svo/knowledge-matchmaker-corpus-indexer/tree/main/.claude/skills/hexagonal-architecture-scaffolder
Command: npx skills add https://github.com/svo/knowledge-matchmaker-corpus-indexer --skill hexagonal-architecture-feature-scaffolder-svo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolding complete features across domain, application, infrastructure, and interface layers to enforce clean architecture and DI.

Core Features & Use Cases

  • Creates domain models, repositories, use cases, DTOs, controllers, and DI wiring following hexagonal architecture templates.
  • Ensures layer boundaries, separation of concerns, and consistent project structure for new features.
  • Use Case-oriented scaffolding to deliver vertical slice capabilities for any feature.

Quick Start

Run the hexagonal-architecture-scaffolder to scaffold a new feature.

Frequently Asked Questions about Hexagonal Architecture Feature Scaffolder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new feature across all hexagonal architecture layers?

Scaffolding a feature across hexagonal architecture layers creates domain models, repositories, use cases, DTOs, and controllers while enforcing layer boundaries and dependency injection. It generates consistent project structures for new vertical slices.

What is the best way to enforce clean architecture boundaries when adding new domain entities?

Enforcing clean architecture boundaries for new domain entities requires separating domain models from DTOs and defining repository interfaces explicitly. The scaffolder generates templates for domain, application, infrastructure, and interface code to ensure separation of concerns.

Can I generate use cases and API endpoints with dependency injection wiring automatically?

Generating use cases and API endpoints with dependency injection wiring is supported by applying hexagonal architecture templates. It creates the necessary DI wiring alongside controllers and use cases to deliver vertical slice capabilities.

Does hexagonal architecture scaffolding separate DTOs from domain models?

Hexagonal architecture scaffolding separates DTOs from domain models by enforcing layer boundaries and defining repository interfaces. This strict separation ensures consistent project structure and maintains domain-driven design principles across new features.

When do I need to scaffold a vertical slice for a new API endpoint?

Scaffolding a vertical slice for a new API endpoint is needed when adding capabilities that require proper layer separation across domain, application, infrastructure, and interface layers. It ensures dependency injection and domain boundaries are consistently enforced.