[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KW39E3YCEW0H9FA305MJHM":3,"skill-same:01M6KW39E3YCEW0H9FA305MJHM":68},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6KW39E3YCEW0H9FA305MJHM","architecture-review",null,"Structured architectural review skill for the HypermediaEngine project. Use when reviewing implemented code for architectural integrity, design flaws, convention compliance, and long-term risk. Invoked by the software-architect agent after implementation is complete.","rafsanulhasan\u002FHypermediaEngine","rafsanulhasan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2341142?v=4","01M6KW2HWPTZWK051N7B0HTBVG","Rafsanul Hasan","01M6KW2J0N3613382MF5DRN79H",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Farchitecture-review\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"review","architecture","architecture review","for","design","long","complete","software","project","structured","review skill","implementation","use","architect","integrity","risk","compliance","code","2026-11-10 10:12:30",false,"---\nname: architecture-review\ndescription: Structured architectural review skill for the HypermediaEngine project. Use when reviewing implemented code for architectural integrity, design flaws, convention compliance, and long-term risk. Invoked by the software-architect agent after implementation is complete.\n---\n\n# Architecture Review\n\nYou are executing the `architecture-review` skill on behalf of the software-architect agent. Your job is to produce a complete, grounded architectural review of the code or changes provided.\n\n## Input\n\nThe calling agent will pass one of:\n- A description of recently implemented or modified code\n- A list of changed files or a diff to review\n- A specific architectural concern to investigate\n\n## Process\n\n### Step 1 — Scope the Review\n\nFocus on what changed, not the entire codebase. Use **Glob** and **Read** to locate changed files, then **Grep** to trace how new components are wired into the existing system.\n\n### Step 2 — Apply the Review Framework\n\nEvaluate each dimension systematically:\n\n1. **Separation of Concerns** — Are responsibilities cleanly divided? Does each component have a single, well-defined purpose?\n2. **Coupling and Cohesion** — Is the design loosely coupled and highly cohesive? Are dependencies flowing in the right direction?\n3. **Extensibility** — Can the system accommodate foreseeable changes without major restructuring?\n4. **Reliability** — Are there single points of failure? Is error handling sound? Does the `{ data, error }` return shape propagate correctly through all paths?\n5. **Security Boundaries** — Are sensitive operations properly isolated? Are there information leakage risks in the API surface?\n6. **Testability** — Is the architecture designed to support unit, integration, and mutation testing (`dotnet stryker`)?\n7. **Scalability** — Only flag when realistic load increases would degrade this design.\n\n### Step 3 — Check Convention Compliance\n\nVerify adherence to project conventions:\n- Explicit type declarations with target-typed new expressions or collection expressions\n- Async disposal preferred over sync disposal (`await using`)\n- Return shape is always `{ data, error }`\n- No stack traces exposed to clients\n- Logger module used, not console output\n- DI-registered services — no hidden `new` for dependencies\n\n### Step 4 — Produce the Review\n\nStructure your output as:\n\n---\n\n**Verdict**: `APPROVED` \u002F `APPROVED WITH CONCERNS` \u002F `REQUIRES REVISION`\n\n**Design Flaws** *(if any)*\nList issues that have architectural impact — not just code style. For each:\n- Severity: `CRITICAL` (blocks design) \u002F `MAJOR` (significant risk) \u002F `MINOR` (improvement opportunity)\n- Description: What the flaw is and why it matters structurally\n- Location: Specific file, class, or method\n\n**Recommended Improvements**\nConcrete, actionable changes with rationale. Never vague — e.g., not \"consider better abstractions\" but \"extract X responsibility into a dedicated Y service because Z\".\n\n**Scalability \u002F Reliability Concerns** *(only if applicable at realistic scale)*\n\n**Convention Compliance**\nList any violations. If compliant, state \"All project conventions followed.\"\n\n**Positive Observations**\nWhat was done well architecturally. Always include at least one — this builds institutional knowledge.\n\n---\n\n### Step 5 — Finalize\n\nBefore returning:\n- Every flaw must have a concrete recommended improvement\n- Severity labels must be applied consistently — CRITICAL only when the design cannot proceed as-is\n- If verdict is REQUIRES REVISION, the recommended improvements must be sufficient to resolve all CRITICAL and MAJOR flaws\n","# Architecture Review\n\nYou are executing the `architecture-review` skill on behalf of the software-architect agent. Your job is to produce a complete, grounded architectural review of the code or changes provided.\n\n## Input\n\nThe calling agent will pass one of:\n- A description of recently implemented or modified code\n- A list of changed files or a diff to review\n- A specific architectural concern to investigate\n\n## Process\n\n### Step 1 — Scope the Review\n\nFocus on what changed, not the entire codebase. Use **Glob** and **Read** to locate changed files, then **Grep** to trace how new components are wired into the existing system.\n\n### Step 2 — Apply the Review Framework\n\nEvaluate each dimension systematically:\n\n1. **Separation of Concerns** — Are responsibilities cleanly divided? Does each component have a single, well-defined purpose?\n2. **Coupling and Cohesion** — Is the design loosely coupled and highly cohesive? Are dependencies flowing in the right direction?\n3. **Extensibility** — Can the system accommodate foreseeable changes without major restructuring?\n4. **Reliability** — Are there single points of failure? Is error handling sound? Does the `{ data, error }` return shape propagate correctly through all paths?\n5. **Security Boundaries** — Are sensitive operations properly isolated? Are there information leakage risks in the API surface?\n6. **Testability** — Is the architecture designed to support unit, integration, and mutation testing (`dotnet stryker`)?\n7. **Scalability** — Only flag when realistic load increases would degrade this design.\n\n### Step 3 — Check Convention Compliance\n\nVerify adherence to project conventions:\n- Explicit type declarations with target-typed new expressions or collection expressions\n- Async disposal preferred over sync disposal (`await using`)\n- Return shape is always `{ data, error }`\n- No stack traces exposed to clients\n- Logger module used, not console output\n- DI-registered services — no hidden `new` for dependencies\n\n### Step 4 — Produce the Review\n\nStructure your output as:\n\n---\n\n**Verdict**: `APPROVED` \u002F `APPROVED WITH CONCERNS` \u002F `REQUIRES REVISION`\n\n**Design Flaws** *(if any)*\nList issues that have architectural impact — not just code style. For each:\n- Severity: `CRITICAL` (blocks design) \u002F `MAJOR` (significant risk) \u002F `MINOR` (improvement opportunity)\n- Description: What the flaw is and why it matters structurally\n- Location: Specific file, class, or method\n\n**Recommended Improvements**\nConcrete, actionable changes with rationale. Never vague — e.g., not \"consider better abstractions\" but \"extract X responsibility into a dedicated Y service because Z\".\n\n**Scalability \u002F Reliability Concerns** *(only if applicable at realistic scale)*\n\n**Convention Compliance**\nList any violations. If compliant, state \"All project conventions followed.\"\n\n**Positive Observations**\nWhat was done well architecturally. Always include at least one — this builds institutional knowledge.\n\n---\n\n### Step 5 — Finalize\n\nBefore returning:\n- Every flaw must have a concrete recommended improvement\n- Severity labels must be applied consistently — CRITICAL only when the design cannot proceed as-is\n- If verdict is REQUIRES REVISION, the recommended improvements must be sufficient to resolve all CRITICAL and MAJOR flaws\n",{"name":5,"description":7},"main","00b2c68281930728ee390bb16cec32b88d2caac7",".claude\u002Fskills\u002Farchitecture-review","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine","https:\u002F\u002Fgithub.com\u002Frafsanulhasan","\r\n    MCSD || A-CSD || Software Architect\r\n\r\n","2026-06-06 07:47:06",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add rafsanulhasan\u002FHypermediaEngine --skill architecture-review",{"tool":60,"command":61},"bunx","bunx skills add rafsanulhasan\u002FHypermediaEngine --skill architecture-review",{"tool":63,"command":64},"pnpm","pnpm dlx skills add rafsanulhasan\u002FHypermediaEngine --skill architecture-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Farchitecture-review\u002FSKILL.md",true,[],[69,98,117,134,161,184],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":80,"publishedAt":42},"01M6KWEJD606FG3DBBRM0W4DKW","write-tests","Test implementation skill for HypermediaEngine. Takes a confirmed test plan from design-test-cases and produces compilable, runnable xUnit tests following project conventions. Validates coverage quality through mutation testing. Invoked by the sqa-engineer agent after the test plan is approved.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-tests\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[81,82,83,84,28,85,86,87,88,89,90,91,92,93,94,95,96,32,97,27],"write tests","write","tests","testing","test","project conventions","test plan","Bash","plan","quality","xunit","read","edit","coverage","engineer","mutation testing","mutation",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":42},"01M6KWEF2XQ00C1Y6QCK7YHZ1H","write-documentation","Structured documentation writing workflow for HypermediaEngine. Writes or updates README.md files at the repo root and in each project directory (src\u002F, tests\u002F, samples\u002F, etc.) based on current implementation, ADRs, and architecture decisions.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-documentation\u002FSKILL.md",[],[105,82,106,107,108,109,25,88,110,111,112,113,92,93,114,32,83,115,116,27],"documentation","write documentation","writing","directory","workflow","src","repo","decisions","README","files","updates","at",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":42},"01M6KWEBDXTXAVPQ3BHS3YYYNT","write-adr","Writes a numbered Architecture Decision Record (ADR) for a significant architectural choice in the HypermediaEngine project. Invoked by the software-architect agent whenever a consequential design decision is made or ratified. Saves the ADR to docs\u002Farchitecture\u002Fdecisions\u002F.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-adr\u002FSKILL.md",[],[124,82,125,28,126,25,37,127,128,129,112,92,130,131,32,31,132,27,133],"adr","write adr","docs","decision","choice","grep","architecture decision record","record","opus","architecture decision",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":144,"publishedAt":42},"01M6KWE76TM3QHGQ08PEB3KY6D","tunit-playwright-ui-testing","Comprehensive guidance for writing coded end-to-end UI tests in C# using TUnit.Playwright. Tests inherit from PageTest — the base class manages all browser lifecycle. Covers NuGet setup, PageTest inheritance, Page Object Model, browser configuration, parallelism limiting, and CI integration. Based on the official TUnit docs at https:\u002F\u002Ftunit.dev\u002Fdocs\u002Fexamples\u002Fplaywright.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftunit-playwright-ui-testing\u002FSKILL.md",[140,141],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[84,145,146,147,148,149,150,107,151,152,153,154,155,156,157,158,83,159,160,27],"playwright","ui","playwright ui testing","ui testing","tunit","tunit playwright ui testing","official","dev","examples","ci","lifecycle","model","page","inheritance","end","object",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":170,"publishedAt":42},"01M6KWE44A738GDK65QS02XJBG","triage","Task classification, decomposition, dependency mapping, and routing skill. Invoked by the triage-agent to break any user request into discrete, independently-routable work items with assigned priorities and agent chains.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage\u002FSKILL.md",[167],{"categoryNo":168,"categoryName":169,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发",[163,171,172,173,174,175,176,177,178,179,180,181,182,183],"routing","classification","work","user","dependency","task","priorities","decomposition","user request","mapping","with","break","request",{"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":194,"publishedAt":42},"01M6KWDZ3W9ZKPR7FTTTSX8H2K","system-design","Expert system design skill. Use PROACTIVELY to design systems, review architectures, and assist software engineers in learning design principles and implementing them in the code with design patterns.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsystem-design\u002FSKILL.md",[190,193],{"categoryNo":191,"categoryName":192,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},[28,195,196,197,198,199,200,129,92,36,201,202,203,204,205,31,206,207,181,208],"system","system design","web","design systems","learning","haiku","design patterns","design principles","expert","patterns","systems","architectures","principles","implementing"]