
Build high-converting landing pages with a simple 6-section framework. Use for landing page guidance.
Guide agents to organize code by functionality instead of technical file type. Use when adding features, refactoring project structure, reviewing architecture, colocating related code, or deciding where components, hooks, types, utilities, tests, styles, and API code should live.
Save team knowledge notes into ./knowledge/ with date-prefixed filenames. Every solved problem, discovered pattern, or key decision becomes searchable knowledge that makes future work easier. Use when the user wants to capture gotchas, errors, build issues, solutions, patterns, or decisions for future reference.
How to access Hono framework documentation.