[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71ESBD9CWFQBZK5E43S9EK6":3,"skill-same:01M71ESBD9CWFQBZK5E43S9EK6":79},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M71ESBD9CWFQBZK5E43S9EK6","pmo-design",null,"Use for product flows, UX and wireframes, creative direction, visual direction, art direction, brand conformance, distinctive or non-generic frontend direction, design systems, visual sheets, and design-ready acceptance criteria tied to scoped requirements.","witchwasin\u002FAxiom-PMO","witchwasin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F212774037?v=4","01M71ERPAKYZ7GWV9FV63G8Y9P","Witchwasin K.","01M71ERPB9RWQHQAQ2GQ2EEH7Q",3,"MIT","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Fskills\u002Fpmo-design\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"design","pmo","pmo design","requirements","use","scoped","sheets","for","generic","brand","conformance","ux","product","design systems","acceptance","frontend","Art","flows","direction","ready","2026-11-10 10:12:30",false,"---\nname: pmo-design\ndescription: Use for product flows, UX and wireframes, creative direction, visual direction, art direction, brand conformance, distinctive or non-generic frontend direction, design systems, visual sheets, and design-ready acceptance criteria tied to scoped requirements.\n---\n\n# pmo-design\n\n## Purpose\n\nTurn scoped requirements into flows, a source-backed visual direction, and a buildable design contract without inventing scope or approval.\n\n## Intents\n\n| Intent | Use when | Read set |\n|---|---|---|\n| `flow` (default) | Map requirements to flow, wireframe, or acceptance wording | `PROJECT.md`, relevant `DESIGN\u002F**` |\n| `visual_direction` | Establish creative\u002Fart direction, avoid generic defaults, or choose how the product should feel | see Required Inputs |\n| `design_system` | Turn a selected direction or existing brand into a developer contract and visual sheet | see Required Inputs |\n| `system_design` | Define architecture, data\u002FAPI boundaries, and early Test Strategy in `DESIGN\u002FBUILD-SPEC.md` | `PROJECT.md`, `DESIGN\u002FBUILD-SPEC.md` |\n| `design_provider` | Prepare the governed Claude Design handoff, run preflight, reconcile candidate output, and record the review | `PROJECT.md`, `DESIGN\u002FBUILD-SPEC.md`, `DESIGN\u002FCLAUDE-DESIGN\u002F**`, `EXTERNALIZATION.json`, `decision-log.md` |\n\nRead `docs\u002Fconcepts\u002Fvisual-direction.md` for creative-direction rules and `docs\u002Fconcepts\u002Fdesign-system.md` for the artifact contract. Do not restate them here.\n\n## Routing and Fallback\n\n1. Route requests for creative, distinctive, premium, unconventional, art direction, visual direction, or \"not generic\" work to `visual_direction`, even when the user also says \"design system\".\n2. For a new design system, consume `DESIGN\u002FVISUAL-DIRECTION.md` when its `direction_status` is `selected` or `conformance`.\n3. If no usable direction exists, use `visual_direction` first. An existing design system may be maintained without retroactively creating this artifact unless the direction is being reopened.\n4. Never reopen a selected direction inside `design_system`; record a proposed change as an open question and return to `visual_direction`.\n\n## Required Inputs\n\nAlways read `PROJECT.md`, relevant requirements and design files, and the configured context\u002Fartifact contracts.\n\n- `visual_direction`: read `DESIGN\u002FVISUAL-DIRECTION.md` if present, `DESIGN\u002FWIREFRAME.md`, `DESIGN\u002FBRAND\u002F**`, `decision-log.md`, and only the configured source files needed for the brief.\n- `design_system`: additionally read `DESIGN\u002FVISUAL-DIRECTION.md`, `DESIGN\u002FWIREFRAME.md`, `DESIGN\u002FBRAND\u002F**`, and `decision-log.md` if present. Read only the scoped set.\n\nAvoid delivery and release documents unless checking impact. The design system and visual direction remain optional in every mode; no gate requires either artifact.\n\n## Evidence and Authority\n\nUse the repository evidence ladder exactly: `verified` = direct source plus human approval; `supported` = direct source without final approval; `inferred` = reasoned from partial source; `missing` = not found; `conflict` = sources disagree. Never use evidence status to describe tool availability or whether a render ran.\n\nOnly a human may declare `brand_starting_point: undecided | existing`, select an art direction, or approve Design Ready. Use `direction_status: pending | selected | conformance`; `selected` requires explicit human choice and a decision reference, while `conformance` requires a human-confirmed existing brand.\n\n## Execution - flow\n\n1. Map requirement IDs to user and system flow steps.\n2. Create or update flow and wireframe artifacts only when the configured contract or confirmed impact requires them.\n3. Record assumptions, open questions, and usable delivery references.\n\n## Execution - system_design\n\n1. Complete System Design and the mode-aware Test Strategy in BUILD-SPEC before detailed UI work.\n2. Create flow\u002Fwireframe artifacts only for an active UI path and actual UI scope.\n3. Record a technical\u002Fscope mismatch as a candidate governed Change Request; do not silently widen the approved contract.\n\n## Execution - design_provider\n\nWhen `UI delivery: claude_design` is declared (see `docs\u002Fconcepts\u002Fclaude-design-workflow.md`):\n\n1. Prepare `DESIGN\u002FCLAUDE-DESIGN\u002FINPUT-MANIFEST.json` from `templates\u002FDESIGN-PROVIDER-INPUT.json`: digest-bound references to the minimum necessary canonical inputs only — never `source\u002F**` by default — plus an approved `EXTERNALIZATION.json` entry, provider, purpose, and generated timestamp. Run the `designProviderDigest` tool (`src\u002Ftools\u002Fdigest-tools.ts`) and record the current digests.\n2. Hand the folder to the Human-operated provider; candidate output lands in `DESIGN\u002FCLAUDE-DESIGN\u002FOUTPUT\u002F**`.\n3. Run the deterministic preflight (paths, manifest, declared screens\u002Fstates, digests, scope references) before any review is recorded.\n4. Perform semantic candidate reconciliation for business\u002FAPI\u002Fdata\u002Fpermission mismatches before Human review; these are candidate findings, not decisions.\n5. Record the Human review outcome in `DESIGN\u002FCLAUDE-DESIGN\u002FREVIEW.json` with a decision reference. Only a Human may mark acceptance (`DPROV-006`); an AI may propose revision.\n6. Route technical\u002Fscope findings through `CHANGE-REQUESTS.json` (`DPROV-007`) before the accepted design baseline is finalized; never silently widen the approved contract.\n7. After revision, recompute all digests; a changed output set invalidates the prior review. Accepted current output is what merges into Final Handoff.\n\n## Execution - visual_direction\n\n1. Read confirmed scope, decisions, wireframes, brand assets, and relevant sources before asking questions.\n2. Fill `DESIGN\u002FVISUAL-DIRECTION.md` from the template. Keep source facts and design judgements at their truthful evidence statuses.\n3. Ask a human for `brand_starting_point` if it is not already human-confirmed. Do not infer or default it.\n4. For `existing`, assess conformance and use `direction_status: conformance`; do not perform a theatrical multi-direction exercise.\n5. For `undecided`, propose two or three directions that differ in geometry, typography, composition, density, colour role, imagery, surface\u002Fdepth, or motion—not merely hex values. Set `direction_status: pending`, then stop for human selection.\n6. After an explicit human choice, set `direction_status: selected`, record the decision reference, and carry the selected direction into `design_system`. Never select on the human's behalf.\n7. If editing `decision-log.md`, first check whether it is semantic-review input; editing it can stale `HANDOFF-REVIEW.json`.\n\n## Execution - design_system\n\n1. List only screens already scoped in `PROJECT.md` and `DESIGN\u002FWIREFRAME.md`.\n2. Consume the selected\u002Fconformance direction and explain every presentation choice by pointing to a brief field. If that sentence cannot be written, the choice is an unexamined default.\n3. Write brand assets when needed, then `DESIGN\u002FDESIGN-SYSTEM.md` and the self-contained HTML sheet from their templates. Keep the first token block and required semantic anchors intact; rewrite the presentation layer to fit the direction.\n4. Keep Markdown and HTML token values identical. Fill the Sample Data Register and measure every contrast ratio stated.\n5. Render and show the sheet when tools permit. Report `tool_availability` and `render_status` separately; never claim a render or review that did not happen.\n6. At Handoff, when `VISUAL-DIRECTION.md`, `DESIGN-SYSTEM.md`, and `DESIGN-SYSTEM.html` all exist, prepare honest desktop and mobile captures when rendering tools permit. A named human must review them and record `DESIGN\u002FVISUAL-REVIEW.json`; an AI may draft notes but may not fabricate the reviewer, decision reference, or aesthetic outcome.\n7. Report assumptions, open questions, scoped screens drawn, undrawn states, and meaningful decisions. Editing a semantic-review or Visual Proof input can stale its candidate evidence.\n\n## Output Contract\n\nReturn changed design files, requirement coverage, evidence status, assumptions, unresolved questions, and any human decision still required. For visual work, also report selected\u002Fconformance direction, screens and states drawn or missing, `tool_availability`, `render_status`, and the rendered path when one exists. When Visual Proof applies at Handoff, report whether its capture and named-human review evidence are missing or stale; do not turn that report into approval.\n\n## Prohibited Actions\n\nDo not expand scope, remove source references, invent requirements or decision IDs, infer `brand_starting_point`, select a direction, mark approval, draw an unscoped screen, present an inference as confirmed, use real customer or personal data, claim an unavailable tool ran, or publish externally without explicit current-session instruction.\n\n## Completion Criteria\n\n- `flow`: every design-affecting item has a design reference or an allowed `not_required` sentinel.\n- `visual_direction`: brief evidence is truthful; status is `pending`, `selected`, or `conformance` consistently; any selection has human evidence and a decision reference.\n- `design_system`: the direction is traceable, `DESIGN-001` passes, no HTML placeholder remains, sample data is registered, every screen traces to a wireframe, and render\u002Ftool claims are honest. At Handoff, the conditional Visual Proof contract is complete only after a named human has recorded both committed captures and the review manifest.\n\n## Validation\n\n`node cli\u002Faxiom.mjs validate --project \u003Cproject> --mode \u003Cmode> --gate Design`\n\nThe artifact pair is candidate evidence only. Design Ready remains human-owned.\n\nVisual Proof stays in the repository workflow: active instructions are under `.claude\u002Fskills\u002F`, and\nthe generated `skills\u002F` package is refreshed by its build command. Do not create or maintain a\nseparate `.agents\u002Fskills` mirror for this capability.\n","# pmo-design\n\n## Purpose\n\nTurn scoped requirements into flows, a source-backed visual direction, and a buildable design contract without inventing scope or approval.\n\n## Intents\n\n| Intent | Use when | Read set |\n|---|---|---|\n| `flow` (default) | Map requirements to flow, wireframe, or acceptance wording | `PROJECT.md`, relevant `DESIGN\u002F**` |\n| `visual_direction` | Establish creative\u002Fart direction, avoid generic defaults, or choose how the product should feel | see Required Inputs |\n| `design_system` | Turn a selected direction or existing brand into a developer contract and visual sheet | see Required Inputs |\n| `system_design` | Define architecture, data\u002FAPI boundaries, and early Test Strategy in `DESIGN\u002FBUILD-SPEC.md` | `PROJECT.md`, `DESIGN\u002FBUILD-SPEC.md` |\n| `design_provider` | Prepare the governed Claude Design handoff, run preflight, reconcile candidate output, and record the review | `PROJECT.md`, `DESIGN\u002FBUILD-SPEC.md`, `DESIGN\u002FCLAUDE-DESIGN\u002F**`, `EXTERNALIZATION.json`, `decision-log.md` |\n\nRead `docs\u002Fconcepts\u002Fvisual-direction.md` for creative-direction rules and `docs\u002Fconcepts\u002Fdesign-system.md` for the artifact contract. Do not restate them here.\n\n## Routing and Fallback\n\n1. Route requests for creative, distinctive, premium, unconventional, art direction, visual direction, or \"not generic\" work to `visual_direction`, even when the user also says \"design system\".\n2. For a new design system, consume `DESIGN\u002FVISUAL-DIRECTION.md` when its `direction_status` is `selected` or `conformance`.\n3. If no usable direction exists, use `visual_direction` first. An existing design system may be maintained without retroactively creating this artifact unless the direction is being reopened.\n4. Never reopen a selected direction inside `design_system`; record a proposed change as an open question and return to `visual_direction`.\n\n## Required Inputs\n\nAlways read `PROJECT.md`, relevant requirements and design files, and the configured context\u002Fartifact contracts.\n\n- `visual_direction`: read `DESIGN\u002FVISUAL-DIRECTION.md` if present, `DESIGN\u002FWIREFRAME.md`, `DESIGN\u002FBRAND\u002F**`, `decision-log.md`, and only the configured source files needed for the brief.\n- `design_system`: additionally read `DESIGN\u002FVISUAL-DIRECTION.md`, `DESIGN\u002FWIREFRAME.md`, `DESIGN\u002FBRAND\u002F**`, and `decision-log.md` if present. Read only the scoped set.\n\nAvoid delivery and release documents unless checking impact. The design system and visual direction remain optional in every mode; no gate requires either artifact.\n\n## Evidence and Authority\n\nUse the repository evidence ladder exactly: `verified` = direct source plus human approval; `supported` = direct source without final approval; `inferred` = reasoned from partial source; `missing` = not found; `conflict` = sources disagree. Never use evidence status to describe tool availability or whether a render ran.\n\nOnly a human may declare `brand_starting_point: undecided | existing`, select an art direction, or approve Design Ready. Use `direction_status: pending | selected | conformance`; `selected` requires explicit human choice and a decision reference, while `conformance` requires a human-confirmed existing brand.\n\n## Execution - flow\n\n1. Map requirement IDs to user and system flow steps.\n2. Create or update flow and wireframe artifacts only when the configured contract or confirmed impact requires them.\n3. Record assumptions, open questions, and usable delivery references.\n\n## Execution - system_design\n\n1. Complete System Design and the mode-aware Test Strategy in BUILD-SPEC before detailed UI work.\n2. Create flow\u002Fwireframe artifacts only for an active UI path and actual UI scope.\n3. Record a technical\u002Fscope mismatch as a candidate governed Change Request; do not silently widen the approved contract.\n\n## Execution - design_provider\n\nWhen `UI delivery: claude_design` is declared (see `docs\u002Fconcepts\u002Fclaude-design-workflow.md`):\n\n1. Prepare `DESIGN\u002FCLAUDE-DESIGN\u002FINPUT-MANIFEST.json` from `templates\u002FDESIGN-PROVIDER-INPUT.json`: digest-bound references to the minimum necessary canonical inputs only — never `source\u002F**` by default — plus an approved `EXTERNALIZATION.json` entry, provider, purpose, and generated timestamp. Run the `designProviderDigest` tool (`src\u002Ftools\u002Fdigest-tools.ts`) and record the current digests.\n2. Hand the folder to the Human-operated provider; candidate output lands in `DESIGN\u002FCLAUDE-DESIGN\u002FOUTPUT\u002F**`.\n3. Run the deterministic preflight (paths, manifest, declared screens\u002Fstates, digests, scope references) before any review is recorded.\n4. Perform semantic candidate reconciliation for business\u002FAPI\u002Fdata\u002Fpermission mismatches before Human review; these are candidate findings, not decisions.\n5. Record the Human review outcome in `DESIGN\u002FCLAUDE-DESIGN\u002FREVIEW.json` with a decision reference. Only a Human may mark acceptance (`DPROV-006`); an AI may propose revision.\n6. Route technical\u002Fscope findings through `CHANGE-REQUESTS.json` (`DPROV-007`) before the accepted design baseline is finalized; never silently widen the approved contract.\n7. After revision, recompute all digests; a changed output set invalidates the prior review. Accepted current output is what merges into Final Handoff.\n\n## Execution - visual_direction\n\n1. Read confirmed scope, decisions, wireframes, brand assets, and relevant sources before asking questions.\n2. Fill `DESIGN\u002FVISUAL-DIRECTION.md` from the template. Keep source facts and design judgements at their truthful evidence statuses.\n3. Ask a human for `brand_starting_point` if it is not already human-confirmed. Do not infer or default it.\n4. For `existing`, assess conformance and use `direction_status: conformance`; do not perform a theatrical multi-direction exercise.\n5. For `undecided`, propose two or three directions that differ in geometry, typography, composition, density, colour role, imagery, surface\u002Fdepth, or motion—not merely hex values. Set `direction_status: pending`, then stop for human selection.\n6. After an explicit human choice, set `direction_status: selected`, record the decision reference, and carry the selected direction into `design_system`. Never select on the human's behalf.\n7. If editing `decision-log.md`, first check whether it is semantic-review input; editing it can stale `HANDOFF-REVIEW.json`.\n\n## Execution - design_system\n\n1. List only screens already scoped in `PROJECT.md` and `DESIGN\u002FWIREFRAME.md`.\n2. Consume the selected\u002Fconformance direction and explain every presentation choice by pointing to a brief field. If that sentence cannot be written, the choice is an unexamined default.\n3. Write brand assets when needed, then `DESIGN\u002FDESIGN-SYSTEM.md` and the self-contained HTML sheet from their templates. Keep the first token block and required semantic anchors intact; rewrite the presentation layer to fit the direction.\n4. Keep Markdown and HTML token values identical. Fill the Sample Data Register and measure every contrast ratio stated.\n5. Render and show the sheet when tools permit. Report `tool_availability` and `render_status` separately; never claim a render or review that did not happen.\n6. At Handoff, when `VISUAL-DIRECTION.md`, `DESIGN-SYSTEM.md`, and `DESIGN-SYSTEM.html` all exist, prepare honest desktop and mobile captures when rendering tools permit. A named human must review them and record `DESIGN\u002FVISUAL-REVIEW.json`; an AI may draft notes but may not fabricate the reviewer, decision reference, or aesthetic outcome.\n7. Report assumptions, open questions, scoped screens drawn, undrawn states, and meaningful decisions. Editing a semantic-review or Visual Proof input can stale its candidate evidence.\n\n## Output Contract\n\nReturn changed design files, requirement coverage, evidence status, assumptions, unresolved questions, and any human decision still required. For visual work, also report selected\u002Fconformance direction, screens and states drawn or missing, `tool_availability`, `render_status`, and the rendered path when one exists. When Visual Proof applies at Handoff, report whether its capture and named-human review evidence are missing or stale; do not turn that report into approval.\n\n## Prohibited Actions\n\nDo not expand scope, remove source references, invent requirements or decision IDs, infer `brand_starting_point`, select a direction, mark approval, draw an unscoped screen, present an inference as confirmed, use real customer or personal data, claim an unavailable tool ran, or publish externally without explicit current-session instruction.\n\n## Completion Criteria\n\n- `flow`: every design-affecting item has a design reference or an allowed `not_required` sentinel.\n- `visual_direction`: brief evidence is truthful; status is `pending`, `selected`, or `conformance` consistently; any selection has human evidence and a decision reference.\n- `design_system`: the direction is traceable, `DESIGN-001` passes, no HTML placeholder remains, sample data is registered, every screen traces to a wireframe, and render\u002Ftool claims are honest. At Handoff, the conditional Visual Proof contract is complete only after a named human has recorded both committed captures and the review manifest.\n\n## Validation\n\n`node cli\u002Faxiom.mjs validate --project \u003Cproject> --mode \u003Cmode> --gate Design`\n\nThe artifact pair is candidate evidence only. Design Ready remains human-owned.\n\nVisual Proof stays in the repository workflow: active instructions are under `.claude\u002Fskills\u002F`, and\nthe generated `skills\u002F` package is refreshed by its build command. Do not create or maintain a\nseparate `.agents\u002Fskills` mirror for this capability.\n",{"name":5,"description":7},"main","9a62fb94c5b3066a2810d0e6685c533a4e2df145","skills\u002Fpmo-design",1,"https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Freleases","https:\u002F\u002Fgithub.com\u002Fwitchwasin","2026-10-14 19:35:57",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add witchwasin\u002FAxiom-PMO --skill pmo-design",{"tool":71,"command":72},"bunx","bunx skills add witchwasin\u002FAxiom-PMO --skill pmo-design",{"tool":74,"command":75},"pnpm","pnpm dlx skills add witchwasin\u002FAxiom-PMO --skill pmo-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Fskills\u002Fpmo-design\u002FSKILL.md",true,[],[80,93,101,109,118,125],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":52},"01M71ET8C9TYQMP9F4TQT31E1Q","pmo-quality-release","Valid fixture skill description.","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-quality-release\u002FSKILL.md",[],[87,33,88,89,90,91,92],"pmo quality release","quality","release","fixture","fixture skill","valid",{"skillNo":94,"name":95,"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":96,"categories":97,"keywords":98,"publishedAt":52},"01M71ET6XRZVVAKSP58XX54G3W","pmo-intake","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-intake\u002FSKILL.md",[],[99,33,100],"pmo intake","intake",{"skillNo":102,"name":103,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":52},"01M71ET5CECTETCAE5FNRV0FRE","pmo-governance","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-governance\u002FSKILL.md",[],[107,33,108,90,91,92],"pmo governance","governance",{"skillNo":110,"name":111,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":52},"01M71ET3YQASNPFSFPJVG3V660","pmo-git-safety","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-git-safety\u002FSKILL.md",[],[33,115,116,117,90,91,92],"pmo git safety","Safety","git",{"skillNo":119,"name":5,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":124,"publishedAt":52},"01M71ET2DA7SMTNRW95K3QAF5J","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-design\u002FSKILL.md",[122,123],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[34,33,32,91,92,90],{"skillNo":126,"name":127,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":52},"01M71ET0VGV1DVPNXEQWX4P27V","pmo-delivery","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-delivery\u002FSKILL.md",[],[131,33,132,91,90,92],"delivery","pmo delivery"]