[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MCDMN4GKZTSNCTG7PN8CXE":3,"skill-same:01M6MCDMN4GKZTSNCTG7PN8CXE":103},{"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":34,"publishedAt":56,"linkOnly":57,"markdownContent":58,"markdownBody":59,"frontMatter":60,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":74,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M6MCDMN4GKZTSNCTG7PN8CXE","htmx-endpoint-design",null,"Design and review htmx endpoint contracts for server-rendered HTML fragments. Use when adding or debugging hx-get, hx-post, hx-put, hx-patch, hx-delete, hx-target, hx-swap, hx-select, out-of-band swaps, HX-Trigger events, partial template responses, redirects, retargeting, or response headers.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fhtmx-endpoint-design\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55],"design","htmx endpoint design","htmx","endpoint","when","frontend","retargeting","headers","events","get","swaps","contracts","patch","select","template","server","ui","code","delete","debugging","review","2026-11-10 10:12:30",false,"---\nname: htmx-endpoint-design\ndescription: Design and review htmx endpoint contracts for server-rendered HTML fragments. Use when adding or debugging hx-get, hx-post, hx-put, hx-patch, hx-delete, hx-target, hx-swap, hx-select, out-of-band swaps, HX-Trigger events, partial template responses, redirects, retargeting, or response headers.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: htmx Endpoint Design\n  category: Frontend\n  tags: htmx,endpoints,html,server-driven-ui,frontend\n---\n\n# htmx Endpoint Design\n\nUse this skill when the hard part is the server\u002Fbrowser contract: which element makes the request, which endpoint handles it, what HTML comes back, and where that HTML lands.\n\n## Contract First\n\nDefine the endpoint contract before writing attributes:\n\n- **Request source**: the element that sends the request.\n- **HTTP method**: `GET` for safe reads; `POST`, `PUT`, `PATCH`, or `DELETE` for mutations when the server\u002Fframework supports them.\n- **Input data**: normal form fields, included elements, path params, or explicit values.\n- **Response shape**: full page, partial fragment, empty response, redirect, or event-only response.\n- **Swap target**: the element to replace or update.\n- **Follow-up effects**: events, out-of-band fragments, URL changes, focus changes, and messages.\n\n## Endpoint Workflow\n\n1. Run the same auth, permission, and data-loading logic for full-page and htmx requests.\n2. Branch late on whether the request is an htmx request.\n3. Reuse the same partial in the full-page render and the htmx response.\n4. Return a fragment whose root matches the intended `hx-target` when using `outerHTML`.\n5. Use response headers or events for cross-component effects instead of coupling unrelated targets.\n6. Test the normal request and the htmx request separately.\n\n## Requests\n\n- Prefer normal form encoding so server validation, CSRF, and file limitations are explicit.\n- Keep mutation requests same-origin unless the project has a deliberate CORS and CSRF design.\n- Use `hx-include` when one control must submit data from a nearby form or filter panel.\n- Use `hx-vals` only for small explicit values. Avoid secrets and avoid executable `js:` values; prefer form fields, hidden inputs, or URL parameters instead.\n- Debounce or throttle chatty triggers such as `keyup`, `input`, and polling.\n- Use real links and forms when possible, then enhance them with htmx attributes.\n\n## Responses\n\nChoose the smallest response that keeps the UI honest:\n\n| Situation | Response |\n| --- | --- |\n| Replace one component | Return that component fragment |\n| Update several unrelated components | Return primary fragment plus `hx-swap-oob` fragments |\n| Mutation succeeds and another element should refresh | Return `204` plus an event\u002Fheader when supported |\n| Validation fails | Return the bound form fragment with errors |\n| Browser should navigate | Return a normal redirect for non-htmx, and an htmx redirect\u002Flocation response for htmx |\n| Server needs a different target\u002Fswap | Use framework helpers or htmx response headers where available |\n\n## Targeting And Swapping\n\n- Use stable IDs for durable targets and keep them unique.\n- Use `hx-target=\"this\"` for self-contained components.\n- Use `outerHTML` when replacing the target element itself.\n- Use `innerHTML` when preserving the target shell and replacing only its contents.\n- Use insert swaps such as `beforeend` for appending rows, log entries, or feed items.\n- Use `hx-select` when the server returns a larger document but the client should extract one fragment.\n- Do not swap a parent that contains long-lived local browser state unless that state is intentionally reset.\n\n## Out-Of-Band Updates\n\nUse out-of-band swaps for shared chrome and secondary facts:\n\n- flash messages\n- cart counts\n- notification badges\n- summary totals\n- list counters\n- modal shells outside the main target\n\nKeep out-of-band fragments small and predictable. If many out-of-band updates are required for one action, consider returning the larger owner component instead.\n\n## Events\n\nUse events to decouple server results from browser-local behavior:\n\n- Fire a server-triggered event after save\u002Fdelete when another component should refresh.\n- Listen for htmx lifecycle events for instrumentation, custom confirmation, and cleanup.\n- Use custom events as boundaries between htmx and Alpine, plain JavaScript, or `_hyperscript`.\n- Keep event names domain-specific, such as `invoice:saved` or `filters:changed`.\n\n## Status Codes\n\n- Use `200` for normal fragment replacement, including many invalid form responses.\n- Use `204` when no visible fragment should be swapped.\n- Use redirects deliberately; do not let htmx silently insert a login page into a small target.\n- For polling, use the framework or htmx convention that stops polling when the server says the job is done.\n\n## Testing Checklist\n\n- Assert status code and key response headers.\n- Assert the partial contains the intended root element.\n- Assert the partial omits full-page chrome when it should.\n- Assert invalid forms render errors into the expected target.\n- Assert out-of-band fragments are present when secondary UI must change.\n- Assert redirects or client events are represented in headers, not only in body text.\n\n## Avoid\n\n- Do not create one endpoint that performs unrelated actions based on arbitrary request parameters.\n- Do not let templates become the authorization layer.\n- Do not return raw JSON for htmx UI updates unless the same endpoint must serve a real API client.\n- Do not use broad selectors that can hit multiple targets by accident.\n- Do not mix server-rendered truth with stale client-side copies of the same state.\n","# htmx Endpoint Design\n\nUse this skill when the hard part is the server\u002Fbrowser contract: which element makes the request, which endpoint handles it, what HTML comes back, and where that HTML lands.\n\n## Contract First\n\nDefine the endpoint contract before writing attributes:\n\n- **Request source**: the element that sends the request.\n- **HTTP method**: `GET` for safe reads; `POST`, `PUT`, `PATCH`, or `DELETE` for mutations when the server\u002Fframework supports them.\n- **Input data**: normal form fields, included elements, path params, or explicit values.\n- **Response shape**: full page, partial fragment, empty response, redirect, or event-only response.\n- **Swap target**: the element to replace or update.\n- **Follow-up effects**: events, out-of-band fragments, URL changes, focus changes, and messages.\n\n## Endpoint Workflow\n\n1. Run the same auth, permission, and data-loading logic for full-page and htmx requests.\n2. Branch late on whether the request is an htmx request.\n3. Reuse the same partial in the full-page render and the htmx response.\n4. Return a fragment whose root matches the intended `hx-target` when using `outerHTML`.\n5. Use response headers or events for cross-component effects instead of coupling unrelated targets.\n6. Test the normal request and the htmx request separately.\n\n## Requests\n\n- Prefer normal form encoding so server validation, CSRF, and file limitations are explicit.\n- Keep mutation requests same-origin unless the project has a deliberate CORS and CSRF design.\n- Use `hx-include` when one control must submit data from a nearby form or filter panel.\n- Use `hx-vals` only for small explicit values. Avoid secrets and avoid executable `js:` values; prefer form fields, hidden inputs, or URL parameters instead.\n- Debounce or throttle chatty triggers such as `keyup`, `input`, and polling.\n- Use real links and forms when possible, then enhance them with htmx attributes.\n\n## Responses\n\nChoose the smallest response that keeps the UI honest:\n\n| Situation | Response |\n| --- | --- |\n| Replace one component | Return that component fragment |\n| Update several unrelated components | Return primary fragment plus `hx-swap-oob` fragments |\n| Mutation succeeds and another element should refresh | Return `204` plus an event\u002Fheader when supported |\n| Validation fails | Return the bound form fragment with errors |\n| Browser should navigate | Return a normal redirect for non-htmx, and an htmx redirect\u002Flocation response for htmx |\n| Server needs a different target\u002Fswap | Use framework helpers or htmx response headers where available |\n\n## Targeting And Swapping\n\n- Use stable IDs for durable targets and keep them unique.\n- Use `hx-target=\"this\"` for self-contained components.\n- Use `outerHTML` when replacing the target element itself.\n- Use `innerHTML` when preserving the target shell and replacing only its contents.\n- Use insert swaps such as `beforeend` for appending rows, log entries, or feed items.\n- Use `hx-select` when the server returns a larger document but the client should extract one fragment.\n- Do not swap a parent that contains long-lived local browser state unless that state is intentionally reset.\n\n## Out-Of-Band Updates\n\nUse out-of-band swaps for shared chrome and secondary facts:\n\n- flash messages\n- cart counts\n- notification badges\n- summary totals\n- list counters\n- modal shells outside the main target\n\nKeep out-of-band fragments small and predictable. If many out-of-band updates are required for one action, consider returning the larger owner component instead.\n\n## Events\n\nUse events to decouple server results from browser-local behavior:\n\n- Fire a server-triggered event after save\u002Fdelete when another component should refresh.\n- Listen for htmx lifecycle events for instrumentation, custom confirmation, and cleanup.\n- Use custom events as boundaries between htmx and Alpine, plain JavaScript, or `_hyperscript`.\n- Keep event names domain-specific, such as `invoice:saved` or `filters:changed`.\n\n## Status Codes\n\n- Use `200` for normal fragment replacement, including many invalid form responses.\n- Use `204` when no visible fragment should be swapped.\n- Use redirects deliberately; do not let htmx silently insert a login page into a small target.\n- For polling, use the framework or htmx convention that stops polling when the server says the job is done.\n\n## Testing Checklist\n\n- Assert status code and key response headers.\n- Assert the partial contains the intended root element.\n- Assert the partial omits full-page chrome when it should.\n- Assert invalid forms render errors into the expected target.\n- Assert out-of-band fragments are present when secondary UI must change.\n- Assert redirects or client events are represented in headers, not only in body text.\n\n## Avoid\n\n- Do not create one endpoint that performs unrelated actions based on arbitrary request parameters.\n- Do not let templates become the authorization layer.\n- Do not return raw JSON for htmx UI updates unless the same endpoint must serve a real API client.\n- Do not use broad selectors that can hit multiple targets by accident.\n- Do not mix server-rendered truth with stale client-side copies of the same state.\n",{"name":5,"license":15,"metadata":61,"description":7,"compatibility":66},{"tags":62,"version":63,"category":64,"displayName":65},"htmx,endpoints,html,server-driven-ui,frontend","0.1.0","Frontend","htmx Endpoint Design","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fhtmx-endpoint-design",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill htmx-endpoint-design",{"tool":83,"command":84},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill htmx-endpoint-design",{"tool":86,"command":87},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill htmx-endpoint-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fhtmx-endpoint-design\u002FSKILL.md",true,[91,97],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"agents\u002Fopenai.yaml","REFERENCE","参考文档",315,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fhtmx-endpoint-design\u002Fagents\u002Fopenai.yaml",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"assets\u002Ficons8-code.svg","ASSET","资产文件",460,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fhtmx-endpoint-design\u002Fassets\u002Ficons8-code.svg",[104,113,121,129,137,145],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":112},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":112},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":112},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":112},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":112},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":112},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]