[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74FA4WNQ3ZSQNEJTX5QRYYQ":3,"skill-same:01M74FA4WNQ3ZSQNEJTX5QRYYQ":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M74FA4WNQ3ZSQNEJTX5QRYYQ","spike-wrap-up",null,"Package findings from a completed spike into a durable project-local skill that auto-loads on future similar work. Reads the latest `.gsd\u002Fworkflows\u002Fspikes\u002F` dir, interviews the user on what's reusable, then writes `.agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md`. Use when asked to \"wrap up the spike\", \"package this as a skill\", \"make this reusable\", \"turn findings into a skill\", or at the synthesize phase of `\u002Fgsd start spike`.","open-gsd\u002Fgsd-pi","open-gsd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286935422?v=4","01M74F5F0MKW0B81YZHRVJMMWR","Open GSD","01M74F5F1782D325EYEM5GNXNC",1369,"MIT","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fspike-wrap-up\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: spike-wrap-up\ndescription: Package findings from a completed spike into a durable project-local skill that auto-loads on future similar work. Reads the latest `.gsd\u002Fworkflows\u002Fspikes\u002F` dir, interviews the user on what's reusable, then writes `.agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md`. Use when asked to \"wrap up the spike\", \"package this as a skill\", \"make this reusable\", \"turn findings into a skill\", or at the synthesize phase of `\u002Fgsd start spike`.\n---\n\n\u003Cobjective>\nConvert the output of a research spike (`SCOPE.md`, `research\u002F*.md`, `RECOMMENDATION.md`) into a project-local skill under `.agents\u002Fskills\u002F` so that the next time a similar task comes up, the agent loads the skill automatically. This is how throwaway spikes become durable capital.\n\u003C\u002Fobjective>\n\n\u003Ccontext>\nGSD's spike workflow (`src\u002Fresources\u002Fextensions\u002Fgsd\u002Fworkflow-templates\u002Fspike.md`) produces documents in `.gsd\u002Fworkflows\u002Fspikes\u002F\u003Cslug>\u002F`. Those documents are useful once and then forgotten unless something packages them for reuse.\n\nGSD already watches `.agents\u002Fskills\u002F` (and `.claude\u002Fskills\u002F` as a legacy compat path) at both user and project levels — see `src\u002Fresources\u002Fextensions\u002Fgsd\u002Fskill-discovery.ts`. Any skill written there is picked up on the next session without further wiring. This skill is the bridge from \"spike done\" to \"skill available.\"\n\nInvocation points:\n\n- End of Phase 3 (synthesize) in `\u002Fgsd start spike` — prompt suggests running this skill\n- User has a spike directory and wants to harvest it\n- Pre-existing `RECOMMENDATION.md` that deserves a permanent home\n\u003C\u002Fcontext>\n\n\u003Ccore_principle>\n**NOT EVERY SPIKE DESERVES A SKILL.** If the recommendation was \"don't do X,\" there may be no reusable guidance. Ask the user first; exit without writing if the answer is no.\n\n**PROJECT-LOCAL, NOT USER-GLOBAL.** Write to `.agents\u002Fskills\u002F` in the project root, not `~\u002F.agents\u002Fskills\u002F`. The skill encodes project-specific choices that should not leak into unrelated projects.\n\n**DESCRIPTION IS THE DISCOVERABILITY SIGNAL.** The `description` field in frontmatter is the primary signal the agent uses to judge relevance and decide whether to load the skill — it is a heuristic, not a deterministic trigger. Write it as keywords the future agent will plausibly encounter, not a summary.\n\u003C\u002Fcore_principle>\n\n\u003Cprocess>\n\n## Step 1: Find the spike\n\n1. List directories under `.gsd\u002Fworkflows\u002Fspikes\u002F` — sort by mtime, newest first.\n2. If multiple exist, ask the user which to wrap up. Default: the most recent.\n3. If none exist, tell the user and stop. This skill requires a completed spike.\n\nRead the core files:\n\n- `\u003Cspike>\u002FSCOPE.md` — the question that was asked\n- `\u003Cspike>\u002Fresearch\u002F*.md` — the angles investigated\n- `\u003Cspike>\u002FRECOMMENDATION.md` — the conclusion\n\n## Step 2: Decide if it deserves a skill\n\nAsk the user — one round:\n\n1. **Is the conclusion reusable on future work, or was it specific to one decision?**\n   Recommendation: packaging is worth it if the findings include repeatable guidance (how to evaluate X, a pattern to follow, a library's gotchas). If the spike ended in \"we chose library Y, end of story,\" it probably belongs in `.gsd\u002FDECISIONS.md` instead.\n\n2. **What is the trigger?** When should a future agent load this skill? Give concrete keywords — \"adding a new webhook handler\", \"writing a SQL migration\", etc.\n\nIf the user says it's not worth packaging, offer instead to save a summary with `gsd_decision_save` and stop.\n\n## Step 3: Design the skill\n\nBefore writing, sketch in the conversation:\n\n- **Name:** kebab-case, short, unambiguous. Prefix with the project's domain when helpful (`auth-webhook-setup`, not `webhook`).\n- **Description (frontmatter):** one sentence, 120–1024 chars, keyword-rich. Must state when the agent should load it. Rewrite at least twice before settling.\n- **Objective:** one paragraph — what the skill does and what artifact it produces.\n- **Process:** numbered steps. Reference the spike's findings as the source, but the skill itself should be executable without reading the spike.\n- **Anti-patterns:** gotchas the spike surfaced — things that looked right but didn't work.\n- **Success criteria:** checklist the skill's user can confirm against.\n\nShow this sketch to the user. One round of feedback. Iterate.\n\n## Step 4: Write the skill\n\nWrite to `.agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (create the directory). Match the frontmatter + XML-tag structure used by other bundled skills — see `src\u002Fresources\u002Fskills\u002Freview\u002FSKILL.md` for the canonical shape.\n\nMinimum structure:\n\n```markdown\n---\nname: \u003Cskill-name>\ndescription: \u003Cone sentence with trigger keywords>\n---\n\n\u003Cobjective>\n\u003Cone paragraph — what this skill does>\n\u003C\u002Fobjective>\n\n\u003Ccontext>\n\u003Cwhen to invoke, what produced it (cite the spike), assumptions>\n\u003C\u002Fcontext>\n\n\u003Cprocess>\n## Step 1: \u003Caction>\n\u003Cinstructions>\n\n## Step 2: \u003Caction>\n\u003Cinstructions>\n\u003C\u002Fprocess>\n\n\u003Canti_patterns>\n- \u003Cgotcha from the spike>\n- \u003Canother gotcha>\n\u003C\u002Fanti_patterns>\n\n\u003Csuccess_criteria>\n- [ ] \u003Cobservable confirmation>\n- [ ] \u003Cobservable confirmation>\n\u003C\u002Fsuccess_criteria>\n```\n\nIf the spike produced a reusable template (a config file, a starter script), copy it into `.agents\u002Fskills\u002F\u003Cname>\u002Ftemplates\u002F` or `.agents\u002Fskills\u002F\u003Cname>\u002Freferences\u002F` and reference it from the skill body.\n\n## Step 5: Archive the spike, link from the skill\n\n1. In the new SKILL.md, reference the originating spike: \"Derived from `.gsd\u002Fworkflows\u002Fspikes\u002F\u003Cslug>\u002FRECOMMENDATION.md` (dated YYYY-MM-DD).\"\n2. Do NOT delete the spike directory — spikes are research artifacts and retain value for forensics.\n3. Call `gsd_decision_save` to record that the \"\u003Cslug>\" spike findings were packaged as skill \u003Cname>.\n\n## Step 6: Confirm pickup\n\nTell the user the skill will be surfaced on the next session via `skill-discovery.ts`. If they want to use it immediately, they can `Read .agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md` now.\n\n\u003C\u002Fprocess>\n\n\u003Canti_patterns>\n\n- **Writing to `~\u002F.claude\u002Fskills\u002F` or `.claude\u002Fskills\u002F`.** These are legacy Claude Code compatibility paths. Write project skills to `.agents\u002Fskills\u002F` in the project root instead.\n- **Verbose frontmatter description.** The description is an index entry, not a tutorial. Keywords over prose.\n- **Packaging every spike.** If the outcome was \"we decided X once,\" save it with `gsd_decision_save` and move on.\n- **Copy-pasting the spike verbatim into the skill.** The spike is research; the skill is executable guidance. Re-author.\n- **Deleting the source spike.** Research artifacts should persist.\n\n\u003C\u002Fanti_patterns>\n\n\u003Csuccess_criteria>\n\n- [ ] A new `.agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md` exists with well-formed frontmatter.\n- [ ] The `description` field uses keywords that will plausibly match future agent work.\n- [ ] The skill body is executable on its own without re-reading the originating spike.\n- [ ] The originating spike is referenced from the skill.\n- [ ] The packaging is recorded with `gsd_decision_save`.\n- [ ] The spike directory itself is untouched.\n\n\u003C\u002Fsuccess_criteria>\n","\u003Cobjective>\nConvert the output of a research spike (`SCOPE.md`, `research\u002F*.md`, `RECOMMENDATION.md`) into a project-local skill under `.agents\u002Fskills\u002F` so that the next time a similar task comes up, the agent loads the skill automatically. This is how throwaway spikes become durable capital.\n\u003C\u002Fobjective>\n\n\u003Ccontext>\nGSD's spike workflow (`src\u002Fresources\u002Fextensions\u002Fgsd\u002Fworkflow-templates\u002Fspike.md`) produces documents in `.gsd\u002Fworkflows\u002Fspikes\u002F\u003Cslug>\u002F`. Those documents are useful once and then forgotten unless something packages them for reuse.\n\nGSD already watches `.agents\u002Fskills\u002F` (and `.claude\u002Fskills\u002F` as a legacy compat path) at both user and project levels — see `src\u002Fresources\u002Fextensions\u002Fgsd\u002Fskill-discovery.ts`. Any skill written there is picked up on the next session without further wiring. This skill is the bridge from \"spike done\" to \"skill available.\"\n\nInvocation points:\n\n- End of Phase 3 (synthesize) in `\u002Fgsd start spike` — prompt suggests running this skill\n- User has a spike directory and wants to harvest it\n- Pre-existing `RECOMMENDATION.md` that deserves a permanent home\n\u003C\u002Fcontext>\n\n\u003Ccore_principle>\n**NOT EVERY SPIKE DESERVES A SKILL.** If the recommendation was \"don't do X,\" there may be no reusable guidance. Ask the user first; exit without writing if the answer is no.\n\n**PROJECT-LOCAL, NOT USER-GLOBAL.** Write to `.agents\u002Fskills\u002F` in the project root, not `~\u002F.agents\u002Fskills\u002F`. The skill encodes project-specific choices that should not leak into unrelated projects.\n\n**DESCRIPTION IS THE DISCOVERABILITY SIGNAL.** The `description` field in frontmatter is the primary signal the agent uses to judge relevance and decide whether to load the skill — it is a heuristic, not a deterministic trigger. Write it as keywords the future agent will plausibly encounter, not a summary.\n\u003C\u002Fcore_principle>\n\n\u003Cprocess>\n\n## Step 1: Find the spike\n\n1. List directories under `.gsd\u002Fworkflows\u002Fspikes\u002F` — sort by mtime, newest first.\n2. If multiple exist, ask the user which to wrap up. Default: the most recent.\n3. If none exist, tell the user and stop. This skill requires a completed spike.\n\nRead the core files:\n\n- `\u003Cspike>\u002FSCOPE.md` — the question that was asked\n- `\u003Cspike>\u002Fresearch\u002F*.md` — the angles investigated\n- `\u003Cspike>\u002FRECOMMENDATION.md` — the conclusion\n\n## Step 2: Decide if it deserves a skill\n\nAsk the user — one round:\n\n1. **Is the conclusion reusable on future work, or was it specific to one decision?**\n   Recommendation: packaging is worth it if the findings include repeatable guidance (how to evaluate X, a pattern to follow, a library's gotchas). If the spike ended in \"we chose library Y, end of story,\" it probably belongs in `.gsd\u002FDECISIONS.md` instead.\n\n2. **What is the trigger?** When should a future agent load this skill? Give concrete keywords — \"adding a new webhook handler\", \"writing a SQL migration\", etc.\n\nIf the user says it's not worth packaging, offer instead to save a summary with `gsd_decision_save` and stop.\n\n## Step 3: Design the skill\n\nBefore writing, sketch in the conversation:\n\n- **Name:** kebab-case, short, unambiguous. Prefix with the project's domain when helpful (`auth-webhook-setup`, not `webhook`).\n- **Description (frontmatter):** one sentence, 120–1024 chars, keyword-rich. Must state when the agent should load it. Rewrite at least twice before settling.\n- **Objective:** one paragraph — what the skill does and what artifact it produces.\n- **Process:** numbered steps. Reference the spike's findings as the source, but the skill itself should be executable without reading the spike.\n- **Anti-patterns:** gotchas the spike surfaced — things that looked right but didn't work.\n- **Success criteria:** checklist the skill's user can confirm against.\n\nShow this sketch to the user. One round of feedback. Iterate.\n\n## Step 4: Write the skill\n\nWrite to `.agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (create the directory). Match the frontmatter + XML-tag structure used by other bundled skills — see `src\u002Fresources\u002Fskills\u002Freview\u002FSKILL.md` for the canonical shape.\n\nMinimum structure:\n\n```markdown\n---\nname: \u003Cskill-name>\ndescription: \u003Cone sentence with trigger keywords>\n---\n\n\u003Cobjective>\n\u003Cone paragraph — what this skill does>\n\u003C\u002Fobjective>\n\n\u003Ccontext>\n\u003Cwhen to invoke, what produced it (cite the spike), assumptions>\n\u003C\u002Fcontext>\n\n\u003Cprocess>\n## Step 1: \u003Caction>\n\u003Cinstructions>\n\n## Step 2: \u003Caction>\n\u003Cinstructions>\n\u003C\u002Fprocess>\n\n\u003Canti_patterns>\n- \u003Cgotcha from the spike>\n- \u003Canother gotcha>\n\u003C\u002Fanti_patterns>\n\n\u003Csuccess_criteria>\n- [ ] \u003Cobservable confirmation>\n- [ ] \u003Cobservable confirmation>\n\u003C\u002Fsuccess_criteria>\n```\n\nIf the spike produced a reusable template (a config file, a starter script), copy it into `.agents\u002Fskills\u002F\u003Cname>\u002Ftemplates\u002F` or `.agents\u002Fskills\u002F\u003Cname>\u002Freferences\u002F` and reference it from the skill body.\n\n## Step 5: Archive the spike, link from the skill\n\n1. In the new SKILL.md, reference the originating spike: \"Derived from `.gsd\u002Fworkflows\u002Fspikes\u002F\u003Cslug>\u002FRECOMMENDATION.md` (dated YYYY-MM-DD).\"\n2. Do NOT delete the spike directory — spikes are research artifacts and retain value for forensics.\n3. Call `gsd_decision_save` to record that the \"\u003Cslug>\" spike findings were packaged as skill \u003Cname>.\n\n## Step 6: Confirm pickup\n\nTell the user the skill will be surfaced on the next session via `skill-discovery.ts`. If they want to use it immediately, they can `Read .agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md` now.\n\n\u003C\u002Fprocess>\n\n\u003Canti_patterns>\n\n- **Writing to `~\u002F.claude\u002Fskills\u002F` or `.claude\u002Fskills\u002F`.** These are legacy Claude Code compatibility paths. Write project skills to `.agents\u002Fskills\u002F` in the project root instead.\n- **Verbose frontmatter description.** The description is an index entry, not a tutorial. Keywords over prose.\n- **Packaging every spike.** If the outcome was \"we decided X once,\" save it with `gsd_decision_save` and move on.\n- **Copy-pasting the spike verbatim into the skill.** The spike is research; the skill is executable guidance. Re-author.\n- **Deleting the source spike.** Research artifacts should persist.\n\n\u003C\u002Fanti_patterns>\n\n\u003Csuccess_criteria>\n\n- [ ] A new `.agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md` exists with well-formed frontmatter.\n- [ ] The `description` field uses keywords that will plausibly match future agent work.\n- [ ] The skill body is executable on its own without re-reading the originating spike.\n- [ ] The originating spike is referenced from the skill.\n- [ ] The packaging is recorded with `gsd_decision_save`.\n- [ ] The spike directory itself is untouched.\n\n\u003C\u002Fsuccess_criteria>\n",{"name":5,"description":7},"main","c0bc9c4e7e0a8581aeac3af397031dc3a63d012e","src\u002Fresources\u002Fskills\u002Fspike-wrap-up",118,"https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi","https:\u002F\u002Fwww.opengsd.net","https:\u002F\u002Fgithub.com\u002Fopen-gsd","opengsd.net","Most AI coding setups rot as the context window fills. Open GSD keeps the context clean, the work verified, and the git history honest — ship more, worry less.","2026-11-15 00:38:19",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add open-gsd\u002Fgsd-pi --skill spike-wrap-up",{"tool":40,"command":41},"bunx","bunx skills add open-gsd\u002Fgsd-pi --skill spike-wrap-up",{"tool":43,"command":44},"pnpm","pnpm dlx skills add open-gsd\u002Fgsd-pi --skill spike-wrap-up","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fspike-wrap-up\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"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},"01M74FAXPHS0QT1S067QDKYDBX","write-milestone-brief","Synthesize the current conversation into a milestone brief (PRD). Saves it as the milestone CONTEXT (`gsd_summary_save`) by default, or files a GitHub issue only with explicit user confirmation. Use when asked to \"turn this into a PRD\", \"draft a milestone brief\", \"capture this context\", \"write it up\", or when enough has been discussed to commit the plan to paper. Does not interview — it synthesizes what is already known.","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fwrite-milestone-brief\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},"01M74FATJT7WZX5CSSG8RJDCF1","write-docs","Collaborative authoring workflow for proposals, technical specs, decision docs, READMEs, ADRs, and long-form prose that must work for fresh readers. Three stages: gather context, iterate on structure, reader-test for a stranger. Use when asked to \"write the docs\", \"draft a proposal\", \"write a spec\", \"write an RFC\", \"write the README\", or when a doc must be understandable without this session's context.","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fwrite-docs\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},"01M74FAQ8HKNVGCZ5ZBHW03A76","web-quality-audit","Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to \"audit my site\", \"review web quality\", \"run lighthouse audit\", \"check page quality\", or \"optimize my website\".","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fweb-quality-audit\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},"01M74FAMZ7WP4RPAG20F448MVF","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M74FAHYM672GKGGS8KMY9CKC","verify-before-complete","Block completion claims until verification evidence has been produced in the current message. Use before marking a task\u002Fslice\u002Fmilestone complete, before creating a commit or PR, before saying \"it works\" or \"tests pass\", and any time you are about to claim work is done. The rule is: evidence before claims, always — running the verification must happen now, not \"earlier in the session\". Fresh output or no claim.","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fverify-before-complete\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M74FADG78GX090P4YE5ZHR2A","userinterface-wiki","UI\u002FUX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fuserinterface-wiki\u002FSKILL.md",[],[]]