[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79CNG9SVC7XD14AV45AAC8S":3,"skill-same:01M79CNG9SVC7XD14AV45AAC8S":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79CNG9SVC7XD14AV45AAC8S","artifact-design",null,"Build a self-contained HTML visual written to disk — page, report, dashboard, mockup, diagram, or poster. Load before the first line of markup or CSS whenever something has to look right, or a redesign is asked for. Not for app code the project's own design system already governs.","kolisachint\u002Fhoocode","kolisachint","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F39264878?v=4","01M725R61G8RKBF4Q0BKXPRE1A","Sachin Koli","01M79CMYXDFWTAXE44YV75W861",2,"MIT","https:\u002F\u002Fgithub.com\u002Fkolisachint\u002Fhoocode\u002Fblob\u002Fmain\u002Fcrates\u002Fhoocode-code-resources\u002Ftemplates\u002Fskills\u002Fartifact-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: artifact-design\ndescription: Build a self-contained HTML visual written to disk — page, report, dashboard, mockup, diagram, or poster. Load before the first line of markup or CSS whenever something has to look right, or a redesign is asked for. Not for app code the project's own design system already governs.\nallowed-tools: Read, Write, Edit, CodeSearch\n---\n\n# Designing a visual\n\nhoocode writes visuals as one self-contained `.html` file on disk. There is no\nhost, no CSP, and no gallery: fonts and libraries may come from a CDN or from\nlocal files, and the page is yours to lay out however the subject demands. The\nconstraint that remains is the only one that ever mattered — it has to be good.\n\n## First, read the request\n\nDecide the treatment, not whether to design. Every visual gets real typographic\nhierarchy, considered spacing, and a deliberate palette. What varies is how far\npast that you go.\n\n- **Utilitarian** — a report, a plan, a status page, a diagram. Most requests.\n  Make it clean and well-composed. Skip the oversized hero. Keep flourishes few.\n- **Editorial** — a landing page, a poster, something the user will show other\n  people. Take a real point of view and one deliberate risk.\n\nWhen unsure, build the well-composed version. A restrained page is never wrong;\nan over-designed one sometimes is.\n\n## Honor what already exists\n\nLook before you invent. If the repo has a design system — a tokens file, a\ntheme, CSS variables, an existing stylesheet, a brand section in a project\ncontext file — use it. Precedence is always:\n\n1. What the user asked for, in their words\n2. The project's existing system\n3. Your own choices\n\nYour choices fill gaps. They never override the first two.\n\n## Write the plan before the markup\n\nThis is the part that does the work. Before any code, write down:\n\n- **Color** — 4 to 6 named hex values. Name them by role (`ink`, `ground`,\n  `accent`, `muted`), not by hue.\n- **Type** — at least two faces with distinct jobs: one with character for\n  display, one comfortable for body text, and a third for data or captions if\n  the content needs it. Name the fallback stack for each.\n- **Layout** — the structural idea in one or two sentences.\n\nThen build from the plan and derive every color and type decision from it. A\npage assembled without a plan reads as assembled without a plan.\n\n## Fundamentals\n\n**Ground it in the subject.** One concrete subject, one audience, one job for\nthe page. Distinctive choices come from the subject's own world — its materials,\nits vocabulary, how people in it actually talk. Use real content throughout.\nNever lorem, never placeholder rows.\n\n**Type carries the page,** including when the page is not about type. Keep\nrunning text near 65 characters wide. Set a scale and stay on it. Give headings\n`text-wrap: balance`, give body text line-height room, give uppercase labels a\nlittle letter-spacing. Always declare a real fallback stack — a silent fallback\nis the most common way a good design ships looking wrong.\n\n**Pick the neutrals.** A pure mid-grey reads as unconsidered. Bias the greys\nslightly toward the accent hue and they read as chosen. Pure white and near-black\nare fine grounds when the subject wants them; the point is that you decided.\n\n**Let layout do the spacing.** Flex or grid with `gap`, not per-element margins\nthat collapse or double unpredictably. Wide content — tables, code blocks,\ndiagrams — gets its own `overflow-x: auto` container so the page body never\nscrolls sideways. Use `font-variant-numeric: tabular-nums` wherever digits line\nup in a column.\n\n**Design both themes.** A local page sees only `prefers-color-scheme`, so this\nis simpler here than on a hosted target: define the complete palette as custom\nproperties on `:root`, redefine only those properties inside\n`@media (prefers-color-scheme: dark)`, and style every component through the\nproperties. Never give a color its only definition inside the media block — that\nis how a page ends up rendering one theme's text on the other theme's ground.\nSet an explicit `background` on `body`. Give the second theme the same attention\nas the first rather than inverting it mechanically; check that the accent still\nworks on both grounds. A page that deliberately commits to one visual world may\nstay single-theme, but then paint every color explicitly so it holds either way.\n\n**Structure should encode something true.** Numbered markers, eyebrows,\ndividers, and section labels are information, not decoration. Number things only\nwhen the order actually matters to the reader.\n\n**When it is a UI, not a document,** the craft shifts from typography to\ninformation design. A dashboard is scanned, not read. Put the summary above the\ndetail. Encode state in form as well as in number — a pill, a chip, a severity\nstripe — so what needs attention is visible at a glance. Semantic color (good,\nwarning, critical) is a separate system from your accent and does not count as\nusing it. Anything interactive should look interactive.\n\n## Avoid the generated look\n\nMachine-generated design keeps landing on the same handful of looks. When the\nuser has specified a direction, follow it exactly, including if it is one of\nthese. When nothing is specified, do not spend the freedom here:\n\n- Warm cream ground, serif display face, terracotta accent\n- Near-black ground with a single acid-green or vermilion pop\n- Hairline rules and dense columns imitating a broadsheet\n- Purple-to-blue gradient hero on white\n- Inter or Space Grotesk chosen as the safe default\n- Emoji as section markers\n- Everything centered\n- Uniform large corner radii on every surface\n- A colored accent rail down the side of every card\n\n## Words are design material\n\nWrite from the reader's side of the screen. Name things the way they would name\nthem, not the way the system is built. Active voice. A control says exactly what\nit does, and the confirmation matches it. Errors say what went wrong and what to\ndo about it. Specific beats clever.\n\nGive the page a real `\u003Ctitle>` — a short, specific noun phrase, not a category\nlabel and not a name with an explainer bolted on after a dash.\n\n## Libraries, and why the answer is usually none\n\nA hosted page and a file on disk fail differently, and that decides this. A\nhosted page is always viewed online, so a CDN dependency is free. A file gets\nmoved, attached to mail, and opened on a laptop in a tunnel — and there a\nruntime dependency does not degrade, it collapses. Tailwind from a CDN with no\nnetwork is an unstyled document. React from a CDN with no network is a blank\none.\n\nSo the default is no runtime dependency at all. Write plain CSS; modern CSS has\ncustom properties, grid, `clamp()`, and container queries, and a page that needs\na utility framework to be laid out usually needs a clearer layout instead.\n\nThere is no build step here and nothing bundles this file, so a framework that\nexpects one — Vite, a JSX pipeline, anything importing bare module specifiers —\nis not an option regardless.\n\nWhen a library genuinely earns its place, and that is mostly charting or syntax\nhighlighting rather than layout:\n\n- Inline it into the file if its licence permits, and the page stays whole.\n- Otherwise pin an exact version, give the feature a readable fallback for when\n  the script does not load, and tell the user the page needs network.\n\nWebfonts are the one dependency that degrades gracefully, because a real\nfallback stack keeps the page readable when the link fails. Use one, and always\ndeclare the stack.\n\n## Build cleanly\n\n- Watch selector specificity. Type-level and element-level selectors fighting\n  over the same padding is how spacing silently comes undone.\n- Close every non-void element and double-quote every attribute.\n- Give keyboard focus a visible state.\n- Respect `prefers-reduced-motion`.\n- For generative or decorative graphics, reach for Canvas or WebGL rather than\n  hand-authoring long SVG path data.\n- Before finishing, scan the stylesheet for any color declared only inside a\n  media query.\n\n## Delivering it\n\nWrite one self-contained `.html` file. Inline the page's own CSS and JS; embed\nsmall assets as data URIs so the file survives being moved or sent to someone.\n\nPut it where the user would expect it — alongside the data it visualizes, or in\nthe directory they named. Then give them the path as a markdown link with a\n`file:\u002F\u002F` URL:\n\n```\n[tokens.html](file:\u002F\u002F\u002Fabs\u002Fpath\u002Fto\u002Ftokens.html)\n```\n\nhoocode's markdown renderer turns that into an OSC 8 hyperlink wherever the\nterminal supports one, so it is clickable in kitty, iTerm2, WezTerm and others,\nand still readable as plain text everywhere else. Offer to open it rather than\nopening it unasked.\n\n","# Designing a visual\n\nhoocode writes visuals as one self-contained `.html` file on disk. There is no\nhost, no CSP, and no gallery: fonts and libraries may come from a CDN or from\nlocal files, and the page is yours to lay out however the subject demands. The\nconstraint that remains is the only one that ever mattered — it has to be good.\n\n## First, read the request\n\nDecide the treatment, not whether to design. Every visual gets real typographic\nhierarchy, considered spacing, and a deliberate palette. What varies is how far\npast that you go.\n\n- **Utilitarian** — a report, a plan, a status page, a diagram. Most requests.\n  Make it clean and well-composed. Skip the oversized hero. Keep flourishes few.\n- **Editorial** — a landing page, a poster, something the user will show other\n  people. Take a real point of view and one deliberate risk.\n\nWhen unsure, build the well-composed version. A restrained page is never wrong;\nan over-designed one sometimes is.\n\n## Honor what already exists\n\nLook before you invent. If the repo has a design system — a tokens file, a\ntheme, CSS variables, an existing stylesheet, a brand section in a project\ncontext file — use it. Precedence is always:\n\n1. What the user asked for, in their words\n2. The project's existing system\n3. Your own choices\n\nYour choices fill gaps. They never override the first two.\n\n## Write the plan before the markup\n\nThis is the part that does the work. Before any code, write down:\n\n- **Color** — 4 to 6 named hex values. Name them by role (`ink`, `ground`,\n  `accent`, `muted`), not by hue.\n- **Type** — at least two faces with distinct jobs: one with character for\n  display, one comfortable for body text, and a third for data or captions if\n  the content needs it. Name the fallback stack for each.\n- **Layout** — the structural idea in one or two sentences.\n\nThen build from the plan and derive every color and type decision from it. A\npage assembled without a plan reads as assembled without a plan.\n\n## Fundamentals\n\n**Ground it in the subject.** One concrete subject, one audience, one job for\nthe page. Distinctive choices come from the subject's own world — its materials,\nits vocabulary, how people in it actually talk. Use real content throughout.\nNever lorem, never placeholder rows.\n\n**Type carries the page,** including when the page is not about type. Keep\nrunning text near 65 characters wide. Set a scale and stay on it. Give headings\n`text-wrap: balance`, give body text line-height room, give uppercase labels a\nlittle letter-spacing. Always declare a real fallback stack — a silent fallback\nis the most common way a good design ships looking wrong.\n\n**Pick the neutrals.** A pure mid-grey reads as unconsidered. Bias the greys\nslightly toward the accent hue and they read as chosen. Pure white and near-black\nare fine grounds when the subject wants them; the point is that you decided.\n\n**Let layout do the spacing.** Flex or grid with `gap`, not per-element margins\nthat collapse or double unpredictably. Wide content — tables, code blocks,\ndiagrams — gets its own `overflow-x: auto` container so the page body never\nscrolls sideways. Use `font-variant-numeric: tabular-nums` wherever digits line\nup in a column.\n\n**Design both themes.** A local page sees only `prefers-color-scheme`, so this\nis simpler here than on a hosted target: define the complete palette as custom\nproperties on `:root`, redefine only those properties inside\n`@media (prefers-color-scheme: dark)`, and style every component through the\nproperties. Never give a color its only definition inside the media block — that\nis how a page ends up rendering one theme's text on the other theme's ground.\nSet an explicit `background` on `body`. Give the second theme the same attention\nas the first rather than inverting it mechanically; check that the accent still\nworks on both grounds. A page that deliberately commits to one visual world may\nstay single-theme, but then paint every color explicitly so it holds either way.\n\n**Structure should encode something true.** Numbered markers, eyebrows,\ndividers, and section labels are information, not decoration. Number things only\nwhen the order actually matters to the reader.\n\n**When it is a UI, not a document,** the craft shifts from typography to\ninformation design. A dashboard is scanned, not read. Put the summary above the\ndetail. Encode state in form as well as in number — a pill, a chip, a severity\nstripe — so what needs attention is visible at a glance. Semantic color (good,\nwarning, critical) is a separate system from your accent and does not count as\nusing it. Anything interactive should look interactive.\n\n## Avoid the generated look\n\nMachine-generated design keeps landing on the same handful of looks. When the\nuser has specified a direction, follow it exactly, including if it is one of\nthese. When nothing is specified, do not spend the freedom here:\n\n- Warm cream ground, serif display face, terracotta accent\n- Near-black ground with a single acid-green or vermilion pop\n- Hairline rules and dense columns imitating a broadsheet\n- Purple-to-blue gradient hero on white\n- Inter or Space Grotesk chosen as the safe default\n- Emoji as section markers\n- Everything centered\n- Uniform large corner radii on every surface\n- A colored accent rail down the side of every card\n\n## Words are design material\n\nWrite from the reader's side of the screen. Name things the way they would name\nthem, not the way the system is built. Active voice. A control says exactly what\nit does, and the confirmation matches it. Errors say what went wrong and what to\ndo about it. Specific beats clever.\n\nGive the page a real `\u003Ctitle>` — a short, specific noun phrase, not a category\nlabel and not a name with an explainer bolted on after a dash.\n\n## Libraries, and why the answer is usually none\n\nA hosted page and a file on disk fail differently, and that decides this. A\nhosted page is always viewed online, so a CDN dependency is free. A file gets\nmoved, attached to mail, and opened on a laptop in a tunnel — and there a\nruntime dependency does not degrade, it collapses. Tailwind from a CDN with no\nnetwork is an unstyled document. React from a CDN with no network is a blank\none.\n\nSo the default is no runtime dependency at all. Write plain CSS; modern CSS has\ncustom properties, grid, `clamp()`, and container queries, and a page that needs\na utility framework to be laid out usually needs a clearer layout instead.\n\nThere is no build step here and nothing bundles this file, so a framework that\nexpects one — Vite, a JSX pipeline, anything importing bare module specifiers —\nis not an option regardless.\n\nWhen a library genuinely earns its place, and that is mostly charting or syntax\nhighlighting rather than layout:\n\n- Inline it into the file if its licence permits, and the page stays whole.\n- Otherwise pin an exact version, give the feature a readable fallback for when\n  the script does not load, and tell the user the page needs network.\n\nWebfonts are the one dependency that degrades gracefully, because a real\nfallback stack keeps the page readable when the link fails. Use one, and always\ndeclare the stack.\n\n## Build cleanly\n\n- Watch selector specificity. Type-level and element-level selectors fighting\n  over the same padding is how spacing silently comes undone.\n- Close every non-void element and double-quote every attribute.\n- Give keyboard focus a visible state.\n- Respect `prefers-reduced-motion`.\n- For generative or decorative graphics, reach for Canvas or WebGL rather than\n  hand-authoring long SVG path data.\n- Before finishing, scan the stylesheet for any color declared only inside a\n  media query.\n\n## Delivering it\n\nWrite one self-contained `.html` file. Inline the page's own CSS and JS; embed\nsmall assets as data URIs so the file survives being moved or sent to someone.\n\nPut it where the user would expect it — alongside the data it visualizes, or in\nthe directory they named. Then give them the path as a markdown link with a\n`file:\u002F\u002F` URL:\n\n```\n[tokens.html](file:\u002F\u002F\u002Fabs\u002Fpath\u002Fto\u002Ftokens.html)\n```\n\nhoocode's markdown renderer turns that into an OSC 8 hyperlink wherever the\nterminal supports one, so it is clickable in kitty, iTerm2, WezTerm and others,\nand still readable as plain text everywhere else. Offer to open it rather than\nopening it unasked.\n\n",{"name":5,"description":7,"allowed-tools":24},"Read, Write, Edit, CodeSearch","main","28f94f989eab0cc33a1ae4006a3fd503a681d28c","crates\u002Fhoocode-code-resources\u002Ftemplates\u002Fskills\u002Fartifact-design",1,"https:\u002F\u002Fgithub.com\u002Fkolisachint\u002Fhoocode","https:\u002F\u002Fgithub.com\u002Fkolisachint","https:\u002F\u002Fkolisachint.github.io","Solution Architect — Cloud Data & AI Platforms","2026-11-12 20:51:36",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add kolisachint\u002Fhoocode --skill artifact-design",{"tool":40,"command":41},"bunx","bunx skills add kolisachint\u002Fhoocode --skill artifact-design",{"tool":43,"command":44},"pnpm","pnpm dlx skills add kolisachint\u002Fhoocode --skill artifact-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkolisachint\u002Fhoocode\u002Fblob\u002Fmain\u002Fcrates\u002Fhoocode-code-resources\u002Ftemplates\u002Fskills\u002Fartifact-design\u002FSKILL.md",true,[],[49,56,63,70,77,83],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M79CPHH1YPBZ7TH7C3CSMQRW","valid-skill","A valid skill for testing purposes.","https:\u002F\u002Fgithub.com\u002Fkolisachint\u002Fhoocode\u002Fblob\u002Fmain\u002Fcrates\u002Fhoocode-code-resources\u002Ftests\u002Ffixtures\u002Fskills\u002Fvalid-skill\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M79CPEG9CACMK0ESN1KES5ZM","unknown-field","A skill with an unknown frontmatter field.","https:\u002F\u002Fgithub.com\u002Fkolisachint\u002Fhoocode\u002Fblob\u002Fmain\u002Fcrates\u002Fhoocode-code-resources\u002Ftests\u002Ffixtures\u002Fskills\u002Funknown-field\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79CPD7B4NTYCMBC1SV35DC0","nested-child","Nested skill should be ignored.","https:\u002F\u002Fgithub.com\u002Fkolisachint\u002Fhoocode\u002Fblob\u002Fmain\u002Fcrates\u002Fhoocode-code-resources\u002Ftests\u002Ffixtures\u002Fskills\u002Froot-skill-preferred\u002Fnested-child\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79CPBSM4WX62GA8NYY2PFE4","root-skill-preferred","Root skill should win.","https:\u002F\u002Fgithub.com\u002Fkolisachint\u002Fhoocode\u002Fblob\u002Fmain\u002Fcrates\u002Fhoocode-code-resources\u002Ftests\u002Ffixtures\u002Fskills\u002Froot-skill-preferred\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"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":80,"categories":81,"keywords":82,"publishedAt":19},"01M79CPAC30QC7W775PCR4F6GZ","no-frontmatter","https:\u002F\u002Fgithub.com\u002Fkolisachint\u002Fhoocode\u002Fblob\u002Fmain\u002Fcrates\u002Fhoocode-code-resources\u002Ftests\u002Ffixtures\u002Fskills\u002Fno-frontmatter\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},"01M79CP8XZJB5BAVQVAG9QNDH5","child-skill","A nested skill in a subdirectory.","https:\u002F\u002Fgithub.com\u002Fkolisachint\u002Fhoocode\u002Fblob\u002Fmain\u002Fcrates\u002Fhoocode-code-resources\u002Ftests\u002Ffixtures\u002Fskills\u002Fnested\u002Fchild-skill\u002FSKILL.md",[],[]]