[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BVCXBXM1MEQ0HJ2HPJ4NB9":3,"skill-same:01M7BVCXBXM1MEQ0HJ2HPJ4NB9":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BVCXBXM1MEQ0HJ2HPJ4NB9","generative_ui",null,"How to render rich interactive HTML widgets inline in the chat or as standalone artifacts. Use this skill when you want to show the user diagrams, data visualizations, interactive controls, educational walkthroughs, or any rich visual content beyond plain text and markdown.","nguyenhungtran18\u002Fskill-and-tool-tracker","nguyenhungtran18","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F297063550?v=4","01M7BV0BFPRRFP84F2ME0FYZ9D","01M7BV0BG83FA5P22NJV0GR0A5",1,"MIT","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fgenerative_ui\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: generative_ui\ndescription: How to render rich interactive HTML widgets inline in the chat or as standalone artifacts. Use this skill when you want to show the user diagrams, data visualizations, interactive controls, educational walkthroughs, or any rich visual content beyond plain text and markdown.\n---\n\n# Generative UI\n\nYou can render custom, rich, interactive user interfaces (inline widgets or\nlarger artifacts) directly in the chat. This is a great way to communicate\ncomplex information to the user, generate rich visualizations, and even create\nsmall interactive experiences for the user.\n\n## Workflow\n\n1.  **Create the HTML Artifact**: Use `write_to_file` to save a self-contained\n    `.html` file (using Tailwind CSS and inline JavaScript) to the artifact\n    directory. Set `UserFacing: true` in `ArtifactMetadata`.\n2.  **Embed Inline (optional)**: Include the `\u003Cagent-embed>` tag in your chat\n    response, if you decide this html artifact should be rendered inline in the\n    conversation:\n\n    ```\n    \u003Cagent-embed src=\"file:\u002F\u002F\u002F\u003Cartifact_path>\u002Fwidget.html\">\u003C\u002Fagent-embed>\n    ```\n\n## Constraints & Theming\n\n*   **External Assets & Tailwind CSS**: All external CDNs are blocked by CSP,\n    except for one allowlisted gstatic Tailwind dependency that you **CAN** and\n    **SHOULD** use to style your artifacts. Include the following script tag in\n    your `\u003Chead>` to enable Tailwind:\n\n    ```html\n    \u003Cscript src=\"https:\u002F\u002Fwww.gstatic.com\u002Fantigravity\u002Fweb\u002Fdev\u002Ftailwindcss.min.js\">\u003C\u002Fscript>\n    ```\n\n*   **Use Provided Theme Variables**: The iframe injects the app's semantic\n    design-system tokens, so widgets automatically match the host theme and the\n    user's custom colors. Surfaces (`--background`, `--content`, `--card`,\n    `--sidebar`), borders (`--border`), text (`--foreground`,\n    `--muted-foreground`, `--placeholder`), and accents\n    (`--primary`\u002F`--primary-foreground`, `--secondary`\u002F`--secondary-foreground`,\n    `--accent`) are all available. Typography is applied for you on the document\n    body — you do not need to set a font.\n\n*   **Text & Surface Colors**: Use semantic variables (`bg-[var(--card)]`,\n    `text-[var(--foreground)]`, `text-[var(--muted-foreground)]`)\n    instead of hardcoded dark\u002Flight utility classes (e.g., `bg-slate-900`,\n    `text-white`) to ensure high contrast across both light and dark themes.\n\n*   **Do Not Declare Local Fallbacks on `:root`**: Never define local color\n    fallbacks on `:root` in a `\u003Cstyle>` block; the host environment manages\n    theme variables dynamically.\n\n*   **HTML Boilerplate Template**: Recommended base template:\n\n    ```html\n    \u003C!DOCTYPE html>\n    \u003Chtml>\n    \u003Chead>\n      \u003Cscript src=\"https:\u002F\u002Fwww.gstatic.com\u002Fantigravity\u002Fweb\u002Fdev\u002Ftailwindcss.min.js\">\u003C\u002Fscript>\n    \u003C\u002Fhead>\n    \u003Cbody class=\"bg-transparent text-[var(--foreground)] antialiased p-5\">\n      \u003Cdiv class=\"bg-[var(--card)] text-[var(--foreground)] border border-[var(--border)] rounded-xl p-5 shadow-sm\">\n        \u003Ch2 class=\"text-[var(--foreground)] font-semibold text-lg\">Title\u003C\u002Fh2>\n        \u003Cp class=\"text-[var(--muted-foreground)] text-sm\">Description\u003C\u002Fp>\n        \u003C!-- Interactive content goes here -->\n      \u003C\u002Fdiv>\n    \u003C\u002Fbody>\n    \u003C\u002Fhtml>\n    ```\n\n*   **General styling**: Aim for a clean, premium aesthetic. For `\u003Ccanvas>`,\n    check `document.documentElement.classList.contains('light')` to adapt\n    colors.\n\n## Deciding on Placement (Inline vs. Standalone)\n\n**Default to artifact only** — reference the HTML artifact in your response and\nlet the user open it in the side pane. Consider inlining when the widget is\ncompact (comfortably under 500px tall) and directly illustrates the surrounding\nexplanation (e.g., a small educational widget, plot, or diagram). Larger, more\ncomplex content (data dashboards, simulations, app prototypes) should stay\nartifact-only. Always follow the user's explicit preference if stated.\n\n## Designing Inline Widgets (Cards & Transparency)\n\nWhen embedding inline in chat (`\u003Cagent-embed>`), style widgets as native chat\ncomponents:\n\n*   **Transparent Root Background**: Always set `\u003Cbody class=\"bg-transparent\n    ...\">` so the widget blends seamlessly into the chat container.\n*   **Card-Based Layouts**: Wrap inline content and controls in a card container\n    (as shown in the Boilerplate Template above) to provide elevation and\n    prevent loose text in light mode.\n*   **Standalone Artifacts**: For full-page side-pane artifacts (like\n    dashboards), use a solid background (e.g., `bg-[var(--background)]`).\n\n## Sizing Inline Embeds\n\nFor inline embeds, it is important to think **small and compact**.\n\nInline embeds only have a **500px** height viewport. Past that the widget\nscrolls inside a small box and the user sees only a fragment of what you built,\nso don't build inlined widgets that are too tall.\n\n*   **Do not set a `height` attribute on `\u003Cagent-embed>`.** It is ignored.\n*   **Think compact** Think carefully about designing something that is compact\n    and fits nicely inline in the chat height budget.\n*   **If the idea genuinely needs more room, make it a standalone artifact.** A\n    scrolling inline widget is usually wrong — full-height in the side pane\n    beats cropped in the chat.\n\nAfter generating the artifact, consider whether it is sufficiently compact to be\nuseful inline and adjust if needed.\n\n> [!IMPORTANT] Never size an inline widget relative to the viewport: no\n> `h-screen`, `min-h-screen`, `100vh`, or `height: 100%` on a top-level\n> container. The frame's viewport is derived from your content, so these feed\n> themselves and the widget collapses to a sliver. Use padding for breathing\n> room instead.\n","# Generative UI\n\nYou can render custom, rich, interactive user interfaces (inline widgets or\nlarger artifacts) directly in the chat. This is a great way to communicate\ncomplex information to the user, generate rich visualizations, and even create\nsmall interactive experiences for the user.\n\n## Workflow\n\n1.  **Create the HTML Artifact**: Use `write_to_file` to save a self-contained\n    `.html` file (using Tailwind CSS and inline JavaScript) to the artifact\n    directory. Set `UserFacing: true` in `ArtifactMetadata`.\n2.  **Embed Inline (optional)**: Include the `\u003Cagent-embed>` tag in your chat\n    response, if you decide this html artifact should be rendered inline in the\n    conversation:\n\n    ```\n    \u003Cagent-embed src=\"file:\u002F\u002F\u002F\u003Cartifact_path>\u002Fwidget.html\">\u003C\u002Fagent-embed>\n    ```\n\n## Constraints & Theming\n\n*   **External Assets & Tailwind CSS**: All external CDNs are blocked by CSP,\n    except for one allowlisted gstatic Tailwind dependency that you **CAN** and\n    **SHOULD** use to style your artifacts. Include the following script tag in\n    your `\u003Chead>` to enable Tailwind:\n\n    ```html\n    \u003Cscript src=\"https:\u002F\u002Fwww.gstatic.com\u002Fantigravity\u002Fweb\u002Fdev\u002Ftailwindcss.min.js\">\u003C\u002Fscript>\n    ```\n\n*   **Use Provided Theme Variables**: The iframe injects the app's semantic\n    design-system tokens, so widgets automatically match the host theme and the\n    user's custom colors. Surfaces (`--background`, `--content`, `--card`,\n    `--sidebar`), borders (`--border`), text (`--foreground`,\n    `--muted-foreground`, `--placeholder`), and accents\n    (`--primary`\u002F`--primary-foreground`, `--secondary`\u002F`--secondary-foreground`,\n    `--accent`) are all available. Typography is applied for you on the document\n    body — you do not need to set a font.\n\n*   **Text & Surface Colors**: Use semantic variables (`bg-[var(--card)]`,\n    `text-[var(--foreground)]`, `text-[var(--muted-foreground)]`)\n    instead of hardcoded dark\u002Flight utility classes (e.g., `bg-slate-900`,\n    `text-white`) to ensure high contrast across both light and dark themes.\n\n*   **Do Not Declare Local Fallbacks on `:root`**: Never define local color\n    fallbacks on `:root` in a `\u003Cstyle>` block; the host environment manages\n    theme variables dynamically.\n\n*   **HTML Boilerplate Template**: Recommended base template:\n\n    ```html\n    \u003C!DOCTYPE html>\n    \u003Chtml>\n    \u003Chead>\n      \u003Cscript src=\"https:\u002F\u002Fwww.gstatic.com\u002Fantigravity\u002Fweb\u002Fdev\u002Ftailwindcss.min.js\">\u003C\u002Fscript>\n    \u003C\u002Fhead>\n    \u003Cbody class=\"bg-transparent text-[var(--foreground)] antialiased p-5\">\n      \u003Cdiv class=\"bg-[var(--card)] text-[var(--foreground)] border border-[var(--border)] rounded-xl p-5 shadow-sm\">\n        \u003Ch2 class=\"text-[var(--foreground)] font-semibold text-lg\">Title\u003C\u002Fh2>\n        \u003Cp class=\"text-[var(--muted-foreground)] text-sm\">Description\u003C\u002Fp>\n        \u003C!-- Interactive content goes here -->\n      \u003C\u002Fdiv>\n    \u003C\u002Fbody>\n    \u003C\u002Fhtml>\n    ```\n\n*   **General styling**: Aim for a clean, premium aesthetic. For `\u003Ccanvas>`,\n    check `document.documentElement.classList.contains('light')` to adapt\n    colors.\n\n## Deciding on Placement (Inline vs. Standalone)\n\n**Default to artifact only** — reference the HTML artifact in your response and\nlet the user open it in the side pane. Consider inlining when the widget is\ncompact (comfortably under 500px tall) and directly illustrates the surrounding\nexplanation (e.g., a small educational widget, plot, or diagram). Larger, more\ncomplex content (data dashboards, simulations, app prototypes) should stay\nartifact-only. Always follow the user's explicit preference if stated.\n\n## Designing Inline Widgets (Cards & Transparency)\n\nWhen embedding inline in chat (`\u003Cagent-embed>`), style widgets as native chat\ncomponents:\n\n*   **Transparent Root Background**: Always set `\u003Cbody class=\"bg-transparent\n    ...\">` so the widget blends seamlessly into the chat container.\n*   **Card-Based Layouts**: Wrap inline content and controls in a card container\n    (as shown in the Boilerplate Template above) to provide elevation and\n    prevent loose text in light mode.\n*   **Standalone Artifacts**: For full-page side-pane artifacts (like\n    dashboards), use a solid background (e.g., `bg-[var(--background)]`).\n\n## Sizing Inline Embeds\n\nFor inline embeds, it is important to think **small and compact**.\n\nInline embeds only have a **500px** height viewport. Past that the widget\nscrolls inside a small box and the user sees only a fragment of what you built,\nso don't build inlined widgets that are too tall.\n\n*   **Do not set a `height` attribute on `\u003Cagent-embed>`.** It is ignored.\n*   **Think compact** Think carefully about designing something that is compact\n    and fits nicely inline in the chat height budget.\n*   **If the idea genuinely needs more room, make it a standalone artifact.** A\n    scrolling inline widget is usually wrong — full-height in the side pane\n    beats cropped in the chat.\n\nAfter generating the artifact, consider whether it is sufficiently compact to be\nuseful inline and adjust if needed.\n\n> [!IMPORTANT] Never size an inline widget relative to the viewport: no\n> `h-screen`, `min-h-screen`, `100vh`, or `height: 100%` on a top-level\n> container. The frame's viewport is derived from your content, so these feed\n> themselves and the widget collapses to a sliver. Use padding for breathing\n> room instead.\n",{"name":5,"description":7},"main","900ea3c9eb045fd5b0317dc1103777ecf3ea4aeb","skills\u002Fgenerative_ui",0,"https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker","https:\u002F\u002Fnguyenhungtran18.github.io\u002Fskill-and-tool-tracker\u002F","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18","2026-08-31 18:36:09",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add nguyenhungtran18\u002Fskill-and-tool-tracker --skill generative_ui",{"tool":37,"command":38},"bunx","bunx skills add nguyenhungtran18\u002Fskill-and-tool-tracker --skill generative_ui",{"tool":40,"command":41},"pnpm","pnpm dlx skills add nguyenhungtran18\u002Fskill-and-tool-tracker --skill generative_ui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fgenerative_ui\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7BVP4P83TK60JZ4P8RP9VP7","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fxcode_project_setup\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7BVP01K4CSJJ8G90FT8S2D5","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7BVNY22GXD871GYTSH599F1","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7BVNQWF24RNKA8A4KM2HJ3T","workflow-skill-creator","Distills a completed user workflow or interaction into a reusable agent skill. Use when the user asks to turn their workflow, interaction, or multi-step process into a skill, or when they say \"make this a skill\", \"create a skill from what we just did\", \"package this workflow\" or similar. Do not use for creating skills from scratch without an existing workflow (use a generic skill-creator for that).","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow_skill_creator\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7BVNNY67XPCQAQHY3FBKDGC","verify-and-stop","Prove existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile proof.","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fverify-and-stop\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7BVNKB4Z7SZT85B73ZZ90Y6","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fnguyenhungtran18\u002Fskill-and-tool-tracker\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[]]