# Build Hono JSX Pages and Interactive Interfaces

Hono interfaces need consistent layouts, asset handling, and clear boundaries between server and browser code. This skill guides server-rendered pages, form workflows, and focused client components without React.

## Install

```bash
npx skillstore add honojs/hono-jsx
```

## Metadata

- Status: approved
- Slug: honojs-hono-jsx
- Skillstore revision: r1
- Version status: missing
- Tree hash: c596c2214e5f26b3839be6d8011c35902b27d18d4911b0582a43bc9d4606a17b
- Author: honojs
- GitHub username: honojs
- Repository: https://github.com/honojs/skills/tree/e54ce51f6effaeb574ebd2629e89e086e14a2db3/skills/hono-jsx
- Ref: 7d2f58d20e866b878cc29805805579249eccde1a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 73
- Public page: https://skillstore.pages.dev/skills/honojs-hono-jsx
- Manifest: https://skillstore.pages.dev/api/skills/honojs-hono-jsx/manifest

## Capabilities

- Guide Cloudflare Workers project setup with Hono JSX, Vite plugins, generated binding types, and asset components.
- Define shared and nested layouts with jsxRenderer, typed layout properties, and page metadata.
- Structure HTML form submissions with Hono routes, validation guidance, error rendering, and redirects.
- Add browser behavior through plain DOM scripts or stateful hono/jsx/dom components.
- Explain stylesheet integration, component-scoped CSS, trusted HTML handling, and experimental streaming.
- Provide alternative Vite build patterns for Node and other supported runtimes.

## Use Cases

- Create a Workers Interface: Add server-rendered pages, shared navigation, and managed Vite assets to a Cloudflare Workers application.
- Build Accessible Form Workflows: Create HTML forms with server validation, visible errors, and redirects while keeping core tasks usable without client JavaScript.
- Review Hono Frontend Architecture: Check rendering boundaries, runtime configuration, binding types, and client asset delivery across an existing Hono project.

## Prompt Templates

### Create a First Page

```
Add a server-rendered home page to my Hono app using hono/jsx and jsxRenderer. Reuse the existing project structure and avoid React.
```

### Add a Validated Form

```
Build a Hono todo page with an HTML form. Validate submissions, preserve entered values on errors, and redirect after successful creation.
```

### Add Focused Client State

```
Add a stateful counter using hono/jsx/dom. Keep page content server-rendered, load browser assets through Vite, and include correct client TypeScript references.
```

### Review Rendering and Builds

```
Review my Hono JSX app for nested layout typing, binding type generation, Vite asset handling, and runtime-specific builds. Assess streaming only for slow data.
```

## Limitations

- Provides a single instruction document, not bundled application code, automated tests, or an executable generator.
- Targets Hono JSX rather than React applications or React component libraries.
- Refers to a separate hono skill for CLI usage, validation details, and broader framework guidance.
- Client components mount without hydration; streaming APIs are experimental and require careful evaluation.

## Best Practices

- Keep core content server-rendered and add browser state only where the interface requires it.
- Validate form input on the server and never pass untrusted input to raw HTML APIs.
- Generate runtime binding types and verify routes, typechecking, and production asset paths in the existing project.

## Anti Patterns

- Adding React dependencies or React-specific Vite plugins to a Hono JSX application.
- Moving essential page content into client-only containers that remain empty without JavaScript.
- Bypassing managed Vite asset components on Cloudflare or manually inventing runtime binding types.

## Security Audit

- Audited at: 2026-11-15T15:12:26.153\+00:00
- Summary: All 87 static findings are false positives from Markdown formatting, legitimate development commands, documentation links, and normal framework binding access. No evidence found of credential extraction, network reconnaissance, malicious execution, or prompt injection. This assessment covers the supplied SKILL.md, not dependency implementations or linked resources.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0
