[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AWD6ZMMQ1914DRJSQZW6F7":3,"skill-same:01M7AWD6ZMMQ1914DRJSQZW6F7":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7AWD6ZMMQ1914DRJSQZW6F7","hono",null,"Build, structure, and ship web apps\u002Fsites with the Hono framework — the the user default for new sites and for converting React SPAs to SSR. Use when the user wants to create a Hono app, convert\u002Fremake a site in Hono, add SSR + islands on Cloudflare Workers, set up Hono routing\u002Fmiddleware\u002FJSX, choose between hono\u002Fjsx (server) and hono\u002Fjsx\u002Fdom (client), wire the Vite build, or asks \"is this Hono\", \"make it Hono\", \"Hono SSR\", \"Hono on Workers\", \"@hono\u002Fjsx\", \"islands\", \"hono framework\". Loads current, verified Hono API patterns so you leverage the framework fully instead of guessing from memory.","barkleesanders\u002Fclaude-code-starter","barkleesanders","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F30680901?v=4","01M7AW019CGBYWDA8MFJEN1JXC","Barklee Sanders","01M7AW01A5H994ASJ2QZPW67AV",4,"MIT","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fhono\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hono\ndescription: >-\n  Build, structure, and ship web apps\u002Fsites with the Hono framework — the\n  the user default for new sites and for converting React SPAs to SSR. Use when\n  the user wants to create a Hono app, convert\u002Fremake a site in Hono, add SSR +\n  islands on Cloudflare Workers, set up Hono routing\u002Fmiddleware\u002FJSX, choose\n  between hono\u002Fjsx (server) and hono\u002Fjsx\u002Fdom (client), wire the Vite build, or\n  asks \"is this Hono\", \"make it Hono\", \"Hono SSR\", \"Hono on Workers\", \"@hono\u002Fjsx\",\n  \"islands\", \"hono framework\". Loads current, verified Hono API patterns so you\n  leverage the framework fully instead of guessing from memory.\n---\n\n# Hono Framework — Full-Leverage Skill\n\nHono is a small, ultrafast web framework built on **Web Standards** (Request\u002FResponse,\n`fetch`). It runs on Cloudflare Workers, Deno, Bun, Node, and the edge. For the user's\nstack it is the **default for new sites** and the **target for React-SPA → SSR conversions**\n(global rule: \"Default to Hono SSR for new sites\", 2026-05-15).\n\n> **Ground-truth note:** every API in this skill was verified against `hono.dev` docs via\n> Context7 (`\u002Fwebsites\u002Fhono_dev`) on 2026-06-04. Before asserting a Hono API that is NOT in\n> these references, re-verify against `hono.dev` — do not invent middleware names, import\n> paths, or hook names from memory. Hono's API surface is small; if you can't find it in the\n> references or live docs, it probably doesn't exist under that name.\n\n## When to use this skill\n\n- Creating a new website or web app on Cloudflare Workers (or any edge runtime)\n- Converting\u002Fremaking an existing React\u002FVue\u002FSPA site into Hono SSR + islands\n- Adding server-rendered HTML, routing, middleware, or an API to an existing Hono worker\n- Deciding `hono\u002Fjsx` (server SSR) vs `hono\u002Fjsx\u002Fdom` (client hydration\u002Fislands)\n- Wiring the Vite build for a Hono Worker with interactive client islands\n- Any \"make it Hono \u002F is this Hono \u002F Hono SSR \u002F Hono on Workers\" request\n\n## The 90-second mental model\n\n1. **One `app = new Hono()`.** Routes are `app.get\u002Fpost\u002F...('\u002Fpath', handler)`. The handler\n   gets a single **Context** `c` and returns a `Response` (via `c.text`, `c.json`, `c.html`,\n   `c.redirect`, or a raw `Response`).\n2. **Server JSX is just a function that returns HTML.** `import { ... } from 'hono\u002Fjsx'`,\n   write components, `return c.html(\u003CPage\u002F>)`. No virtual DOM on the server — it renders to a\n   string. This is your SSR.\n3. **Interactivity = islands.** A small client bundle built with `hono\u002Fjsx\u002Fdom` mounts into a\n   placeholder via `render(\u003CWidget\u002F>, el)`. `useState`\u002F`useEffect` from `hono\u002Fjsx` work there.\n   A counter island is **2.8 KB brotli vs 47.8 KB for React** — that's the whole point.\n4. **`c.env` is your bindings**, typed via `new Hono\u003C{ Bindings }>()`. No `process.env` on\n   Workers.\n5. **Static assets** are served by the platform (`assets` in `wrangler.jsonc`), not by route\n   handlers. The Worker handles dynamic routes; the SPA\u002Fasset fallback handles the rest.\n\n## Core decision: server vs client JSX (do not mix import sources)\n\n| | Server (SSR) | Client (island) |\n|---|---|---|\n| Import | `hono\u002Fjsx` | `hono\u002Fjsx\u002Fdom` |\n| Renders to | HTML string (`c.html`) | live DOM (`render(node, el)`) |\n| `jsxImportSource` | `hono\u002Fjsx` (default) | `hono\u002Fjsx\u002Fdom` (set per client build) |\n| Hooks | for structure only | `useState`, `useEffect`, `useRef`, etc. are live |\n| Ship size | 0 KB to the browser | tiny (counter ≈ 2.8 KB brotli) |\n\nThe classic mistake is rendering an interactive component with `hono\u002Fjsx` and expecting clicks\nto work — server JSX has no event loop in the browser. Interactive = build it into the **client\nentry** with `hono\u002Fjsx\u002Fdom` and mount it.\n\n## Workflow for any Hono task\n\n1. **Identify the runtime + build.** Cloudflare Workers? Then `wrangler.jsonc` `main` =\n   server entry, `assets` for static, and a Vite config that emits BOTH a server bundle and a\n   client island bundle. See `references\u002Fcloudflare-workers-vite.md`.\n2. **Lay out routes + SSR pages** with `hono\u002Fjsx`. Shared `\u003CLayout>` via the `html` helper or\n   the `jsxRenderer` middleware. See `references\u002Fssr-jsx.md`.\n3. **Carve out islands** — only the genuinely interactive pieces (maps, charts, modals,\n   toggles). Each island = a client entry that `render()`s into an SSR'd `\u003Cdiv id=\"...\">`.\n   See `references\u002Fclient-islands.md`.\n4. **Add middleware** (logger, CORS, cache, secureHeaders, etc.) with `app.use()`. See\n   `references\u002Fcore-routing-middleware.md`.\n5. **Verify**: `c.html` returns 200 with real markup (curl it), island bundle loads and\n   hydrates (check the DOM updates), no `hono\u002Fjsx` import in client code and no\n   `hono\u002Fjsx\u002Fdom` in server code.\n\n## Converting a React SPA → Hono (the big one)\n\nRead `references\u002Freact-spa-to-hono-migration.md`. The short version:\n\n- **Pages → SSR JSX.** Each React Router route becomes a Hono route returning `c.html(\u003CPage\u002F>)`.\n  Static content (text, layout, data-driven markup) renders on the server — instant, SEO-friendly,\n  great Lighthouse.\n- **Interactive components → islands.** `react-leaflet` map, `d3` force graph, modals, anything\n  with `useState`\u002Fevent handlers → a `hono\u002Fjsx\u002Fdom` island OR keep the underlying lib\n  (Leaflet\u002FD3 are framework-agnostic) and mount it from a client entry. D3 and Leaflet don't\n  need React at all.\n- **Icons:** `lucide-react` is React-specific. On the server use inline SVG (or `lucide`'s\n  framework-agnostic SVG strings); don't import `lucide-react` into `hono\u002Fjsx`.\n- **Router:** delete `react-router`; routing is server-side in Hono. Client nav can be plain\n  `\u003Ca href>` (full SSR navigation) or a tiny island if you want SPA-like transitions.\n- **Data modules** (plain `.ts` exports) port over unchanged — import them into server pages.\n- **Don't big-bang it blindly.** Keep the build green at every step; convert page-by-page and\n  curl each route. A working SSR page with a missing island beats a broken全-rewrite.\n\n## 🛑 \"Using Hono\" means SSR — a Hono ROUTER in front of static HTML is NOT the default (2026-08-31)\n\n**The most likely way to think you built a Hono site and not have one:** `new Hono()` for the\nAPI, `secureHeaders()`, typed `Bindings` — all correct — and then the actual page is a\nhand-written `public\u002Findex.html` served through the `ASSETS` binding. Every Hono symbol is\npresent. Zero HTML is server-rendered. That is **Hono-as-router**, and it satisfies none of the\nreasons the Hono default exists (real markup to crawlers\u002Fcurl\u002FWayback, no CSR shell, FCP).\n\nIt passes every check you would naively run: `tsc` clean, `wrangler deploy --dry-run` rc=0,\n`import { Hono } from \"hono\"` right there at the top of the file.\n\n**The one-command test — run it before claiming a site is Hono:**\n```bash\ngrep -rn 'c\\.html(' src\u002F | grep -v node_modules     # ZERO hits => you have a router, not SSR\ngrep -rln 'hono\u002Fjsx' src\u002F                            # ZERO files => no server JSX exists\n```\nAny page a human reads must reach the browser via `c.html(\u003CPage\u002F>)`. `ASSETS.fetch` is for\n**assets** — `.js`, `.css`, images, fonts — never for the document.\n\n**Reference incident (2026-08-31, improvecortland).** Built the Worker in Hono, wrote the portal\nas `public\u002Findex.html`, and reported the site as built on Hono. The user asked *\"did you build\nthis on hono framework btw like \u002Fcode says to\"* — the honest answer was *partially*. The\nconversion afterwards was ~30 minutes and had one non-obvious constraint worth stealing:\n\n**Converting static-HTML → SSR when tests execute the shipped page.** The harnesses regex-\nextracted JS out of `public\u002Findex.html` and ran it, so deleting that file would have broken\nthem. The fix is better than the original on both axes: move the executable blocks into a real\n`public\u002Ffoil-core.js`, `\u003Cscript src>` it from the SSR page, and point the tests at that file.\nOne source, no HTML parsing in the test, and the tests still execute **the shipped bytes**.\nDeleting the old `index.html` then doubles as a free negative control — the suites would fail if\nthey were still reading it. Keep DOM-touching wiring in a separate `public\u002Fui.js`, because the\nharnesses run the core in plain Node with no `document`.\n\nAlso: JSX in a `.ts` file is `error TS1005: '>' expected`. Rename to `.tsx` **and** update\n`main` in `wrangler.toml` — the rename alone leaves the config pointing at a file that is gone.\n\n## Hard rules\n\n- **A page is not \"in Hono\" until it renders through `c.html(\u003CPage\u002F>)`.** A Hono router serving\n  static HTML via `ASSETS` is the anti-pattern above — grep `c.html(` before you claim SSR.\n- **Never mix `hono\u002Fjsx` and `hono\u002Fjsx\u002Fdom` in the same module.** Pick by where the code runs.\n- **No `process.env` on Workers** — use `c.env` (typed `Bindings`) or `env(c)` from `hono\u002Fadapter`.\n- **Don't hand-serve static files from route handlers** when the platform has an `assets` binding.\n- **Verify against live docs before using an unfamiliar Hono API** — the framework is small and\n  memory-invented middleware\u002Fhooks are the #1 failure mode.\n- **Client islands must be code-split** so SSR pages ship 0 JS except the island that page needs.\n\n## Reference files\n\n| File | Use when |\n|---|---|\n| `references\u002Fcore-routing-middleware.md` | Routing, Context (`c`), middleware, bindings, error handling |\n| `references\u002Fssr-jsx.md` | Server JSX, `c.html`, `html` helper, `jsxRenderer`, layouts, streaming |\n| `references\u002Fclient-islands.md` | `hono\u002Fjsx\u002Fdom`, `render()`, hooks, hydration, mounting D3\u002FLeaflet |\n| `references\u002Fcloudflare-workers-vite.md` | `wrangler.jsonc`, dual client\u002Fserver Vite build, assets, deploy |\n| `references\u002Freact-spa-to-hono-migration.md` | Step-by-step React-SPA → Hono conversion playbook |\n\nAll import paths and patterns in these files were verified against `hono.dev` on 2026-06-04.\n","# Hono Framework — Full-Leverage Skill\n\nHono is a small, ultrafast web framework built on **Web Standards** (Request\u002FResponse,\n`fetch`). It runs on Cloudflare Workers, Deno, Bun, Node, and the edge. For the user's\nstack it is the **default for new sites** and the **target for React-SPA → SSR conversions**\n(global rule: \"Default to Hono SSR for new sites\", 2026-05-15).\n\n> **Ground-truth note:** every API in this skill was verified against `hono.dev` docs via\n> Context7 (`\u002Fwebsites\u002Fhono_dev`) on 2026-06-04. Before asserting a Hono API that is NOT in\n> these references, re-verify against `hono.dev` — do not invent middleware names, import\n> paths, or hook names from memory. Hono's API surface is small; if you can't find it in the\n> references or live docs, it probably doesn't exist under that name.\n\n## When to use this skill\n\n- Creating a new website or web app on Cloudflare Workers (or any edge runtime)\n- Converting\u002Fremaking an existing React\u002FVue\u002FSPA site into Hono SSR + islands\n- Adding server-rendered HTML, routing, middleware, or an API to an existing Hono worker\n- Deciding `hono\u002Fjsx` (server SSR) vs `hono\u002Fjsx\u002Fdom` (client hydration\u002Fislands)\n- Wiring the Vite build for a Hono Worker with interactive client islands\n- Any \"make it Hono \u002F is this Hono \u002F Hono SSR \u002F Hono on Workers\" request\n\n## The 90-second mental model\n\n1. **One `app = new Hono()`.** Routes are `app.get\u002Fpost\u002F...('\u002Fpath', handler)`. The handler\n   gets a single **Context** `c` and returns a `Response` (via `c.text`, `c.json`, `c.html`,\n   `c.redirect`, or a raw `Response`).\n2. **Server JSX is just a function that returns HTML.** `import { ... } from 'hono\u002Fjsx'`,\n   write components, `return c.html(\u003CPage\u002F>)`. No virtual DOM on the server — it renders to a\n   string. This is your SSR.\n3. **Interactivity = islands.** A small client bundle built with `hono\u002Fjsx\u002Fdom` mounts into a\n   placeholder via `render(\u003CWidget\u002F>, el)`. `useState`\u002F`useEffect` from `hono\u002Fjsx` work there.\n   A counter island is **2.8 KB brotli vs 47.8 KB for React** — that's the whole point.\n4. **`c.env` is your bindings**, typed via `new Hono\u003C{ Bindings }>()`. No `process.env` on\n   Workers.\n5. **Static assets** are served by the platform (`assets` in `wrangler.jsonc`), not by route\n   handlers. The Worker handles dynamic routes; the SPA\u002Fasset fallback handles the rest.\n\n## Core decision: server vs client JSX (do not mix import sources)\n\n| | Server (SSR) | Client (island) |\n|---|---|---|\n| Import | `hono\u002Fjsx` | `hono\u002Fjsx\u002Fdom` |\n| Renders to | HTML string (`c.html`) | live DOM (`render(node, el)`) |\n| `jsxImportSource` | `hono\u002Fjsx` (default) | `hono\u002Fjsx\u002Fdom` (set per client build) |\n| Hooks | for structure only | `useState`, `useEffect`, `useRef`, etc. are live |\n| Ship size | 0 KB to the browser | tiny (counter ≈ 2.8 KB brotli) |\n\nThe classic mistake is rendering an interactive component with `hono\u002Fjsx` and expecting clicks\nto work — server JSX has no event loop in the browser. Interactive = build it into the **client\nentry** with `hono\u002Fjsx\u002Fdom` and mount it.\n\n## Workflow for any Hono task\n\n1. **Identify the runtime + build.** Cloudflare Workers? Then `wrangler.jsonc` `main` =\n   server entry, `assets` for static, and a Vite config that emits BOTH a server bundle and a\n   client island bundle. See `references\u002Fcloudflare-workers-vite.md`.\n2. **Lay out routes + SSR pages** with `hono\u002Fjsx`. Shared `\u003CLayout>` via the `html` helper or\n   the `jsxRenderer` middleware. See `references\u002Fssr-jsx.md`.\n3. **Carve out islands** — only the genuinely interactive pieces (maps, charts, modals,\n   toggles). Each island = a client entry that `render()`s into an SSR'd `\u003Cdiv id=\"...\">`.\n   See `references\u002Fclient-islands.md`.\n4. **Add middleware** (logger, CORS, cache, secureHeaders, etc.) with `app.use()`. See\n   `references\u002Fcore-routing-middleware.md`.\n5. **Verify**: `c.html` returns 200 with real markup (curl it), island bundle loads and\n   hydrates (check the DOM updates), no `hono\u002Fjsx` import in client code and no\n   `hono\u002Fjsx\u002Fdom` in server code.\n\n## Converting a React SPA → Hono (the big one)\n\nRead `references\u002Freact-spa-to-hono-migration.md`. The short version:\n\n- **Pages → SSR JSX.** Each React Router route becomes a Hono route returning `c.html(\u003CPage\u002F>)`.\n  Static content (text, layout, data-driven markup) renders on the server — instant, SEO-friendly,\n  great Lighthouse.\n- **Interactive components → islands.** `react-leaflet` map, `d3` force graph, modals, anything\n  with `useState`\u002Fevent handlers → a `hono\u002Fjsx\u002Fdom` island OR keep the underlying lib\n  (Leaflet\u002FD3 are framework-agnostic) and mount it from a client entry. D3 and Leaflet don't\n  need React at all.\n- **Icons:** `lucide-react` is React-specific. On the server use inline SVG (or `lucide`'s\n  framework-agnostic SVG strings); don't import `lucide-react` into `hono\u002Fjsx`.\n- **Router:** delete `react-router`; routing is server-side in Hono. Client nav can be plain\n  `\u003Ca href>` (full SSR navigation) or a tiny island if you want SPA-like transitions.\n- **Data modules** (plain `.ts` exports) port over unchanged — import them into server pages.\n- **Don't big-bang it blindly.** Keep the build green at every step; convert page-by-page and\n  curl each route. A working SSR page with a missing island beats a broken全-rewrite.\n\n## 🛑 \"Using Hono\" means SSR — a Hono ROUTER in front of static HTML is NOT the default (2026-08-31)\n\n**The most likely way to think you built a Hono site and not have one:** `new Hono()` for the\nAPI, `secureHeaders()`, typed `Bindings` — all correct — and then the actual page is a\nhand-written `public\u002Findex.html` served through the `ASSETS` binding. Every Hono symbol is\npresent. Zero HTML is server-rendered. That is **Hono-as-router**, and it satisfies none of the\nreasons the Hono default exists (real markup to crawlers\u002Fcurl\u002FWayback, no CSR shell, FCP).\n\nIt passes every check you would naively run: `tsc` clean, `wrangler deploy --dry-run` rc=0,\n`import { Hono } from \"hono\"` right there at the top of the file.\n\n**The one-command test — run it before claiming a site is Hono:**\n```bash\ngrep -rn 'c\\.html(' src\u002F | grep -v node_modules     # ZERO hits => you have a router, not SSR\ngrep -rln 'hono\u002Fjsx' src\u002F                            # ZERO files => no server JSX exists\n```\nAny page a human reads must reach the browser via `c.html(\u003CPage\u002F>)`. `ASSETS.fetch` is for\n**assets** — `.js`, `.css`, images, fonts — never for the document.\n\n**Reference incident (2026-08-31, improvecortland).** Built the Worker in Hono, wrote the portal\nas `public\u002Findex.html`, and reported the site as built on Hono. The user asked *\"did you build\nthis on hono framework btw like \u002Fcode says to\"* — the honest answer was *partially*. The\nconversion afterwards was ~30 minutes and had one non-obvious constraint worth stealing:\n\n**Converting static-HTML → SSR when tests execute the shipped page.** The harnesses regex-\nextracted JS out of `public\u002Findex.html` and ran it, so deleting that file would have broken\nthem. The fix is better than the original on both axes: move the executable blocks into a real\n`public\u002Ffoil-core.js`, `\u003Cscript src>` it from the SSR page, and point the tests at that file.\nOne source, no HTML parsing in the test, and the tests still execute **the shipped bytes**.\nDeleting the old `index.html` then doubles as a free negative control — the suites would fail if\nthey were still reading it. Keep DOM-touching wiring in a separate `public\u002Fui.js`, because the\nharnesses run the core in plain Node with no `document`.\n\nAlso: JSX in a `.ts` file is `error TS1005: '>' expected`. Rename to `.tsx` **and** update\n`main` in `wrangler.toml` — the rename alone leaves the config pointing at a file that is gone.\n\n## Hard rules\n\n- **A page is not \"in Hono\" until it renders through `c.html(\u003CPage\u002F>)`.** A Hono router serving\n  static HTML via `ASSETS` is the anti-pattern above — grep `c.html(` before you claim SSR.\n- **Never mix `hono\u002Fjsx` and `hono\u002Fjsx\u002Fdom` in the same module.** Pick by where the code runs.\n- **No `process.env` on Workers** — use `c.env` (typed `Bindings`) or `env(c)` from `hono\u002Fadapter`.\n- **Don't hand-serve static files from route handlers** when the platform has an `assets` binding.\n- **Verify against live docs before using an unfamiliar Hono API** — the framework is small and\n  memory-invented middleware\u002Fhooks are the #1 failure mode.\n- **Client islands must be code-split** so SSR pages ship 0 JS except the island that page needs.\n\n## Reference files\n\n| File | Use when |\n|---|---|\n| `references\u002Fcore-routing-middleware.md` | Routing, Context (`c`), middleware, bindings, error handling |\n| `references\u002Fssr-jsx.md` | Server JSX, `c.html`, `html` helper, `jsxRenderer`, layouts, streaming |\n| `references\u002Fclient-islands.md` | `hono\u002Fjsx\u002Fdom`, `render()`, hooks, hydration, mounting D3\u002FLeaflet |\n| `references\u002Fcloudflare-workers-vite.md` | `wrangler.jsonc`, dual client\u002Fserver Vite build, assets, deploy |\n| `references\u002Freact-spa-to-hono-migration.md` | Step-by-step React-SPA → Hono conversion playbook |\n\nAll import paths and patterns in these files were verified against `hono.dev` on 2026-06-04.\n",{"name":5,"description":7},"main","e7b39d448c7d905feed2b044d3ccdf60822596ab","skills\u002Fhono",0,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter","https:\u002F\u002Fgithub.com\u002Fbarkleesanders","barkleesanders.com","Stay Hungry, Stay Foolish","2026-11-06 08:47:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add barkleesanders\u002Fclaude-code-starter --skill hono",{"tool":39,"command":40},"bunx","bunx skills add barkleesanders\u002Fclaude-code-starter --skill hono",{"tool":42,"command":43},"pnpm","pnpm dlx skills add barkleesanders\u002Fclaude-code-starter --skill hono","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fhono\u002FSKILL.md",true,[47,53,57,61,65],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fclient-islands.md","REFERENCE","参考文档",4210,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fhono\u002Freferences\u002Fclient-islands.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fcloudflare-workers-vite.md",7211,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fhono\u002Freferences\u002Fcloudflare-workers-vite.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fcore-routing-middleware.md",5185,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fhono\u002Freferences\u002Fcore-routing-middleware.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Freact-spa-to-hono-migration.md",8642,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fhono\u002Freferences\u002Freact-spa-to-hono-migration.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fssr-jsx.md",5228,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fhono\u002Freferences\u002Fssr-jsx.md",[70,76,83,90,97,104],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7AWV75B37B6YKG7ZKGZ783F","zi-search","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fzi-search\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7AWTZA3JGK1T7V1HS543FG7","visualise","Render inline interactive visuals — SVG diagrams, HTML widgets, charts, and explainers — directly in the conversation. Use this skill whenever the user asks to visualize, diagram, chart, illustrate, or explain something visually, or when an explanation would genuinely benefit from a spatial\u002Finteractive diagram rather than text. Also triggers for: flowcharts, architecture diagrams, data visualizations, interactive explainers, comparison layouts, UI mockups, and any request containing 'show me', 'draw', 'map out', 'visualize', or 'diagram'. Even when the user doesn't explicitly ask for a visual, use this skill proactively when the topic has spatial, sequential, or systemic relationships that a diagram would clarify better than prose.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvisualise\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7AWTR056C3P9R3VS8YVM2WX","video","When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Runway,' 'Kling,' 'Pika,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social-content. For paid video ad creative, see ad-creative.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7AWTHTWBMTYZPMHHEYX3TTG","manim-video","Production pipeline for mathematical and technical animations using Manim Community Edition. Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories. Use when users request: animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos, or any programmatic animation with geometric\u002Fmathematical content.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-use\u002Fskills\u002Fmanim-video\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7AWTCXDJ9NWFQW51ENM8A2Z","video-use","Edit any video by conversation. Transcribe, cut, color grade, generate overlay animations, burn subtitles — for talking heads, montages, tutorials, travel, interviews. No presets, no menus. Ask questions, confirm the plan, execute, iterate, persist. Production-correctness rules are hard; everything else is artistic freedom.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-use\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7AWTA1D5FP895S33GHSA2G5","ui-improver","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fui-improver\u002FSKILL.md",[],[]]