[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MZ2CVFWBP7TF9PH6B8Q8A":3,"skill-same:01M71MZ2CVFWBP7TF9PH6B8Q8A":85},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M71MZ2CVFWBP7TF9PH6B8Q8A","solution",null,"Use when the user wants to write system architecture at docs\u002Farchitecture\u002Fsolution.md (stub or full arc42-lite). Drafts or re-authors the document. Triggers on \"write the architecture\", \"solution design\", \"arc42\". Re-authoring is also how an existing solution.md gets critiqued or revised — docs-review checks writing quality and cross-document consistency, not architectural soundness. Do NOT use for business strategy (product), delivery phases (roadmap), epic list (tasks), work-item tdd.md (tdd), task Gherkin (tasks), or ADR files (adr write). Story AC belongs in docs\u002Fwork\u002F{work-id}\u002Ftasks.md.","carinyadigital\u002Fskills","carinyadigital","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F185663942?v=4","01M71MWSF49DXG75MCNJ5D9CE2","Carinya Digital","01M71MWSFRXEATZ2MQGKD8A2S2",2,"MIT","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsolution\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"review","write","read","at","delivery","how","product","business strategy","work","notes","architecture","tasks","when","roadmap","writing","files","design","re","arc42","2026-11-10 10:56:23",false,"---\nname: solution\ndescription: >\n  Use when the user wants to write system architecture at\n  docs\u002Farchitecture\u002Fsolution.md (stub or full arc42-lite). Drafts or\n  re-authors the document. Triggers on \"write the architecture\", \"solution\n  design\", \"arc42\". Re-authoring is also how an existing solution.md gets\n  critiqued or revised — docs-review checks writing quality and cross-document\n  consistency, not architectural soundness. Do NOT use for business strategy (product), delivery\n  phases (roadmap), epic list (tasks), work-item tdd.md (tdd), task\n  Gherkin (tasks), or ADR files (adr write). Story AC belongs in\n  docs\u002Fwork\u002F{work-id}\u002Ftasks.md.\nlicense: MIT\nallowed-tools: Read Write Glob Grep\nargument-hint: \"[--stage stub|full] [--context \u003Cnotes>]\"\nmetadata:\n  author: Carinya Parc\n  version: \"2.0\"\n  owner: architecture\n  work_shape: authoring\n  output_class: delivery-artefact\n---\n\n# Solution\n\nYou are a Solution Architect writing arc42-lite solution design.\n\n## Artefact\n\nDefault path: `docs\u002Farchitecture\u002Fsolution.md` — arc42-lite architecture (stub or full).\n\n## Path resolution\n\nIf the user names a different file path in their request, read and write that\npath instead of the default.\n\n## Stage (`--stage`)\n\n- `stub` — Phase 0: fill §1–§2 only; scaffold §3–11 as `[NEEDS CLARIFICATION]`. ≤2 pages.\n- `full` — Phase 2+: all eleven sections. 8–12 pages.\n\n## Negative constraints\n\nsolution.md MUST NOT contain:\n\n- Commercial rationale, personas, positioning → `docs\u002Fproduct\u002Fproduct.md`\n- Story-level acceptance criteria → `docs\u002Fwork\u002F{work-id}\u002Ftasks.md`\n- Phase sequencing → `docs\u002Fproduct\u002Froadmap.md`\n\n## Context\n\n\u003Cartifacts>\n[Stub: docs\u002Fproduct\u002Fproduct.md, architecture principles, system boundary\nFull: product.md, docs\u002Fwork\u002F{work-id}\u002Ftdd.md (skeleton mode), ADR register,\naccepted ADRs]\n\u003C\u002Fartifacts>\n\n## Steps (stub)\n\n1. Read product.md and architecture principles\n2. §1 Context and scope — boundary, C4 L1 (ASCII), owns \u002F does not own\n3. §2 Quality goals and constraints — top 3–5 NFRs, constraints\n4. Scaffold §3–11 with `[NEEDS CLARIFICATION]`\n5. Delete the `\u003C!-- DO NOT INCLUDE -->` comment block before saving\n\n## Steps (full)\n\n1. Read all context\n2. §1 Context and scope\n3. §2 Quality goals and constraints\n4. §3 Solution strategy — style, key choices, principles vs quality goals\n5. §4 Building block view — C4 L2\u002FL3, module layout\n6. §5 Runtime view — 2–5 key sequences\n7. §6 Data model and ubiquitous language\n8. §7 Cross-cutting concepts — observability, errors, security, testing\n9. §8 Deployment and environments\n10. §9 Architectural decisions — links to ADRs in `docs\u002Farchitecture\u002Fdecisions\u002F`; mark gaps as \"_(Not yet written)_\"\n11. §10 Risks, technical debt, open questions\n12. §11 Graduation candidates — patterns that may lift org-wide when reused\n13. Delete the `\u003C!-- DO NOT INCLUDE -->` comment block before saving\n\n## Quality rules\n\n- §1 includes text-based C4 L1 diagram\n- §3 names trade-offs, not only choices\n- §9 does not invent full ADR bodies — link or mark candidates\n- Do not repeat business context from product.md — link instead\n\n## Gotchas\n\n- **Per-work-item files\u002FAPIs** → cite from `docs\u002Fwork\u002F{work-id}\u002Ftdd.md`, don't duplicate full specs.\n- **Story-level Gherkin** → `tasks.md`, not solution.\n- **Closed ADRs** → `ADR-NNNN-*.md`; proposals stay in register only.\n\n## Output format\n\nMarkdown with YAML frontmatter. Save to the resolved path. Use\n[assets\u002Fsolution.template.md](assets\u002Fsolution.template.md).\n\n## Supporting files\n\n- [assets\u002Fsolution.template.md](assets\u002Fsolution.template.md)\n\n## Related skills\n\n- `product`, `tasks`, `tdd`, `adr`\n- `docs-review` — review or critique an existing solution.md\n","# Solution\n\nYou are a Solution Architect writing arc42-lite solution design.\n\n## Artefact\n\nDefault path: `docs\u002Farchitecture\u002Fsolution.md` — arc42-lite architecture (stub or full).\n\n## Path resolution\n\nIf the user names a different file path in their request, read and write that\npath instead of the default.\n\n## Stage (`--stage`)\n\n- `stub` — Phase 0: fill §1–§2 only; scaffold §3–11 as `[NEEDS CLARIFICATION]`. ≤2 pages.\n- `full` — Phase 2+: all eleven sections. 8–12 pages.\n\n## Negative constraints\n\nsolution.md MUST NOT contain:\n\n- Commercial rationale, personas, positioning → `docs\u002Fproduct\u002Fproduct.md`\n- Story-level acceptance criteria → `docs\u002Fwork\u002F{work-id}\u002Ftasks.md`\n- Phase sequencing → `docs\u002Fproduct\u002Froadmap.md`\n\n## Context\n\n\u003Cartifacts>\n[Stub: docs\u002Fproduct\u002Fproduct.md, architecture principles, system boundary\nFull: product.md, docs\u002Fwork\u002F{work-id}\u002Ftdd.md (skeleton mode), ADR register,\naccepted ADRs]\n\u003C\u002Fartifacts>\n\n## Steps (stub)\n\n1. Read product.md and architecture principles\n2. §1 Context and scope — boundary, C4 L1 (ASCII), owns \u002F does not own\n3. §2 Quality goals and constraints — top 3–5 NFRs, constraints\n4. Scaffold §3–11 with `[NEEDS CLARIFICATION]`\n5. Delete the `\u003C!-- DO NOT INCLUDE -->` comment block before saving\n\n## Steps (full)\n\n1. Read all context\n2. §1 Context and scope\n3. §2 Quality goals and constraints\n4. §3 Solution strategy — style, key choices, principles vs quality goals\n5. §4 Building block view — C4 L2\u002FL3, module layout\n6. §5 Runtime view — 2–5 key sequences\n7. §6 Data model and ubiquitous language\n8. §7 Cross-cutting concepts — observability, errors, security, testing\n9. §8 Deployment and environments\n10. §9 Architectural decisions — links to ADRs in `docs\u002Farchitecture\u002Fdecisions\u002F`; mark gaps as \"_(Not yet written)_\"\n11. §10 Risks, technical debt, open questions\n12. §11 Graduation candidates — patterns that may lift org-wide when reused\n13. Delete the `\u003C!-- DO NOT INCLUDE -->` comment block before saving\n\n## Quality rules\n\n- §1 includes text-based C4 L1 diagram\n- §3 names trade-offs, not only choices\n- §9 does not invent full ADR bodies — link or mark candidates\n- Do not repeat business context from product.md — link instead\n\n## Gotchas\n\n- **Per-work-item files\u002FAPIs** → cite from `docs\u002Fwork\u002F{work-id}\u002Ftdd.md`, don't duplicate full specs.\n- **Story-level Gherkin** → `tasks.md`, not solution.\n- **Closed ADRs** → `ADR-NNNN-*.md`; proposals stay in register only.\n\n## Output format\n\nMarkdown with YAML frontmatter. Save to the resolved path. Use\n[assets\u002Fsolution.template.md](assets\u002Fsolution.template.md).\n\n## Supporting files\n\n- [assets\u002Fsolution.template.md](assets\u002Fsolution.template.md)\n\n## Related skills\n\n- `product`, `tasks`, `tdd`, `adr`\n- `docs-review` — review or critique an existing solution.md\n",{"name":5,"license":15,"metadata":48,"description":53,"allowed-tools":54,"argument-hint":55},{"owner":34,"author":49,"version":50,"work_shape":51,"output_class":52},"Carinya Parc","2.0","authoring","delivery-artefact","Use when the user wants to write system architecture at docs\u002Farchitecture\u002Fsolution.md (stub or full arc42-lite). Drafts or re-authors the document. Triggers on \"write the architecture\", \"solution design\", \"arc42\". Re-authoring is also how an existing solution.md gets critiqued or revised — docs-review checks writing quality and cross-document consistency, not architectural soundness. Do NOT use for business strategy (product), delivery phases (roadmap), epic list (tasks), work-item tdd.md (tdd), task Gherkin (tasks), or ADR files (adr write). Story AC belongs in docs\u002Fwork\u002F{work-id}\u002Ftasks.md.\n","Read Write Glob Grep","[--stage stub|full] [--context \u003Cnotes>]","main","a130b08e73c014d346320ba5258cf89d60b5e070","skills\u002Fsolution",0,"https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills","https:\u002F\u002Fgithub.com\u002Fcarinyadigital","carinyadigital.com","AI agents and agentic operations for small and medium businesses.","2026-08-20 06:13:13",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add carinyadigital\u002Fskills --skill solution",{"tool":71,"command":72},"bunx","bunx skills add carinyadigital\u002Fskills --skill solution",{"tool":74,"command":75},"pnpm","pnpm dlx skills add carinyadigital\u002Fskills --skill solution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsolution\u002FSKILL.md",true,[79],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"assets\u002Fsolution.template.md","ASSET","资产文件",4355,"https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsolution\u002Fassets\u002Fsolution.template.md",[86,105,133,160,184,198],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":97,"publishedAt":43},"01M71N0PD9RJD79MXQR54DART2","skill-name","Replace with description of the skill and when the agent should use it.","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Ftemplate\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[98,99,100,101,102,36,103,104],"skill name","name","with","replace","use","author","it",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":118,"publishedAt":43},"01M71N0D9N2NSX040S4WST3TG3","validate","Use when the user wants final completion sign-off on any work item — epic, story, bug, or spike: every task in docs\u002Fwork\u002F{work-id}\u002Ftasks.md verified against Gherkin AC and, for an epic, roadmap phase exit criteria. Triggers on \"validate CHK01\", \"validate JIRA-123\", \"is this story done\", \"sign off the epic\". Builds an acceptance matrix with evidence, updates task and work-item status, and produces a validation report. Do NOT use for PR or branch code review (code-review), writing tasks (tasks), sprint retrospective (sprint-retro), or drafting the breakdown (tasks) or the technical design (tdd).","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate\u002FSKILL.md",[111,114,117],{"categoryNo":112,"categoryName":113,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":115,"categoryName":116,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[107,119,120,121,122,123,40,124,125,126,38,127,37,36,128,129,130,131,35,132],"back","branch","sprint","code review","decision","remote","decision-support","MCP","acceptance","updates","done","Bash","code","drafting",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":144,"publishedAt":43},"01M71N056DQWSSSYHSWYF7MNM6","ux-design-review","Use when the user wants a UX or design review of implemented UI — components, pages, or flows — against its design source, covering accessibility (WCAG 2.2 AA), interaction states, responsiveness, design fidelity, and design-system conformity. Triggers on \"review the checkout page\", \"check this UI before I ship it\", \"is this accessible\", \"does this match the design\". Live-environment-first: drives the rendered UI in a real browser where possible. Works with any framework or design tooling. Produces a structured verdict with a coverage statement; writes no source changes. Do NOT use to address or fix UX findings (ux-design-fix), for code correctness or security review (code-review), to review a tdd.md document (docs-review), or to implement features (implement).","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fux-design-review\u002FSKILL.md",[139,140,141],{"categoryNo":115,"categoryName":116,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[40,145,24,146,147,148,149,120,150,151,152,153,126,154,155,156,157,158,159,26],"ux design review","ux","ux design","design review","reviews","figma","browser mcp","static","fix","URL","components","server","interaction","security review","figma mcp",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":172,"publishedAt":43},"01M71MZV7G5S97AVBNRSR60NAS","ux-design-fix","Use when the user wants to change how existing UI looks or behaves — fix spacing, colour, layout, states, responsiveness, or accessibility on a component, page, or flow. Takes either a ux-design-review output (scoped by action tier) or a direct instruction. Triggers on \"the summary card padding is off\", \"the modal breaks on mobile\", \"make the focus ring visible\", \"fix the UX review findings\", \"this button looks wrong\". Fixes via design tokens and library components rather than local patches, re-renders to verify visually, and re-checks neighbours for shift. Do NOT use to build new UI, screens, or flows (implement), to review UI without changing it (ux-design-review), to fix code-review findings (code-review-fix), or to redesign a component or flow.","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fux-design-fix\u002FSKILL.md",[166,167,168,171],{"categoryNo":115,"categoryName":116,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":169,"categoryName":170,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},[153,40,146,173,147,174,151,175,176,41,177,178,179,180,181,182,126,183,36,130],"ux design fix","design fix","states","project","review findings","card","flows","local","ux-design","new","either",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":192,"publishedAt":43},"01M71MZNT1G9Q83P374S8KCPTY","tdd","Use when the user wants a technical design document (TDD) for any work item — epic, story, bug, or spike — at docs\u002Fwork\u002F{work-id}\u002Ftdd.md, in skeleton or full mode. Pass a work item ID (CHK01, or a Linear\u002FJira\u002FGitHub key like JIRA-123). Resolves the source system and writes at whatever level the ID names — a story gets its own tdd.md beside its parent epic's, not nested inside it. Cite solution.md — do not re-narrate architecture. Triggers on \"tdd CHK01\", \"write the technical design for JIRA-123\", \"design the epic\", \"how should we build this story\". For reviewing an existing tdd.md, use docs-review instead. Do NOT use for test-driven development — writing a failing test first, red\u002Fgreen\u002Frefactor, or any test-authoring task is implement. Do NOT use to write the breakdown itself — stories, tasks, or sub-tasks (tasks), task Gherkin (tasks), system-wide architecture (solution), ADR write (adr), or code implementation (implement).","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftdd\u002FSKILL.md",[190,191],{"categoryNo":115,"categoryName":116,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[186,119,193,194,41,195,196,197,40,124,126,38,36,130,131,35,34,24,33,32],"test-driven","green","mode","failing","skeleton",{"skillNo":199,"name":35,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":205,"publishedAt":43},"01M71MZCPYDVZQCS12F54SJHHS","Use to decompose anything into delivery work — a product strategy and roadmap into epics, an epic into stories and tasks with Gherkin acceptance criteria, a story into sub-tasks, or an external spec, RFC, or PRD into both in one pass. Resolves the work item's source system (Linear, Jira, GitHub\u002FGitLab issues, or filesystem) and its type first. Writes docs\u002Fproduct\u002Fbacklog.md and docs\u002Fwork\u002F{work-id}\u002Ftasks.md, or the tracker directly when one is resolved. Triggers on \"break this spec into a backlog\", \"write the epics\", \"decompose checkout-foundation\", \"turn this RFC into tickets\", \"write tasks for CHK01\", \"write sub-tasks for JIRA-123\", \"what stories do we need\". EARS with --ears. Do NOT use to groom an existing backlog or check sprint readiness (backlog-refine), write technical design at any level (tdd), write architecture (solution), phase the delivery (roadmap), implement code (implement), or sign off a work item (validate).","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftasks\u002FSKILL.md",[203,204],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[35,119,121,206,207,40,208,124,126,127,37,36,130,131,34,209,33,32,5,210],"checkout","issues","gherkin acceptance criteria","phase","gitlab"]