[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74FAXPHS0QT1S067QDKYDBX":3,"skill-same:01M74FAXPHS0QT1S067QDKYDBX":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},"01M74FAXPHS0QT1S067QDKYDBX","write-milestone-brief",null,"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.","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\u002Fwrite-milestone-brief\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: write-milestone-brief\ndescription: 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.\n---\n\n\u003Cobjective>\nTake everything established in the current conversation (plus repo reality) and produce a milestone brief that a future agent can execute from with zero additional context. The output is a populated `M###-CONTEXT.md`, matching the template at `src\u002Fresources\u002Fextensions\u002Fgsd\u002Ftemplates\u002Fcontext.md`. Optionally, with explicit confirmation, also a GitHub issue.\n\u003C\u002Fobjective>\n\n\u003Ccontext>\nThis skill runs at the end of a discussion phase, after enough grilling\u002Fdesign has happened that the plan has stabilized. It does NOT interview — use the `grill-me` skill for that. This skill collapses what is already on the page into a durable artifact.\n\nTypical invocation points:\n\n- User says \"capture this\" or \"write it up\" after a planning discussion\n- End of a `discuss` phase before moving to `plan`\n- User wants to hand the work off to another agent or a human teammate\n\u003C\u002Fcontext>\n\n\u003Ccore_principle>\n**SYNTHESIZE, DO NOT RE-INTERVIEW.** Use what is already in this conversation. If a decision is genuinely missing, note it in `Open Questions` — do not relitigate.\n\n**REAL OUTCOMES, NOT TASKS.** `M###-CONTEXT.md` describes what the user can do when the milestone ships, what scenarios must pass for \"done,\" and what architectural decisions were made. It does NOT list tasks or implementation steps — those belong in `M###-ROADMAP.md` and `S##-PLAN.md`.\n\n**NO FILE PATHS OR LINE NUMBERS IN THE BRIEF.** Those go stale. Describe modules, interfaces, and behaviors. The roadmap and plans can cite code locations; the brief should outlive refactors.\n\u003C\u002Fcore_principle>\n\n\u003Cprocess>\n\n## Step 1: Locate the target\n\nFind the active milestone:\n\n1. Call `gsd_project_snapshot` — it names the active milestone.\n2. If no milestone is active, ask the user whether this is a new milestone (create directory + files) or appending to an existing one.\n3. For a new milestone, use `gsd_milestone_new` or the `\u002Fgsd new-milestone` flow — do not create directories by hand.\n\n## Step 2: Read the template\n\nRead `src\u002Fresources\u002Fextensions\u002Fgsd\u002Ftemplates\u002Fcontext.md` (the full path is shown in the `templatesDir` system-prompt field). Match its structure exactly — parsers and downstream prompts depend on the headings.\n\n## Step 3: Sketch the modules\n\nBefore filling the template, sketch the major modules the milestone will build or modify. Actively look for opportunities to extract **deep modules** — ones that encapsulate a lot of functionality in a simple, testable interface that rarely changes. A deep module is more testable, more AI-navigable, and survives refactors.\n\nIf the modules are non-obvious, offer the user a brief check-in: \"The milestone touches modules A, B, and C. A can be extracted as a deep module that hides X. Does that match your thinking?\" One round. Then proceed.\n\n## Step 4: Fill the template\n\nPopulate `M###-CONTEXT.md` using the template. Key sections:\n\n- **Project Description** — one paragraph, plain English, what this milestone is.\n- **Why This Milestone** — the problem it solves and why now, from the user's perspective.\n- **User-Visible Outcome** — literal user actions in the real environment. \"User can complete the import flow end-to-end\" not \"Adds import API.\"\n- **Completion Class** — contract \u002F integration \u002F operational. Be honest about what level of proof is required.\n- **Final Integrated Acceptance** — the real end-to-end scenarios that must pass. Name things that cannot be simulated.\n- **Architectural Decisions** — one `### Decision Title` block per decision, with rationale and alternatives considered. If there were no architectural decisions, write \"None — straightforward execution\" and skip the subsections.\n- **Error Handling Strategy** — approach for failures, edge cases, and error propagation. Include retry policies, fallback behaviors, and user-facing error messages where relevant.\n- **Risks and Unknowns** — only real ones. Do not invent risks.\n- **Existing Codebase \u002F Prior Art** — module names, not line numbers. Brief description of how each relates.\n- **Relevant Requirements** — requirement IDs this milestone advances and how.\n- **Scope** — In Scope \u002F Out of Scope \u002F Non-Goals. Be specific about tempting adjacent work that is out.\n- **Technical Constraints** — binding constraints (runtime, platform, dependencies, performance budgets).\n- **Integration Points** — external systems\u002Fservices this milestone touches and how.\n- **Testing Requirements** — test types (unit, integration, e2e), coverage expectations, and specific scenarios that must pass.\n- **Acceptance Criteria** — per-slice, testable criteria gathered during discussion.\n- **Open Questions** — anything material that is genuinely unresolved. Note current thinking so future agents have a starting point.\n\n> The template headings above are mandatory — do not omit, rename, or reorder them. The exact required order matches `src\u002Fresources\u002Fextensions\u002Fgsd\u002Ftemplates\u002Fcontext.md`: Project Description → Why This Milestone → User-Visible Outcome → Completion Class → Final Integrated Acceptance → Architectural Decisions → Error Handling Strategy → Risks and Unknowns → Existing Codebase \u002F Prior Art → Relevant Requirements → Scope → Technical Constraints → Integration Points → Testing Requirements → Acceptance Criteria → Open Questions.\n\n## Step 5: Write it\n\nCall `gsd_summary_save` with the `milestone_id`, `artifact_type: \"CONTEXT\"` and the full brief as `content`. The tool stores the brief in the database and renders `.gsd\u002Fmilestones\u002F\u003CMID>\u002F\u003CMID>-CONTEXT.md`; do not write the file. Do not ask for approval of the contents before saving — the user will see the rendered file and can ask for changes.\n\nThen call `gsd_decision_save` for any genuinely hard-to-reverse architectural decision, with a one-line rationale.\n\n## Step 6: Offer next steps\n\nAfter writing, offer the user (do not auto-execute):\n\n1. **Proceed to planning** — run `\u002Fgsd dispatch plan` to generate `M###-ROADMAP.md` from this brief.\n2. **File as GitHub issue** — use the active GitHub issue-write tool if one is available, using its exact active tool name. Requires explicit \"yes\" per the outward-action rule. Use the PRD template below for the body.\n3. **Iterate on the brief** — if something feels wrong, run `grill-me` to stress-test before moving on.\n\n### GitHub issue body template (only if user chooses option 2)\n\n```markdown\n## Problem Statement\n\u003Cuser-perspective problem — one paragraph>\n\n## Solution\n\u003Cuser-perspective solution — one paragraph>\n\n## User Stories\n1. As a \u003Cactor>, I want \u003Cfeature>, so that \u003Cbenefit>.\n2. ...\n\u003Ccover all aspects; be exhaustive>\n\n## Architectural Decisions\n\u003Clist of decisions with rationale — copy from M###-CONTEXT.md>\n\n## Testing Strategy\n\u003Cwhat a good test looks like here: external behavior only, which modules get tested, prior art>\n\n## Out of Scope\n\u003Cthings explicitly not covered>\n\n## Further Notes\n\u003Cany extra context>\n\n---\nSee `.gsd\u002Fmilestones\u002F\u003CMID>\u002F\u003CMID>-CONTEXT.md` for the full brief.\n```\n\n\u003C\u002Fprocess>\n\n\u003Canti_patterns>\n\n- **Re-interviewing the user.** Use context, not fresh questions. If something is missing, put it in Open Questions.\n- **Listing implementation tasks.** The brief describes outcomes and decisions — the roadmap and plans describe tasks.\n- **Citing specific line numbers.** They rot. Cite modules or interfaces.\n- **Inventing risks or decisions.** If the discussion didn't surface a real architectural choice, the Architectural Decisions section is short — that's fine.\n- **Auto-filing the GitHub issue.** Any outward-facing action needs explicit confirmation.\n\n\u003C\u002Fanti_patterns>\n\n\u003Csuccess_criteria>\n\n- [ ] `M###-CONTEXT.md` exists and follows the template structure.\n- [ ] User-Visible Outcome section names literal user actions, not internal tasks.\n- [ ] Completion Class is honest — no \"just unit tests\" when the milestone demands live integration.\n- [ ] Every architectural decision has a rationale and named alternatives.\n- [ ] Open Questions captures genuinely unresolved items — not decisions the user already made.\n- [ ] Any hard-to-reverse decision is saved with `gsd_decision_save`.\n\n\u003C\u002Fsuccess_criteria>\n","\u003Cobjective>\nTake everything established in the current conversation (plus repo reality) and produce a milestone brief that a future agent can execute from with zero additional context. The output is a populated `M###-CONTEXT.md`, matching the template at `src\u002Fresources\u002Fextensions\u002Fgsd\u002Ftemplates\u002Fcontext.md`. Optionally, with explicit confirmation, also a GitHub issue.\n\u003C\u002Fobjective>\n\n\u003Ccontext>\nThis skill runs at the end of a discussion phase, after enough grilling\u002Fdesign has happened that the plan has stabilized. It does NOT interview — use the `grill-me` skill for that. This skill collapses what is already on the page into a durable artifact.\n\nTypical invocation points:\n\n- User says \"capture this\" or \"write it up\" after a planning discussion\n- End of a `discuss` phase before moving to `plan`\n- User wants to hand the work off to another agent or a human teammate\n\u003C\u002Fcontext>\n\n\u003Ccore_principle>\n**SYNTHESIZE, DO NOT RE-INTERVIEW.** Use what is already in this conversation. If a decision is genuinely missing, note it in `Open Questions` — do not relitigate.\n\n**REAL OUTCOMES, NOT TASKS.** `M###-CONTEXT.md` describes what the user can do when the milestone ships, what scenarios must pass for \"done,\" and what architectural decisions were made. It does NOT list tasks or implementation steps — those belong in `M###-ROADMAP.md` and `S##-PLAN.md`.\n\n**NO FILE PATHS OR LINE NUMBERS IN THE BRIEF.** Those go stale. Describe modules, interfaces, and behaviors. The roadmap and plans can cite code locations; the brief should outlive refactors.\n\u003C\u002Fcore_principle>\n\n\u003Cprocess>\n\n## Step 1: Locate the target\n\nFind the active milestone:\n\n1. Call `gsd_project_snapshot` — it names the active milestone.\n2. If no milestone is active, ask the user whether this is a new milestone (create directory + files) or appending to an existing one.\n3. For a new milestone, use `gsd_milestone_new` or the `\u002Fgsd new-milestone` flow — do not create directories by hand.\n\n## Step 2: Read the template\n\nRead `src\u002Fresources\u002Fextensions\u002Fgsd\u002Ftemplates\u002Fcontext.md` (the full path is shown in the `templatesDir` system-prompt field). Match its structure exactly — parsers and downstream prompts depend on the headings.\n\n## Step 3: Sketch the modules\n\nBefore filling the template, sketch the major modules the milestone will build or modify. Actively look for opportunities to extract **deep modules** — ones that encapsulate a lot of functionality in a simple, testable interface that rarely changes. A deep module is more testable, more AI-navigable, and survives refactors.\n\nIf the modules are non-obvious, offer the user a brief check-in: \"The milestone touches modules A, B, and C. A can be extracted as a deep module that hides X. Does that match your thinking?\" One round. Then proceed.\n\n## Step 4: Fill the template\n\nPopulate `M###-CONTEXT.md` using the template. Key sections:\n\n- **Project Description** — one paragraph, plain English, what this milestone is.\n- **Why This Milestone** — the problem it solves and why now, from the user's perspective.\n- **User-Visible Outcome** — literal user actions in the real environment. \"User can complete the import flow end-to-end\" not \"Adds import API.\"\n- **Completion Class** — contract \u002F integration \u002F operational. Be honest about what level of proof is required.\n- **Final Integrated Acceptance** — the real end-to-end scenarios that must pass. Name things that cannot be simulated.\n- **Architectural Decisions** — one `### Decision Title` block per decision, with rationale and alternatives considered. If there were no architectural decisions, write \"None — straightforward execution\" and skip the subsections.\n- **Error Handling Strategy** — approach for failures, edge cases, and error propagation. Include retry policies, fallback behaviors, and user-facing error messages where relevant.\n- **Risks and Unknowns** — only real ones. Do not invent risks.\n- **Existing Codebase \u002F Prior Art** — module names, not line numbers. Brief description of how each relates.\n- **Relevant Requirements** — requirement IDs this milestone advances and how.\n- **Scope** — In Scope \u002F Out of Scope \u002F Non-Goals. Be specific about tempting adjacent work that is out.\n- **Technical Constraints** — binding constraints (runtime, platform, dependencies, performance budgets).\n- **Integration Points** — external systems\u002Fservices this milestone touches and how.\n- **Testing Requirements** — test types (unit, integration, e2e), coverage expectations, and specific scenarios that must pass.\n- **Acceptance Criteria** — per-slice, testable criteria gathered during discussion.\n- **Open Questions** — anything material that is genuinely unresolved. Note current thinking so future agents have a starting point.\n\n> The template headings above are mandatory — do not omit, rename, or reorder them. The exact required order matches `src\u002Fresources\u002Fextensions\u002Fgsd\u002Ftemplates\u002Fcontext.md`: Project Description → Why This Milestone → User-Visible Outcome → Completion Class → Final Integrated Acceptance → Architectural Decisions → Error Handling Strategy → Risks and Unknowns → Existing Codebase \u002F Prior Art → Relevant Requirements → Scope → Technical Constraints → Integration Points → Testing Requirements → Acceptance Criteria → Open Questions.\n\n## Step 5: Write it\n\nCall `gsd_summary_save` with the `milestone_id`, `artifact_type: \"CONTEXT\"` and the full brief as `content`. The tool stores the brief in the database and renders `.gsd\u002Fmilestones\u002F\u003CMID>\u002F\u003CMID>-CONTEXT.md`; do not write the file. Do not ask for approval of the contents before saving — the user will see the rendered file and can ask for changes.\n\nThen call `gsd_decision_save` for any genuinely hard-to-reverse architectural decision, with a one-line rationale.\n\n## Step 6: Offer next steps\n\nAfter writing, offer the user (do not auto-execute):\n\n1. **Proceed to planning** — run `\u002Fgsd dispatch plan` to generate `M###-ROADMAP.md` from this brief.\n2. **File as GitHub issue** — use the active GitHub issue-write tool if one is available, using its exact active tool name. Requires explicit \"yes\" per the outward-action rule. Use the PRD template below for the body.\n3. **Iterate on the brief** — if something feels wrong, run `grill-me` to stress-test before moving on.\n\n### GitHub issue body template (only if user chooses option 2)\n\n```markdown\n## Problem Statement\n\u003Cuser-perspective problem — one paragraph>\n\n## Solution\n\u003Cuser-perspective solution — one paragraph>\n\n## User Stories\n1. As a \u003Cactor>, I want \u003Cfeature>, so that \u003Cbenefit>.\n2. ...\n\u003Ccover all aspects; be exhaustive>\n\n## Architectural Decisions\n\u003Clist of decisions with rationale — copy from M###-CONTEXT.md>\n\n## Testing Strategy\n\u003Cwhat a good test looks like here: external behavior only, which modules get tested, prior art>\n\n## Out of Scope\n\u003Cthings explicitly not covered>\n\n## Further Notes\n\u003Cany extra context>\n\n---\nSee `.gsd\u002Fmilestones\u002F\u003CMID>\u002F\u003CMID>-CONTEXT.md` for the full brief.\n```\n\n\u003C\u002Fprocess>\n\n\u003Canti_patterns>\n\n- **Re-interviewing the user.** Use context, not fresh questions. If something is missing, put it in Open Questions.\n- **Listing implementation tasks.** The brief describes outcomes and decisions — the roadmap and plans describe tasks.\n- **Citing specific line numbers.** They rot. Cite modules or interfaces.\n- **Inventing risks or decisions.** If the discussion didn't surface a real architectural choice, the Architectural Decisions section is short — that's fine.\n- **Auto-filing the GitHub issue.** Any outward-facing action needs explicit confirmation.\n\n\u003C\u002Fanti_patterns>\n\n\u003Csuccess_criteria>\n\n- [ ] `M###-CONTEXT.md` exists and follows the template structure.\n- [ ] User-Visible Outcome section names literal user actions, not internal tasks.\n- [ ] Completion Class is honest — no \"just unit tests\" when the milestone demands live integration.\n- [ ] Every architectural decision has a rationale and named alternatives.\n- [ ] Open Questions captures genuinely unresolved items — not decisions the user already made.\n- [ ] Any hard-to-reverse decision is saved with `gsd_decision_save`.\n\n\u003C\u002Fsuccess_criteria>\n",{"name":5,"description":7},"main","c0bc9c4e7e0a8581aeac3af397031dc3a63d012e","src\u002Fresources\u002Fskills\u002Fwrite-milestone-brief",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 write-milestone-brief",{"tool":40,"command":41},"bunx","bunx skills add open-gsd\u002Fgsd-pi --skill write-milestone-brief",{"tool":43,"command":44},"pnpm","pnpm dlx skills add open-gsd\u002Fgsd-pi --skill write-milestone-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fwrite-milestone-brief\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},"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":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},"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":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},"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":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},"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":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},"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",[],[],{"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},"01M74FAB75D1RJDGWAETQ9JB4G","test","Generate or run tests. Auto-detects test framework, generates comprehensive tests for source files, or runs existing test suites with failure analysis.","https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-pi\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Ftest\u002FSKILL.md",[],[]]