adapter-creator

Generate standardized Hexagonal Architecture adapter projects for .NET with IStartupRegister scaffolding.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/lcmassena/AI_Skills --skill adapter-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adapter-creator
Source: https://github.com/lcmassena/AI_Skills/tree/main/hexagonal-architect/adapter-creator
Command: npx skills add https://github.com/lcmassena/AI_Skills --skill adapter-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adapter project scaffolding is automated to reduce boilerplate and ensure consistent Hexagonal Architecture patterns.

Core Features & Use Cases

  • Standardized folder structure for new adapters (Adapters/<Category>/<ServiceName>/ with csproj, Services, Startup, and Settings).
  • Auto-generated project template builds; ensures DI registration via IStartupRegister and correct namespaces.
  • Supports common categories (Stream, Storage, Repository) and adheres to the project's shared patterns.

Quick Start

Run the adapter-creator with inputs for Category and ServiceName to generate the complete adapter scaffold under /Adapters.

Frequently Asked Questions about adapter-creator

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

FAQPage Schema
How do I scaffold a new adapter project for a hexagonal .NET application?

Scaffolding a hexagonal adapter project is automated by providing the Category and ServiceName inputs to generate the complete folder structure, csproj, Services, Startup, and Settings files under /Adapters.

What is the standard folder structure for hexagonal architecture adapters in .NET?

The standard structure uses an Adapters/<Category>/<ServiceName>/ directory containing the csproj, Services, Startup, and Settings scaffolding to ensure consistent hexagonal architecture patterns across the project.

Can I generate scaffolding for Stream, Storage, and Repository adapter categories?

Yes, adapter scaffolding supports generating projects for Stream, Storage, and Repository categories, automatically applying the shared patterns and conventions defined by the project's hexagonal architecture.

How does dependency injection registration work for generated .NET adapter projects?

Dependency injection registration is handled through an auto-generated IStartupRegister implementation in the Startup class, ensuring the adapter follows project conventions without hardcoding configuration values.

Do I need to manually configure namespaces and csproj files for new hexagonal adapters?

No, manual configuration is unnecessary because the generation process automatically creates the csproj file and applies correct namespaces to ensure the new adapter builds and follows project conventions immediately.