hono-architecture

To enforce Hono architecture consistency, use automated rules that validate route composition, middleware ordering, and database repository boundaries. This prevents architectural drift by ensuring route registration and handler typing align with established project conventions.

The best way to refactor Hono route modules to kebab-case naming is through automated remediation scripts. These scripts scan the folder structure and safely rename files, ensuring your TypeScript application adheres to strict architectural conventions without manual file management errors.

To align OpenAPI contracts with Hono route handlers, validate your handler typing and route registration against the OpenAPI definitions. This ensures typed RPC boundaries remain consistent and prevents contract mismatches during API feature development or refactoring.

Yes, you can manage Drizzle transaction boundaries by validating database access patterns. The Skill enforces explicit transaction management in Drizzle-backed services, ensuring database repository boundaries are maintained and preventing direct database access from route handlers.

Yes, the architecture enforcement requires the ripgrep dependency for scanning and validating the codebase. It operates on Hono-based TypeScript applications and relies on ripgrep to efficiently search and identify architectural violations across files.

Middleware ordering matters in Hono because incorrect sequencing can bypass authentication or alter request contexts before handlers execute. Enforcing strict middleware ordering ensures your API remains scalable, maintainable, and functionally secure across all route compositions.