Hype Stack is built to work well with AI coding assistants. The repo includes structured rules and skills that teach AI agents how the codebase works, so they produce code that follows your conventions instead of guessing.
.cursor/rules/)24 rule files that cover every major area of the codebase:
| Area | Rules |
|---|---|
| Backend | Error handling, features structure, route validation, file uploads, deletion cascades, frontend URLs, general patterns |
| Frontend | Feature organization, styling, theming, data fetching |
| Testing | Backend testing, frontend testing, workflow conventions |
| Code style | Human voice, no em-dash, verification after changes |
| Infrastructure | Permissions, registry, CLI testing, pack SDK types |
These rules are always active. When an AI agent works in the repo, it follows the same conventions you'd enforce in code review.
.agents/skills/)6 skills that give AI agents deeper capabilities:
| Skill | What it does |
|---|---|
| brainstorming | Explores intent and requirements before building anything |
| create-pack | Guides pack creation with the right file structure |
| frontend-design | Produces polished, non-generic UI designs |
| hono | Builds Hono routes with proper patterns and testing |
| prisma-postgres | Handles database setup and provisioning |
| find-skills | Discovers and installs new skills |
Without rules, AI tools generate generic code. With rules, they generate code that fits your architecture. The AI knows to use validate() middleware instead of ctx.req.json(), throws ApplicationError instead of catching errors locally, and organizes features in <domain>/<feature>/ folders instead of flat structures.