Which ORM is supported by these guidelines?

The skill is specifically optimized for Drizzle ORM, providing patterns for managing database sessions, transactions, and the Unit of Work (UoW) pattern.

How does it handle API documentation and validation?

It mandates a schema-driven approach using hono-openapi and zod-openapi to ensure that API documentation and request/response validation are always in sync.

How are tests implemented in this framework?

Testing guidelines are based on the official Hono documentation, prioritizing the use of app.request() to perform integration tests that verify end-to-end behavior.

What architecture does this skill use?

It follows Domain-Driven Design (DDD) principles, organizing code into four distinct layers: domain, application, infrastructure, and controller, with clear rules on dependency direction.

Can I use this for existing Hono projects?

Yes, the skill includes specific instructions for refactoring existing codebases to align with DDD principles and improved layer separation.

Hono DDD Architecture Guide

Name: Hono DDD Architecture Guide
Author: Higashi-Masafumi

byHigashi-Masafumi

API Development

Architects and refactors Hono backend services using Domain-Driven Design principles, Drizzle ORM, and schema-driven OpenAPI development.

About

This skill provides a comprehensive framework for building robust, scalable Hono backends following Domain-Driven Design (DDD) principles. It guides developers through creating well-defined layers—domain, application, infrastructure, and controller—while enforcing strict dependency directions and responsibility boundaries. By integrating hono-openapi and zod-openapi for schema-driven design, and Drizzle ORM for standardized database interactions, it ensures type-safety and maintainability. Whether starting a new project or refactoring an existing codebase, this skill provides the patterns, templates, and testing strategies needed for production-grade TypeScript APIs.

Key Features

Implements multi-layered DDD architecture (Domain, Application, Infrastructure, Controller)
Enforces schema-driven development with hono-openapi and zod-openapi integration
Standardizes Drizzle ORM usage with transaction and Unit of Work patterns
Provides automated testing strategies based on Hono's native app.request() method
Ensures code consistency via strict ESLint and Prettier configuration guidelines
0 GitHub stars

Use Cases

Starting a new Hono backend project with a scalable, production-ready architecture
Implementing type-safe OpenAPI documentation and request validation for Hono services
Refactoring an existing Hono codebase into a maintainable DDD structure

About

Key Features

Implements multi-layered DDD architecture (Domain, Application, Infrastructure, Controller)
Enforces schema-driven development with hono-openapi and zod-openapi integration
Standardizes Drizzle ORM usage with transaction and Unit of Work patterns
Provides automated testing strategies based on Hono's native app.request() method
Ensures code consistency via strict ESLint and Prettier configuration guidelines
0 GitHub stars

Use Cases

Starting a new Hono backend project with a scalable, production-ready architecture
Implementing type-safe OpenAPI documentation and request validation for Hono services
Refactoring an existing Hono codebase into a maintainable DDD structure