[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CHTP18GSDWPB2KXRR895D9":3,"skill-same:01M6CHTP18GSDWPB2KXRR895D9":102},{"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":30,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":68,"repositoryHtmlUrl":69,"repositoryHomepageUrl":70,"ownerHtmlUrl":71,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":72,"install":73,"resources":86},"01M6CHTP18GSDWPB2KXRR895D9","ux",null,"[ADD v{{VERSION}}] Iterate on UI\u002FUX design before implementation — wireframes, flow validation, and design sign-off","MountainUnicorn\u002Fadd","MountainUnicorn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F199411549?v=4","01M6CHRAWFWD275ANP1S2A0HXC","01M6CHRB0QE1678D913B438SAR",11,"MIT","https:\u002F\u002Fgithub.com\u002FMountainUnicorn\u002Fadd\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fux\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[5,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"Bash","implementation","design-system","version","edit","write","read","grep","Rules","system","design","flow","ui","file","figma","validation","telemetry","spec","2026-11-10 10:12:30",false,"---\ndescription: \"[ADD v{{VERSION}}] Iterate on UI\u002FUX design before implementation — wireframes, flow validation, and design sign-off\"\nargument-hint: \"\u003Cspec-file> [--figma \u003Curl-or-frame-id>]\"\nallowed-tools: [Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion]\nreferences: [\"design-system.md\", \"rules\u002Ftelemetry.md\"]\n---\n\n# ADD UX Command v{{VERSION}}\n\nIterate on UI\u002FUX design for a feature before implementation begins. Produces a signed-off design artifact that gates `\u002Fadd:plan` and `\u002Fadd:tdd-cycle`. Prevents token burn from building the wrong UI.\n\n## Pre-Flight\n\n1. Read `.add\u002Fconfig.json` to understand project context and maturity level\n2. If `spec-file` argument is provided, read it. Otherwise, list specs in `specs\u002F` and ask which feature to design\n3. Verify the spec exists and has a UI component (Q8 answered, or acceptance criteria mention UI states)\n   - If no UI component is detectable, confirm with the human: \"This spec doesn't appear to have a UI — do you still want to run a UX iteration?\"\n4. Check if a UI artifact already exists at `specs\u002Fux\u002F{feature-slug}-ux.md`\n   - If it does, and it's marked `Status: APPROVED`, ask: \"This feature already has a signed-off design. Start over or review the existing one?\"\n\n---\n\n## Phase 1: Design Source\n\nDetermine where the design will come from.\n\n### Step 1: Check for Figma MCP\n\nAttempt to detect whether a Figma MCP tool is available in the current session.\n\n**If `--figma` argument was provided OR Figma MCP is available:**\n```\nFigma integration detected.\n\nOptions:\n  A) Provide a Figma file URL or frame ID to start from an existing design\n  B) Skip Figma and generate wireframes from scratch\n```\n\nIf the human provides a Figma link:\n- Use the Figma MCP to read the frame(s)\n- Summarize what was found: screen names, key components, flow structure\n- Note: Figma MCP is read-only — changes happen in conversation, not in Figma itself\n- Proceed to Phase 2 with the Figma content as the starting point\n\n**If no Figma MCP and no `--figma` argument:**\n- Skip Figma detection silently\n- Proceed directly to wireframe generation in Phase 2\n\n---\n\n## Phase 2: UX Iteration Loop\n\nThis phase is a conversation loop. Repeat until the human approves the design or explicitly exits.\n\n### Step 1: Understand the UI Requirements\n\nBefore generating anything, ask focused questions to understand what needs to be designed. Keep it tight — 3-5 questions max.\n\n**Q1:** \"What are the primary screens or views in this feature?\"\n→ Captures: screen inventory\n\n**Q2:** \"Walk me through the main user flow — what does the user do, step by step?\"\n→ Captures: primary path, transitions between screens\n\n**Q3:** \"What are the key UI states? Think: loading, empty, error, success, edge cases.\"\n→ Captures: state matrix — the most commonly missed UX work\n\n**Q4 (optional):** \"Are there any existing patterns in the app this should follow? Or intentional departures?\"\n→ Captures: design system constraints, intentional exceptions\n\n**Q5 (optional):** \"Any mobile\u002Fresponsive requirements, accessibility constraints, or performance-sensitive areas?\"\n→ Captures: non-functional UX requirements\n\n### Step 2: Generate Initial Wireframes\n\nBased on the answers (and Figma content if available), generate wireframes for each screen.\n\nUse ASCII wireframes by default. They are fast to generate, easy to iterate on in conversation, and require no external tools.\n\n**ASCII wireframe format:**\n```\n┌─────────────────────────────────┐\n│  Screen Name                    │\n├─────────────────────────────────┤\n│  [Header \u002F Nav]                 │\n│                                 │\n│  ┌───────────────────────────┐  │\n│  │  Primary content area     │  │\n│  │                           │  │\n│  │  [Component A]            │  │\n│  │  [Component B]            │  │\n│  └───────────────────────────┘  │\n│                                 │\n│  [CTA Button]   [Secondary]     │\n└─────────────────────────────────┘\n```\n\nGenerate all primary screens in sequence. Label each clearly. Show transitions between screens with arrows or notes.\n\nAfter generating, present the full set:\n```\nHere's the initial design for {feature-name}:\n\nScreen 1: {Name} — {one-line description}\n{wireframe}\n\nScreen 2: {Name} — {one-line description}\n{wireframe}\n\n[etc.]\n\nState matrix:\n  Loading:  {description or wireframe}\n  Empty:    {description or wireframe}\n  Error:    {description or wireframe}\n  Success:  {description or wireframe}\n\nDoes this capture the intent? What would you change?\n```\n\n### Step 3: Iterate\n\nThe human will respond with feedback. Common patterns:\n\n- **\"Move X to Y\"** → Update the affected wireframe(s), re-display only what changed\n- **\"Add a state for Z\"** → Add to the state matrix\n- **\"What about mobile?\"** → Generate responsive variant(s)\n- **\"Can we simplify this?\"** → Consolidate screens, reduce cognitive load, explain the trade-off\n- **\"Show me option B\"** → Generate an alternative approach side-by-side\n\nKeep iterating until one of:\n- Human says something like \"looks good\", \"ship it\", \"I'm happy with this\" → move to Phase 3\n- Human explicitly exits: \"stop\", \"skip sign-off\" → write draft artifact and note it's unsigned\n\n**Iteration discipline:**\n- Never silently change something that wasn't mentioned\n- Call out any UX concerns you notice (e.g., \"this flow requires 5 taps to reach a frequent action — worth reconsidering?\")\n- If a requested change conflicts with a stated acceptance criterion, flag it: \"This change would affect AC-003 — should we update the spec too?\"\n\n---\n\n## Phase 3: Sign-Off and Artifact\n\nOnce the human approves the design:\n\n### Step 1: Summarize the Design\n\nPresent a clean summary before writing the artifact:\n```\nDesign approved for: {feature-name}\n\nScreens: {N}\n  • {Screen 1}: {one-liner}\n  • {Screen 2}: {one-liner}\n\nStates covered: loading, empty, error, success{, and X}\n\nKey decisions made:\n  • {Decision 1 and rationale}\n  • {Decision 2 and rationale}\n\nSpec impact: {None | \"AC-003 should be updated to reflect...\"}\n```\n\n### Step 2: Write the UX Artifact\n\nWrite to `specs\u002Fux\u002F{feature-slug}-ux.md`:\n\n```markdown\n# UX Design: {Feature Name}\n\n**Spec:** specs\u002F{feature-slug}.md\n**Status:** APPROVED\n**Approved:** {date}\n**Iterations:** {N}\n\n## Screens\n\n### {Screen 1 Name}\n{ASCII wireframe}\n{Notes}\n\n### {Screen 2 Name}\n{ASCII wireframe}\n{Notes}\n\n[etc.]\n\n## State Matrix\n\n| State    | Behavior | Notes |\n|----------|----------|-------|\n| Loading  | {description} | |\n| Empty    | {description} | |\n| Error    | {description} | |\n| Success  | {description} | |\n\n## Flow\n\n{Description of transitions between screens}\n\n## Key Decisions\n\n| Decision | Rationale | Alternatives Considered |\n|----------|-----------|------------------------|\n| {decision} | {why} | {what else was considered} |\n\n## Figma Reference\n\n{If Figma was used: URL, frame names, notes on divergence from Figma}\n{If no Figma: \"N\u002FA — wireframes generated in session\"}\n\n## Spec Notes\n\n{Any acceptance criteria or spec sections that should be updated based on design decisions}\n```\n\n### Step 3: Update the Feature Spec\n\nIf any spec updates are needed (e.g., Q8 was empty and is now filled in, or a design decision affects an AC):\n1. Read `specs\u002F{feature-slug}.md`\n2. Update the relevant sections (UI states, acceptance criteria, notes)\n3. Add a note: `UI design approved — see specs\u002Fux\u002F{feature-slug}-ux.md`\n\n### Step 4: Present Next Steps\n\n```\nUX design signed off: specs\u002Fux\u002F{feature-slug}-ux.md\n\nThis feature is now ready for implementation planning.\n\nNext steps:\n  \u002Fadd:plan specs\u002F{feature-slug}.md    — create implementation plan\n  \u002Fadd:tdd-cycle specs\u002F{feature-slug}.md — jump straight into TDD\n```\n\nIf spec was updated:\n```\nNote: specs\u002F{feature-slug}.md was updated to reflect design decisions.\nReview the changes before proceeding.\n```\n\n---\n\n## Maturity Behavior\n\n| Maturity | UX Gate Required? | Wireframe Depth | Sign-Off |\n|----------|-------------------|-----------------|----------|\n| POC      | Optional (prompted) | Minimal — key screen only | Informal (\"looks good\") |\n| Alpha    | Recommended for UI features | Primary screens + states | Human confirms in chat |\n| Beta     | Required for user-facing features | All screens + full state matrix | Explicit approval + artifact written |\n| GA       | Required for all UI changes | All screens + states + responsive + a11y notes | Artifact written + spec updated |\n\nAt POC maturity, the skill will note: \"UX gate is optional at POC maturity. Skipping means accepting rework risk if the design needs to change after implementation.\"\n","# ADD UX Command v{{VERSION}}\n\nIterate on UI\u002FUX design for a feature before implementation begins. Produces a signed-off design artifact that gates `\u002Fadd:plan` and `\u002Fadd:tdd-cycle`. Prevents token burn from building the wrong UI.\n\n## Pre-Flight\n\n1. Read `.add\u002Fconfig.json` to understand project context and maturity level\n2. If `spec-file` argument is provided, read it. Otherwise, list specs in `specs\u002F` and ask which feature to design\n3. Verify the spec exists and has a UI component (Q8 answered, or acceptance criteria mention UI states)\n   - If no UI component is detectable, confirm with the human: \"This spec doesn't appear to have a UI — do you still want to run a UX iteration?\"\n4. Check if a UI artifact already exists at `specs\u002Fux\u002F{feature-slug}-ux.md`\n   - If it does, and it's marked `Status: APPROVED`, ask: \"This feature already has a signed-off design. Start over or review the existing one?\"\n\n---\n\n## Phase 1: Design Source\n\nDetermine where the design will come from.\n\n### Step 1: Check for Figma MCP\n\nAttempt to detect whether a Figma MCP tool is available in the current session.\n\n**If `--figma` argument was provided OR Figma MCP is available:**\n```\nFigma integration detected.\n\nOptions:\n  A) Provide a Figma file URL or frame ID to start from an existing design\n  B) Skip Figma and generate wireframes from scratch\n```\n\nIf the human provides a Figma link:\n- Use the Figma MCP to read the frame(s)\n- Summarize what was found: screen names, key components, flow structure\n- Note: Figma MCP is read-only — changes happen in conversation, not in Figma itself\n- Proceed to Phase 2 with the Figma content as the starting point\n\n**If no Figma MCP and no `--figma` argument:**\n- Skip Figma detection silently\n- Proceed directly to wireframe generation in Phase 2\n\n---\n\n## Phase 2: UX Iteration Loop\n\nThis phase is a conversation loop. Repeat until the human approves the design or explicitly exits.\n\n### Step 1: Understand the UI Requirements\n\nBefore generating anything, ask focused questions to understand what needs to be designed. Keep it tight — 3-5 questions max.\n\n**Q1:** \"What are the primary screens or views in this feature?\"\n→ Captures: screen inventory\n\n**Q2:** \"Walk me through the main user flow — what does the user do, step by step?\"\n→ Captures: primary path, transitions between screens\n\n**Q3:** \"What are the key UI states? Think: loading, empty, error, success, edge cases.\"\n→ Captures: state matrix — the most commonly missed UX work\n\n**Q4 (optional):** \"Are there any existing patterns in the app this should follow? Or intentional departures?\"\n→ Captures: design system constraints, intentional exceptions\n\n**Q5 (optional):** \"Any mobile\u002Fresponsive requirements, accessibility constraints, or performance-sensitive areas?\"\n→ Captures: non-functional UX requirements\n\n### Step 2: Generate Initial Wireframes\n\nBased on the answers (and Figma content if available), generate wireframes for each screen.\n\nUse ASCII wireframes by default. They are fast to generate, easy to iterate on in conversation, and require no external tools.\n\n**ASCII wireframe format:**\n```\n┌─────────────────────────────────┐\n│  Screen Name                    │\n├─────────────────────────────────┤\n│  [Header \u002F Nav]                 │\n│                                 │\n│  ┌───────────────────────────┐  │\n│  │  Primary content area     │  │\n│  │                           │  │\n│  │  [Component A]            │  │\n│  │  [Component B]            │  │\n│  └───────────────────────────┘  │\n│                                 │\n│  [CTA Button]   [Secondary]     │\n└─────────────────────────────────┘\n```\n\nGenerate all primary screens in sequence. Label each clearly. Show transitions between screens with arrows or notes.\n\nAfter generating, present the full set:\n```\nHere's the initial design for {feature-name}:\n\nScreen 1: {Name} — {one-line description}\n{wireframe}\n\nScreen 2: {Name} — {one-line description}\n{wireframe}\n\n[etc.]\n\nState matrix:\n  Loading:  {description or wireframe}\n  Empty:    {description or wireframe}\n  Error:    {description or wireframe}\n  Success:  {description or wireframe}\n\nDoes this capture the intent? What would you change?\n```\n\n### Step 3: Iterate\n\nThe human will respond with feedback. Common patterns:\n\n- **\"Move X to Y\"** → Update the affected wireframe(s), re-display only what changed\n- **\"Add a state for Z\"** → Add to the state matrix\n- **\"What about mobile?\"** → Generate responsive variant(s)\n- **\"Can we simplify this?\"** → Consolidate screens, reduce cognitive load, explain the trade-off\n- **\"Show me option B\"** → Generate an alternative approach side-by-side\n\nKeep iterating until one of:\n- Human says something like \"looks good\", \"ship it\", \"I'm happy with this\" → move to Phase 3\n- Human explicitly exits: \"stop\", \"skip sign-off\" → write draft artifact and note it's unsigned\n\n**Iteration discipline:**\n- Never silently change something that wasn't mentioned\n- Call out any UX concerns you notice (e.g., \"this flow requires 5 taps to reach a frequent action — worth reconsidering?\")\n- If a requested change conflicts with a stated acceptance criterion, flag it: \"This change would affect AC-003 — should we update the spec too?\"\n\n---\n\n## Phase 3: Sign-Off and Artifact\n\nOnce the human approves the design:\n\n### Step 1: Summarize the Design\n\nPresent a clean summary before writing the artifact:\n```\nDesign approved for: {feature-name}\n\nScreens: {N}\n  • {Screen 1}: {one-liner}\n  • {Screen 2}: {one-liner}\n\nStates covered: loading, empty, error, success{, and X}\n\nKey decisions made:\n  • {Decision 1 and rationale}\n  • {Decision 2 and rationale}\n\nSpec impact: {None | \"AC-003 should be updated to reflect...\"}\n```\n\n### Step 2: Write the UX Artifact\n\nWrite to `specs\u002Fux\u002F{feature-slug}-ux.md`:\n\n```markdown\n# UX Design: {Feature Name}\n\n**Spec:** specs\u002F{feature-slug}.md\n**Status:** APPROVED\n**Approved:** {date}\n**Iterations:** {N}\n\n## Screens\n\n### {Screen 1 Name}\n{ASCII wireframe}\n{Notes}\n\n### {Screen 2 Name}\n{ASCII wireframe}\n{Notes}\n\n[etc.]\n\n## State Matrix\n\n| State    | Behavior | Notes |\n|----------|----------|-------|\n| Loading  | {description} | |\n| Empty    | {description} | |\n| Error    | {description} | |\n| Success  | {description} | |\n\n## Flow\n\n{Description of transitions between screens}\n\n## Key Decisions\n\n| Decision | Rationale | Alternatives Considered |\n|----------|-----------|------------------------|\n| {decision} | {why} | {what else was considered} |\n\n## Figma Reference\n\n{If Figma was used: URL, frame names, notes on divergence from Figma}\n{If no Figma: \"N\u002FA — wireframes generated in session\"}\n\n## Spec Notes\n\n{Any acceptance criteria or spec sections that should be updated based on design decisions}\n```\n\n### Step 3: Update the Feature Spec\n\nIf any spec updates are needed (e.g., Q8 was empty and is now filled in, or a design decision affects an AC):\n1. Read `specs\u002F{feature-slug}.md`\n2. Update the relevant sections (UI states, acceptance criteria, notes)\n3. Add a note: `UI design approved — see specs\u002Fux\u002F{feature-slug}-ux.md`\n\n### Step 4: Present Next Steps\n\n```\nUX design signed off: specs\u002Fux\u002F{feature-slug}-ux.md\n\nThis feature is now ready for implementation planning.\n\nNext steps:\n  \u002Fadd:plan specs\u002F{feature-slug}.md    — create implementation plan\n  \u002Fadd:tdd-cycle specs\u002F{feature-slug}.md — jump straight into TDD\n```\n\nIf spec was updated:\n```\nNote: specs\u002F{feature-slug}.md was updated to reflect design decisions.\nReview the changes before proceeding.\n```\n\n---\n\n## Maturity Behavior\n\n| Maturity | UX Gate Required? | Wireframe Depth | Sign-Off |\n|----------|-------------------|-----------------|----------|\n| POC      | Optional (prompted) | Minimal — key screen only | Informal (\"looks good\") |\n| Alpha    | Recommended for UI features | Primary screens + states | Human confirms in chat |\n| Beta     | Required for user-facing features | All screens + full state matrix | Explicit approval + artifact written |\n| GA       | Required for all UI changes | All screens + states + responsive + a11y notes | Artifact written + spec updated |\n\nAt POC maturity, the skill will note: \"UX gate is optional at POC maturity. Skipping means accepting rework risk if the design needs to change after implementation.\"\n",{"references":54,"description":7,"allowed-tools":57,"argument-hint":64},[55,56],"design-system.md","rules\u002Ftelemetry.md",[58,59,60,61,62,31,63],"Read","Write","Edit","Glob","Grep","AskUserQuestion","\u003Cspec-file> [--figma \u003Curl-or-frame-id>]","main","e335248c85d50f73919320bc138766eb413c5ee3","core\u002Fskills\u002Fux",6,"https:\u002F\u002Fgithub.com\u002FMountainUnicorn\u002Fadd","https:\u002F\u002Fgetadd.dev","https:\u002F\u002Fgithub.com\u002FMountainUnicorn","2026-10-31 22:03:50",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add MountainUnicorn\u002Fadd --skill ux",{"tool":79,"command":80},"bunx","bunx skills add MountainUnicorn\u002Fadd --skill ux",{"tool":82,"command":83},"pnpm","pnpm dlx skills add MountainUnicorn\u002Fadd --skill ux","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMountainUnicorn\u002Fadd\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fux\u002FSKILL.md",true,[87,92,98],{"path":88,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"LICENSE","许可证",1071,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fdanthamanvoiss-website-marketing-audit\u002FLICENSE",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"SOURCE.md","REFERENCE","参考文档",425,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fdanthamanvoiss-website-marketing-audit\u002FSOURCE.md",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fdanthamanvoiss-website-marketing-audit\u002FTRUST.auto.yaml",[103,111,116,121,131,156],{"skillNo":104,"name":105,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":49},"01M6CHXN68ZCGNXE9Q0K2T2RKX","add-verify","https:\u002F\u002Fgithub.com\u002FMountainUnicorn\u002Fadd\u002Fblob\u002Fmain\u002Ftests\u002Fhooks\u002Ffixtures\u002Fdoctor\u002Fmanifest-modified\u002Fskills\u002Fadd-verify\u002FSKILL.md",[],[109,110],"add verify","verify",{"skillNo":112,"name":105,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":49},"01M6CHXJY4ZXKTNP0235A9KTNH","https:\u002F\u002Fgithub.com\u002FMountainUnicorn\u002Fadd\u002Fblob\u002Fmain\u002Ftests\u002Fhooks\u002Ffixtures\u002Fdoctor\u002Fmanifest-missing\u002Fskills\u002Fadd-verify\u002FSKILL.md",[],[109,110],{"skillNo":117,"name":105,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":49},"01M6CHXG6NV1DBMWT2N6XE5555","https:\u002F\u002Fgithub.com\u002FMountainUnicorn\u002Fadd\u002Fblob\u002Fmain\u002Ftests\u002Fhooks\u002Ffixtures\u002Fdoctor\u002Fhealthy\u002Fskills\u002Fadd-verify\u002FSKILL.md",[],[109,110],{"skillNo":122,"name":34,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":49},"01M6CHXDZFPEFBZ79GHP48S1BB","[ADD v0.11.0] Show installed version, project version, and upgrade status","https:\u002F\u002Fgithub.com\u002FMountainUnicorn\u002Fadd\u002Fblob\u002Fmain\u002Fplugins\u002Fadd\u002Fskills\u002Fversion\u002FSKILL.md",[],[34,38,127,47,31,39,128,37,129,130],"status","check","v0","show",{"skillNo":132,"name":110,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":143,"publishedAt":49},"01M6CHXB5XG415PP88E0GACHP8","[ADD v0.11.0] Run quality gates — lint, types, tests, coverage, spec compliance","https:\u002F\u002Fgithub.com\u002FMountainUnicorn\u002Fadd\u002Fblob\u002Fmain\u002Fplugins\u002Fadd\u002Fskills\u002Fverify\u002FSKILL.md",[136,139,140],{"categoryNo":137,"categoryName":138,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":141,"categoryName":142,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000037","律师与法务",[110,38,37,144,145,129,146,147,39,47,48,148,149,150,151,152,153,31,154,155],"coverage","fix","smoke","gate","quality gates","run","lint","ci","compliance","secrets","learning","quality",{"skillNo":157,"name":5,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":164,"publishedAt":49},"01M6CHX8JF3M3J8BKTBW604D37","[ADD v0.11.0] Iterate on UI\u002FUX design before implementation — wireframes, flow validation, and design sign-off","https:\u002F\u002Fgithub.com\u002FMountainUnicorn\u002Fadd\u002Fblob\u002Fmain\u002Fplugins\u002Fadd\u002Fskills\u002Fux\u002FSKILL.md",[161,162,163],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},[5,43,44,45,46,47,48,31,40,39,38,37,36,35,129,33,32,42,41]]