[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KW34R72F0AFCKS1SFVP368":3,"skill-same:01M6KW34R72F0AFCKS1SFVP368":72},{"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":28,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6KW34R72F0AFCKS1SFVP368","architecture-design",null,"Structured architectural design skill for the HypermediaEngine project. Use when translating requirements into architectural decisions, producing component designs, or documenting architectural trade-offs. Invoked by the software-architect agent to apply a consistent, systematic design process.","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-design\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"architecture","architecture design","design","trade","apply","trade-offs","for","software","systematic","requirements","project","structured","use","process","decisions","architect","component","2026-11-10 10:12:30",false,"---\nname: architecture-design\ndescription: Structured architectural design skill for the HypermediaEngine project. Use when translating requirements into architectural decisions, producing component designs, or documenting architectural trade-offs. Invoked by the software-architect agent to apply a consistent, systematic design process.\n---\n\n# Architecture Design\n\nYou are executing the `architecture-design` skill on behalf of the software-architect agent. Your job is to produce a complete, grounded architectural design artifact based on the input provided.\n\n## Input\n\nThe calling agent will pass one of:\n- A set of analyzed requirements (from requirement-analyst output)\n- A description of a feature or subsystem to design\n- A specific architectural question or decision to resolve\n\n## Process\n\n### Step 1 — Explore the Codebase\n\nBefore designing anything, ground yourself in the existing architecture:\n\n1. Use **Glob** to discover the current project structure\n2. Use **Read** on key files: middleware pipeline, DI registration, filter definitions, base types\n3. Use **Grep** to find established patterns: `{ data, error }` return shape usage, middleware chain wiring, existing filter implementations\n4. Identify what already exists that the new design must integrate with or extend\n\n### Step 2 — Identify Architectural Constraints\n\nExtract constraints from the project conventions:\n- Return shape must always be `{ data, error }`\n- Explicit type declarations with target-typed new or collection expressions\n- Async disposal over sync disposal\n- No stack traces exposed to clients\n- Logger module, not console output\n- Must fit within: Middlewares, Dependency Injection, Endpoint Filters \u002F Result Filters\n\n### Step 3 — Select Patterns\n\nChoose architectural patterns appropriate to the requirements:\n- **Middleware pipeline** — for cross-cutting concerns (auth, logging, error handling, transformation)\n- **Endpoint Filters** — for per-endpoint request\u002Fresponse interception\n- **Result Filters** — for transforming or enriching responses before they leave the pipeline\n- **Repository pattern** — for data access abstraction\n- **CQRS** — for separating read and write models when complexity warrants it\n- **DI-registered services** — for stateless, reusable business logic components\n\nJustify each pattern selection explicitly. Reject patterns that add complexity without a concrete benefit.\n\n### Step 4 — Produce the Design\n\nStructure your output as follows:\n\n---\n\n#### Architecture Overview\nHigh-level description of the proposed design in 3–5 sentences. State what the design achieves and how it fits into the existing system.\n\n#### Component Breakdown\nFor each major component:\n- **Name**: The component or class name\n- **Responsibility**: Single, precise statement of what it does\n- **Interface**: Key public surface (method signatures or contracts)\n- **DI Registration**: Lifetime (Singleton \u002F Scoped \u002F Transient) and registration approach\n- **Dependencies**: What it depends on and how those are injected\n\n#### Data Flow\nStep-by-step description of how a request moves through the system:\n1. Entry point (endpoint \u002F middleware invocation)\n2. Filter \u002F middleware chain steps in order\n3. Core logic execution\n4. Response construction using `{ data, error }` shape\n5. Exit point\n\nInclude error paths: what happens when a step fails, and how errors propagate without exposing stack traces.\n\n#### Key Decisions\nFor each significant design choice, document:\n- **Decision**: What was chosen\n- **Rationale**: Why this option over alternatives\n- **Trade-off**: What is given up\n\n#### Risks and Mitigations\nFor each identified risk:\n- **Risk**: Specific concern (not vague — name the failure mode)\n- **Likelihood**: Low \u002F Medium \u002F High given this system's context\n- **Mitigation**: Concrete design or implementation measure that addresses it\n\n#### Implementation Guidance\nOrdered list of implementation steps for the SoftwareEngineer agent, each referencing the relevant project conventions. Include:\n- File\u002Fclass creation order (dependency-first)\n- DI registration location and approach\n- Test strategy: what to unit test, what to integration test, mutation test coverage targets\n\n---\n\n### Step 5 — Validate Against the Framework\n\nBefore returning the design, verify:\n- [ ] Every component is reachable via DI — no `new` for services\n- [ ] All public response types use `{ data, error }` shape\n- [ ] No synchronous disposal of disposable resources\n- [ ] No stack trace exposure in error paths\n- [ ] Design is testable — no hidden static dependencies or global state\n- [ ] Mutation testing is viable — logic is isolated enough to be mutated and caught by tests\n\nIf any check fails, revise the relevant component before returning.\n\n## Output\n\nReturn the complete design artifact from Step 4, preceded by a one-line summary:\n\n> **Design for**: [feature\u002Fsubsystem name] — [one sentence on the core architectural approach]\n","# Architecture Design\n\nYou are executing the `architecture-design` skill on behalf of the software-architect agent. Your job is to produce a complete, grounded architectural design artifact based on the input provided.\n\n## Input\n\nThe calling agent will pass one of:\n- A set of analyzed requirements (from requirement-analyst output)\n- A description of a feature or subsystem to design\n- A specific architectural question or decision to resolve\n\n## Process\n\n### Step 1 — Explore the Codebase\n\nBefore designing anything, ground yourself in the existing architecture:\n\n1. Use **Glob** to discover the current project structure\n2. Use **Read** on key files: middleware pipeline, DI registration, filter definitions, base types\n3. Use **Grep** to find established patterns: `{ data, error }` return shape usage, middleware chain wiring, existing filter implementations\n4. Identify what already exists that the new design must integrate with or extend\n\n### Step 2 — Identify Architectural Constraints\n\nExtract constraints from the project conventions:\n- Return shape must always be `{ data, error }`\n- Explicit type declarations with target-typed new or collection expressions\n- Async disposal over sync disposal\n- No stack traces exposed to clients\n- Logger module, not console output\n- Must fit within: Middlewares, Dependency Injection, Endpoint Filters \u002F Result Filters\n\n### Step 3 — Select Patterns\n\nChoose architectural patterns appropriate to the requirements:\n- **Middleware pipeline** — for cross-cutting concerns (auth, logging, error handling, transformation)\n- **Endpoint Filters** — for per-endpoint request\u002Fresponse interception\n- **Result Filters** — for transforming or enriching responses before they leave the pipeline\n- **Repository pattern** — for data access abstraction\n- **CQRS** — for separating read and write models when complexity warrants it\n- **DI-registered services** — for stateless, reusable business logic components\n\nJustify each pattern selection explicitly. Reject patterns that add complexity without a concrete benefit.\n\n### Step 4 — Produce the Design\n\nStructure your output as follows:\n\n---\n\n#### Architecture Overview\nHigh-level description of the proposed design in 3–5 sentences. State what the design achieves and how it fits into the existing system.\n\n#### Component Breakdown\nFor each major component:\n- **Name**: The component or class name\n- **Responsibility**: Single, precise statement of what it does\n- **Interface**: Key public surface (method signatures or contracts)\n- **DI Registration**: Lifetime (Singleton \u002F Scoped \u002F Transient) and registration approach\n- **Dependencies**: What it depends on and how those are injected\n\n#### Data Flow\nStep-by-step description of how a request moves through the system:\n1. Entry point (endpoint \u002F middleware invocation)\n2. Filter \u002F middleware chain steps in order\n3. Core logic execution\n4. Response construction using `{ data, error }` shape\n5. Exit point\n\nInclude error paths: what happens when a step fails, and how errors propagate without exposing stack traces.\n\n#### Key Decisions\nFor each significant design choice, document:\n- **Decision**: What was chosen\n- **Rationale**: Why this option over alternatives\n- **Trade-off**: What is given up\n\n#### Risks and Mitigations\nFor each identified risk:\n- **Risk**: Specific concern (not vague — name the failure mode)\n- **Likelihood**: Low \u002F Medium \u002F High given this system's context\n- **Mitigation**: Concrete design or implementation measure that addresses it\n\n#### Implementation Guidance\nOrdered list of implementation steps for the SoftwareEngineer agent, each referencing the relevant project conventions. Include:\n- File\u002Fclass creation order (dependency-first)\n- DI registration location and approach\n- Test strategy: what to unit test, what to integration test, mutation test coverage targets\n\n---\n\n### Step 5 — Validate Against the Framework\n\nBefore returning the design, verify:\n- [ ] Every component is reachable via DI — no `new` for services\n- [ ] All public response types use `{ data, error }` shape\n- [ ] No synchronous disposal of disposable resources\n- [ ] No stack trace exposure in error paths\n- [ ] Design is testable — no hidden static dependencies or global state\n- [ ] Mutation testing is viable — logic is isolated enough to be mutated and caught by tests\n\nIf any check fails, revise the relevant component before returning.\n\n## Output\n\nReturn the complete design artifact from Step 4, preceded by a one-line summary:\n\n> **Design for**: [feature\u002Fsubsystem name] — [one sentence on the core architectural approach]\n",{"name":5,"description":7},"main","00b2c68281930728ee390bb16cec32b88d2caac7",".claude\u002Fskills\u002Farchitecture-design","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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add rafsanulhasan\u002FHypermediaEngine --skill architecture-design",{"tool":64,"command":65},"bunx","bunx skills add rafsanulhasan\u002FHypermediaEngine --skill architecture-design",{"tool":67,"command":68},"pnpm","pnpm dlx skills add rafsanulhasan\u002FHypermediaEngine --skill architecture-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Farchitecture-design\u002FSKILL.md",true,[],[73,100,118,135,160,183],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":82,"publishedAt":46},"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",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[83,84,85,86,31,87,88,89,90,91,92,93,94,95,96,97,98,39,99,35],"write tests","write","tests","testing","test","project conventions","test plan","Bash","plan","quality","xunit","read","edit","coverage","engineer","mutation testing","mutation",{"skillNo":101,"name":102,"nameZh":6,"description":103,"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":46},"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",[],[107,84,108,109,110,111,29,90,112,113,43,114,94,95,115,39,85,116,117,35],"documentation","write documentation","writing","directory","workflow","src","repo","README","files","updates","at",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":46},"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",[],[125,84,126,31,127,29,44,128,129,130,43,94,131,132,39,36,133,35,134],"adr","write adr","docs","decision","choice","grep","architecture decision record","record","opus","architecture decision",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":143,"publishedAt":46},"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",[141,142],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[86,144,145,146,147,148,149,109,150,151,152,153,154,155,156,157,85,158,159,35],"playwright","ui","playwright ui testing","ui testing","tunit","tunit playwright ui testing","official","dev","examples","ci","lifecycle","model","page","inheritance","end","object",{"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":169,"publishedAt":46},"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",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[162,170,171,172,173,174,175,176,177,178,179,180,181,182],"routing","classification","work","user","dependency","task","priorities","decomposition","user request","mapping","with","break","request",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":191,"publishedAt":46},"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",[189,190],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[31,192,193,194,195,196,197,130,94,41,198,199,200,201,202,36,203,204,180,205],"system","system design","web","design systems","learning","haiku","design patterns","design principles","expert","patterns","systems","architectures","principles","implementing"]