hashgraph-online/awesome-codex-plugins / plugins/alpoxdev/hypercore/skills/hyper-architecture
hyper-architecture
Verified[Hyper] Use this skill when the user asks for architecture, project setup, or performance work - building, auditing, restructuring, or reviewing project structure, routes, data or server boundaries, the lint/format/type tooling baseline (oxlint, Prettier, tsconfig, rustfmt, clippy), or build and runtime performance - in a Next.js App Router, TanStack Start, Vite with TanStack Router, Astro, Expo, Lynx (ReactLynx), Hono, Axum, Tauri v2, Electron, or Rust CLI, WASM, or MCP server project. It detects the stack from manifests and config files, routes each touched package of a monorepo separately, and applies the matching bundled stack guide, the shared setup baseline, and that stack's performance rules. Do not use it for stacks outside those eleven or for work that crosses no architecture, setup, or performance boundary, such as copy edits, a plain dependency bump, or one build failure.
rules/hono/conventions.md
View on GitHub# Code Conventions
> Hono project coding rules/hono
---
## Stable Compatibility Rule
Project tooling owns formatting and import order. Hono does not require kebab-case paths, arrow functions, or one universal import grouping; those are Hypercore conventions and must be reported as such.
- Inspect the formatter, linter, TypeScript mode, module resolution, aliases, generated files, and runtime before enforcing style.
- Preserve Hono's inferred route types; do not add broad annotations solely to satisfy a style preference.
- Prefer `unknown` at untrusted boundaries and narrow through validators or explicit guards.
- Keep `import type` when required by the compiler/linter and avoid runtime imports created only for types.
- Never hand-edit generated route trees, declarations, OpenAPI artifacts, or migrations unless their owning tool and repository workflow explicitly permit it.
- A path rename is behavioral: update case-sensitive imports, exports, tests, aliases, package exports, config, and generated references atomically.
## Folder And File Naming
> camelCase and PascalCase source paths are forbidden. Keep source folders and files in kebab-case.
| Type | Rule | Example |
|------|------|---------|
| General files | kebab-case | `create-app.ts`, `request-id.ts` |
| Route folders | kebab-case | `routes/user-profile/` |
| Feature folders | kebab-case | `services/user-profile/`, `repositories/audit-log/` |
| Database folders | kebab-case | `database/`, `drizzle/migrations/` |
| Handler files | kebab-case | `handlers.ts`, `list-users.ts` |
| Schema files | kebab-case | `schemas.ts`, `user-payload.ts` |
| Middleware | kebab-case | `auth.ts`, `request-id.ts` |
Allowed exceptions:
- Tool-required root files such as `package.json`, `tsconfig.json`, `drizzle.config.ts`, lockfiles, and generated declaration files
- Provider-generated migration artifacts when the configured migration tool requires a specific name
- Framework conventions already present in the repo, only when renaming would break external contracts
In `전체 수정` mode, scan all detected Hono source folders and files, then rename kebab-case violations when every import, test path, route reference, and config reference can be updated in the same change.
---
## TypeScript Rules
| Rule | Description | Example |
|------|-------------|---------|
| Function style | const arrow function, explicit return type | `const handler = (c: Context): Response => {}` |
| No any | Use unknown or concrete types | `const payload: unknown = await c.req.json()` |
| Type imports | Separate type imports | `import type { Context } from 'hono'` |
| App generics | Type `Bindings` and `Variables` when used | `new Hono<AppEnv>()` |
---
## Import Order
```ts
import { Hono } from 'hono'
import { createFactory } from 'hono/factory'
import { zValidator } from '@hono/zod-validator'
import { createApp } from '@/lib/create-app'
import { authMiddleware } from '@/middlewares/auth'
import { createUser } from '@/services/users/create-user'
import { userSchema } from './schemas'
import type { AppEnv } from '@/lib/types'
```
---
## Comment Style
- Prefer short block comments only where a code group needs orientation
- Do not add line-by-line narration
- Keep comments durable and architecture-oriented
## Sources
> Checked 2026-11-04. No external source outside this package's own references informed this file; official Hono behavior is delegated to [`references/official/hono/hono-docs.md`](../../references/official/hono/hono-docs.md), verified 2026-11-04.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |