🧩 hono × browser-extension

Ship browser extension on Hono without losing weeks to compliance.

Hono is a TypeScript natural fit for browser extension. GreatCTO auto-detects both — adds the browser-extension archetype overlay, wires browser-extension-specific gates, and runs 34 specialist agents around your existing Hono workflow.

$ npx great-cto init 🧩 See archetype →

What changes when GreatCTO joins your Hono project

Detection → overlay → gates → reviewers.

1 · DETECT

Stack + archetype

GreatCTO reads your package.json and detects hono + browser-extension archetype from signals: imports, file structure, env vars, README hints.

2 · OVERLAY

Archetype pack

Attaches the browser-extension archetype overlay: archetype-specific reviewer + compliance gates. Override if your specifics differ; the defaults are sensible for Hono-style projects.

3 · GATES

Hono-aware reviewers

qa-engineer runs tsc --strict / eslint / vitest --coverage; security-officer checks for prototype pollution + XSS sinks; performance-engineer reviews bundle size + cold-start times.

4 · MEMORY

Cross-project lessons

Bugs you've hit before in other Hono projects (connection-pool exhaustion, ORM N+1 queries, retry storms) — the agent's Step 0 includes the prior detection order. MTTR drops 94 % on second occurrence (methodology).

First 10 minutes

Concrete walkthrough.

$ cd my-hono-app && npx great-cto init
✓ scanning manifests… found package.json
✓ stack: hono (TypeScript)
✓ archetype: browser-extension
✓ overlay: applied
✓ 34 agents ready

$ /start "add browser-extension feature"
▸ architect drafting ARCH-browser-extension.md…
▸ pm decomposing into beads tasks…
⚐ gate:plan — your approval needed

Approve → 3 senior-devs run in parallel worktrees → 5 reviewers fan out in parallel → gate:ship → deploy. One real run walked stage-by-stage: /proof.