App Recipes

Hyper-Dank recipes are adoption maps. They show which packages compose well together, what the shared code owns, what the app still owns, and which checks prove the boundary.

Recipe docsRecipes

Choose the recipe closest to the app you are building. Each page names the required packages, app-owned responsibilities, verification path, and references.

Hono and HTMX Server app Authenticated apps where the server owns state, validation, persistence, and fragments. Content Static blog Docs, journals, release notes, and content-heavy pages served from static hosting. Operations Dashboard or admin tool Dense screens for scanning, filtering, pagination, status, and action review. Browser only Static demo GitHub Pages demos or offline examples that should not assume a server. Automation Script consumer Repeatable local automation without copying one-off process and server helpers. Static site Static-content generator Markdown pages, pretty routes, copied assets, and a custom document shell.

Recipe Protection

Recipe examples are protected by consumer-compatibility tests that import public package paths. Run bun run verify before shipping recipe or package-boundary changes.