Hono Backend

Build Hono applications using current official patterns. Before giving framework-specific guidance, consult the relevant page in the official Hono documentation; prefer the hono-docs MCP server when configured. Use app.request() or the repository package manager's Hono CLI to test endpoints.

Start and Topic Routing

Inspect the existing package manager, workspace layout, and deployment runtime before changing project structure. Do not initialize a repository inside an existing repository.

• Existing project: add Hono to the application package that owns the API.
• New standalone project: run the Hono creator with the chosen package manager, such as bun create hono@latest my-app or npm create hono@latest my-app.
• Existing monorepo: create or reuse an API workspace such as apps/api; keep its runtime dependencies in that workspace's package.json.

Select the actual deployment runtime during setup. Runtime choice controls the entrypoint, deployment, static-file, and WebSocket adapters.

Composition with Bun Tooling

When a Bun toolchain skill also applies, inherit its package-manager, workspace, TypeScript baseline, lint, format, hooks, and CI conventions. This skill still owns Hono routing, middleware, validation, API contracts, endpoint tests, and the Hono-specific Bun entrypoint. Keep Hono and its runtime integrations in the API workspace; keep repository-wide tooling at the monorepo root.

Composition with System Design