[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KWAN5V17E8CJSGR63WBF1E":3,"skill-same:01M6KWAN5V17E8CJSGR63WBF1E":134},{"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},"01M6KWAN5V17E8CJSGR63WBF1E","csharp-unit-testing",null,"Comprehensive guidance for writing C# unit tests using TUnit, TUnit.Mocks, Bogus, and TUnit.Assertions.Should with project conventions","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.github\u002Fskills\u002Fcsharp-unit-testing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"csharp unit testing","csharp","unit testing","testing","unit","tests","mocks","assertions","for","C#","with","tunit","project","conventions","guidance","project conventions","unit tests","writing","2026-11-10 10:12:30",false,"---\nname: csharp-unit-testing\ndescription: Comprehensive guidance for writing C# unit tests using TUnit, TUnit.Mocks, Bogus, and TUnit.Assertions.Should with project conventions\n---\n\n# csharp-unit-testing\n\nThis skill encodes best practices for writing C# unit tests in the HypermediaEngine project. It guides test implementation using a standardized stack: **TUnit** for the test framework, **TUnit.Mocks** for mocking, **Bogus** for test data generation, and **TUnit.Assertions.Should** for powerful assertions. It also reinforces project conventions like the `{ data, error }` return shape and Assert.Multiple() failure collection.\n\n---\n\n## Phase 0 — Context Load (silent)\n\n1. Read `.claude\u002FCLAUDE.md` and `.claude\u002Frules\u002Ftesting.md`\n2. Invoke `Skill(\"manage-memory\", args: \"sqa-engineer\")` to load persistent memory\n3. Note the project conventions:\n   - All API responses use `{ data, error }` shape\n   - Test framework: TUnit\n   - Mocking: TUnit.Mocks\n   - Test data: Bogus\n   - Assertions: TUnit.Assertions.Should\n\n---\n\n## Phase 1 — C# Unit Testing Conventions\n\n### Testing Framework: TUnit\n\nTUnit is the project's testing framework. Use it for:\n- Creating test classes (mark with `[TestClass]`)\n- Defining test methods (mark with `[Test]`)\n- Test organization and discovery\n\n**Why TUnit:** Lightweight, modern, integrates well with .NET 6+, and aligns with the HypermediaEngine architecture.\n\n### Mocking Framework: TUnit.Mocks\n\nTUnit.Mocks handles mock creation and behavior configuration. Always use it when a unit test needs to isolate the system under test (SUT) from its dependencies.\n\n**Pattern 1: Create a mock**\n\n[`templates\u002Fmock-create.md`](templates\u002Fmock-create.md)\n\n**Pattern 2: Configure return behavior**\n\n[`templates\u002Fmock-configure.md`](templates\u002Fmock-configure.md)\n\n**Pattern 3: Verify invocation**\n\n[`templates\u002Fmock-verify.md`](templates\u002Fmock-verify.md)\n\n**Pattern 4: Argument matching**\n\n[`templates\u002Fmock-argument-matching.md`](templates\u002Fmock-argument-matching.md)\n\n**Why TUnit.Mocks:** Zero ceremony — the mock IS the interface. Setup and verification are expressed as plain method calls, not lambda expressions.\n\n### Test Data Generation: Bogus\n\nBogus generates realistic test data. Always use it instead of hardcoded test data, especially for complex objects.\n\n**Pattern 1: Create a Faker instance**\n\n[`templates\u002Fbogus-test-data.md`](templates\u002Fbogus-test-data.md)\n\n**Pattern 2: Generate multiple instances**\n\n[`templates\u002Fbogus-generate-multiple.md`](templates\u002Fbogus-generate-multiple.md)\n\n**Why Bogus:** Produces realistic, varied test data; reduces brittleness from hardcoded values; makes tests easier to read and maintain.\n\n### Assertion Library: TUnit.Assertions.Should\n\nTUnit.Assertions.Should provides readable, fluent assertions. Always use it instead of basic `Assert` statements.\n\n**Pattern 1: Simple assertions**\n\n[`templates\u002Fassert-simple.md`](templates\u002Fassert-simple.md)\n\n**Pattern 2: Collection assertions**\n\n[`templates\u002Fassert-collection.md`](templates\u002Fassert-collection.md)\n\nNote: `.Any(predicate)` and `.All(predicate)` are hand-written in TUnit.Assertions.Should and take a plain `Func\u003CTItem, bool>` — not nested `.Should()` chains.\n\n**Pattern 3: Exception assertions (Act + Assert merged)**\n\nWhen asserting that a method call throws an exception, assign the call to a lambda and assert on it. This merges Act and Assert into one focused block.\n\n**Async exception:**\n\n[`templates\u002Fassert-async-exception.md`](templates\u002Fassert-async-exception.md)\n\n**Sync exception:**\n\n[`templates\u002Fassert-sync-exception.md`](templates\u002Fassert-sync-exception.md)\n\n**Critical rule:** Always use TUnit.Assertions.Should's `.Should().Throw\u003C>()` — this works for both `Action` (sync) and `Func\u003CTask>` (async) delegates. Never use `.ThrowAsync\u003C>()` (it does not exist in TUnit.Assertions.Should) and never use try\u002Fcatch.\n\n**Note:** To assert exception messages, use `Assert.That()` — TUnit.Assertions.Should does not expose `.WithMessage()` on exception assertions.\n\n**Pattern 4: And\u002FOr chaining**\n\n[`templates\u002Fassert-chaining.md`](templates\u002Fassert-chaining.md)\n\nNote: Do not mix `.And` and `.Or` in the same chain — TUnit will throw `MixedAndOrAssertionsException`.\n\n**Pattern 5: Justification**\n\n```csharp\nawait score.Should().BeGreaterThan(70).Because(\"passing grade is required\");\n```\n\n**Why TUnit.Assertions.Should:** Reads like English, provides rich failure messages, fluent syntax integrates seamlessly with TUnit.\n\n### Assert.Multiple: Collect All Failures\n\nAlways wrap multiple assertions in `Assert.Multiple()` to collect all failures before reporting. This is critical for debugging — you see all problems at once instead of fixing them one-by-one.\n\n[`templates\u002Fassert-multiple.md`](templates\u002Fassert-multiple.md)\n\nIf any assertion fails, the block collects all failures and reports them together. This saves debugging time.\n\n**Why Assert.Multiple():** Avoids stopping at the first failure; lets you see the full picture of what went wrong in a single test run. Native to TUnit assertion framework.\n\n### The `{ data, error }` Return Shape\n\nAll HypermediaEngine API responses use a consistent shape:\n```csharp\npublic record ApiResponse\u003CT>(T? Data, string? Error);\n```\n\nAlways assert BOTH `Data` and `Error` fields. Never verify only one side. This ensures the response shape is correct.\n\n[`templates\u002Fdata-error-shape.md`](templates\u002Fdata-error-shape.md)\n\n### Test Naming Convention\n\nUse descriptive test names that explain the scenario and expected outcome using the `Method_Scenario_Outcome` shape:\n\n[`templates\u002Ftest-naming.md`](templates\u002Ftest-naming.md)\n\n### Test Structure: Arrange, Act, Assert (AAA)\n\nEvery test follows the **Arrange, Act, Assert** pattern to keep test logic clear and maintainable. This structure separates concerns and makes tests easier to understand at a glance.\n\n**Arrange** — Set up dependencies, test data, and the system under test (SUT). Configure mocks, build test objects with Bogus, and prepare any preconditions needed.\n\n**Act** — Call the method under test exactly once. This is a single line of code that invokes the SUT with the arranged inputs. Any logic here should belong in production code, not the test.\n\n**Assert** — Verify that the result matches expectations using TUnit.Assertions.Should. Use `Assert.Multiple()` to collect all failures at once.\n\n[`templates\u002Ftest-structure.md`](templates\u002Ftest-structure.md)\n\n**Critical rule: one Act per test.** If a test needs to call the SUT more than once, split it into separate tests. Each test should verify a single behavior path.\n\n---\n\n## Phase 2 — Complete Example: Middleware Test\n\nHere is a complete example testing a middleware component using all conventions together:\n\n[`templates\u002Fmiddleware-unit-test.md`](templates\u002Fmiddleware-unit-test.md)\n\n---\n\n## Phase 3 — Key Takeaways\n\nWhen writing C# unit tests for HypermediaEngine:\n\n1. **Use TUnit** — it's the project's test framework\n2. **Mock with TUnit.Mocks** — fluent, intuitive, and integrated with TUnit\n3. **Generate test data with Bogus** — realistic, varied, maintainable\n4. **Assert with TUnit.Assertions.Should** — readable, fluent, powerful\n5. **Collect failures with Assert.Multiple()** — see all problems at once\n6. **Always assert both Data and Error** — the `{ data, error }` shape is mandatory\n7. **Name tests clearly** — explain scenario and expected outcome\n8. **Test behavior, not implementation** — tests must survive refactoring\n\nFollow these patterns consistently across all test suites.\n","# csharp-unit-testing\n\nThis skill encodes best practices for writing C# unit tests in the HypermediaEngine project. It guides test implementation using a standardized stack: **TUnit** for the test framework, **TUnit.Mocks** for mocking, **Bogus** for test data generation, and **TUnit.Assertions.Should** for powerful assertions. It also reinforces project conventions like the `{ data, error }` return shape and Assert.Multiple() failure collection.\n\n---\n\n## Phase 0 — Context Load (silent)\n\n1. Read `.claude\u002FCLAUDE.md` and `.claude\u002Frules\u002Ftesting.md`\n2. Invoke `Skill(\"manage-memory\", args: \"sqa-engineer\")` to load persistent memory\n3. Note the project conventions:\n   - All API responses use `{ data, error }` shape\n   - Test framework: TUnit\n   - Mocking: TUnit.Mocks\n   - Test data: Bogus\n   - Assertions: TUnit.Assertions.Should\n\n---\n\n## Phase 1 — C# Unit Testing Conventions\n\n### Testing Framework: TUnit\n\nTUnit is the project's testing framework. Use it for:\n- Creating test classes (mark with `[TestClass]`)\n- Defining test methods (mark with `[Test]`)\n- Test organization and discovery\n\n**Why TUnit:** Lightweight, modern, integrates well with .NET 6+, and aligns with the HypermediaEngine architecture.\n\n### Mocking Framework: TUnit.Mocks\n\nTUnit.Mocks handles mock creation and behavior configuration. Always use it when a unit test needs to isolate the system under test (SUT) from its dependencies.\n\n**Pattern 1: Create a mock**\n\n[`templates\u002Fmock-create.md`](templates\u002Fmock-create.md)\n\n**Pattern 2: Configure return behavior**\n\n[`templates\u002Fmock-configure.md`](templates\u002Fmock-configure.md)\n\n**Pattern 3: Verify invocation**\n\n[`templates\u002Fmock-verify.md`](templates\u002Fmock-verify.md)\n\n**Pattern 4: Argument matching**\n\n[`templates\u002Fmock-argument-matching.md`](templates\u002Fmock-argument-matching.md)\n\n**Why TUnit.Mocks:** Zero ceremony — the mock IS the interface. Setup and verification are expressed as plain method calls, not lambda expressions.\n\n### Test Data Generation: Bogus\n\nBogus generates realistic test data. Always use it instead of hardcoded test data, especially for complex objects.\n\n**Pattern 1: Create a Faker instance**\n\n[`templates\u002Fbogus-test-data.md`](templates\u002Fbogus-test-data.md)\n\n**Pattern 2: Generate multiple instances**\n\n[`templates\u002Fbogus-generate-multiple.md`](templates\u002Fbogus-generate-multiple.md)\n\n**Why Bogus:** Produces realistic, varied test data; reduces brittleness from hardcoded values; makes tests easier to read and maintain.\n\n### Assertion Library: TUnit.Assertions.Should\n\nTUnit.Assertions.Should provides readable, fluent assertions. Always use it instead of basic `Assert` statements.\n\n**Pattern 1: Simple assertions**\n\n[`templates\u002Fassert-simple.md`](templates\u002Fassert-simple.md)\n\n**Pattern 2: Collection assertions**\n\n[`templates\u002Fassert-collection.md`](templates\u002Fassert-collection.md)\n\nNote: `.Any(predicate)` and `.All(predicate)` are hand-written in TUnit.Assertions.Should and take a plain `Func\u003CTItem, bool>` — not nested `.Should()` chains.\n\n**Pattern 3: Exception assertions (Act + Assert merged)**\n\nWhen asserting that a method call throws an exception, assign the call to a lambda and assert on it. This merges Act and Assert into one focused block.\n\n**Async exception:**\n\n[`templates\u002Fassert-async-exception.md`](templates\u002Fassert-async-exception.md)\n\n**Sync exception:**\n\n[`templates\u002Fassert-sync-exception.md`](templates\u002Fassert-sync-exception.md)\n\n**Critical rule:** Always use TUnit.Assertions.Should's `.Should().Throw\u003C>()` — this works for both `Action` (sync) and `Func\u003CTask>` (async) delegates. Never use `.ThrowAsync\u003C>()` (it does not exist in TUnit.Assertions.Should) and never use try\u002Fcatch.\n\n**Note:** To assert exception messages, use `Assert.That()` — TUnit.Assertions.Should does not expose `.WithMessage()` on exception assertions.\n\n**Pattern 4: And\u002FOr chaining**\n\n[`templates\u002Fassert-chaining.md`](templates\u002Fassert-chaining.md)\n\nNote: Do not mix `.And` and `.Or` in the same chain — TUnit will throw `MixedAndOrAssertionsException`.\n\n**Pattern 5: Justification**\n\n```csharp\nawait score.Should().BeGreaterThan(70).Because(\"passing grade is required\");\n```\n\n**Why TUnit.Assertions.Should:** Reads like English, provides rich failure messages, fluent syntax integrates seamlessly with TUnit.\n\n### Assert.Multiple: Collect All Failures\n\nAlways wrap multiple assertions in `Assert.Multiple()` to collect all failures before reporting. This is critical for debugging — you see all problems at once instead of fixing them one-by-one.\n\n[`templates\u002Fassert-multiple.md`](templates\u002Fassert-multiple.md)\n\nIf any assertion fails, the block collects all failures and reports them together. This saves debugging time.\n\n**Why Assert.Multiple():** Avoids stopping at the first failure; lets you see the full picture of what went wrong in a single test run. Native to TUnit assertion framework.\n\n### The `{ data, error }` Return Shape\n\nAll HypermediaEngine API responses use a consistent shape:\n```csharp\npublic record ApiResponse\u003CT>(T? Data, string? Error);\n```\n\nAlways assert BOTH `Data` and `Error` fields. Never verify only one side. This ensures the response shape is correct.\n\n[`templates\u002Fdata-error-shape.md`](templates\u002Fdata-error-shape.md)\n\n### Test Naming Convention\n\nUse descriptive test names that explain the scenario and expected outcome using the `Method_Scenario_Outcome` shape:\n\n[`templates\u002Ftest-naming.md`](templates\u002Ftest-naming.md)\n\n### Test Structure: Arrange, Act, Assert (AAA)\n\nEvery test follows the **Arrange, Act, Assert** pattern to keep test logic clear and maintainable. This structure separates concerns and makes tests easier to understand at a glance.\n\n**Arrange** — Set up dependencies, test data, and the system under test (SUT). Configure mocks, build test objects with Bogus, and prepare any preconditions needed.\n\n**Act** — Call the method under test exactly once. This is a single line of code that invokes the SUT with the arranged inputs. Any logic here should belong in production code, not the test.\n\n**Assert** — Verify that the result matches expectations using TUnit.Assertions.Should. Use `Assert.Multiple()` to collect all failures at once.\n\n[`templates\u002Ftest-structure.md`](templates\u002Ftest-structure.md)\n\n**Critical rule: one Act per test.** If a test needs to call the SUT more than once, split it into separate tests. Each test should verify a single behavior path.\n\n---\n\n## Phase 2 — Complete Example: Middleware Test\n\nHere is a complete example testing a middleware component using all conventions together:\n\n[`templates\u002Fmiddleware-unit-test.md`](templates\u002Fmiddleware-unit-test.md)\n\n---\n\n## Phase 3 — Key Takeaways\n\nWhen writing C# unit tests for HypermediaEngine:\n\n1. **Use TUnit** — it's the project's test framework\n2. **Mock with TUnit.Mocks** — fluent, intuitive, and integrated with TUnit\n3. **Generate test data with Bogus** — realistic, varied, maintainable\n4. **Assert with TUnit.Assertions.Should** — readable, fluent, powerful\n5. **Collect failures with Assert.Multiple()** — see all problems at once\n6. **Always assert both Data and Error** — the `{ data, error }` shape is mandatory\n7. **Name tests clearly** — explain scenario and expected outcome\n8. **Test behavior, not implementation** — tests must survive refactoring\n\nFollow these patterns consistently across all test suites.\n",{"name":5,"description":7},"main","00b2c68281930728ee390bb16cec32b88d2caac7",".github\u002Fskills\u002Fcsharp-unit-testing","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 csharp-unit-testing",{"tool":60,"command":61},"bunx","bunx skills add rafsanulhasan\u002FHypermediaEngine --skill csharp-unit-testing",{"tool":63,"command":64},"pnpm","pnpm dlx skills add rafsanulhasan\u002FHypermediaEngine --skill csharp-unit-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002FSKILL.md",true,[68,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"templates\u002Fassert-async-exception.md","REFERENCE","参考文档",272,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fassert-async-exception.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"templates\u002Fassert-chaining.md",195,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fassert-chaining.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"templates\u002Fassert-collection.md",207,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fassert-collection.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"templates\u002Fassert-multiple.md",349,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fassert-multiple.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"templates\u002Fassert-simple.md",160,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fassert-simple.md",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"templates\u002Fassert-sync-exception.md",269,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fassert-sync-exception.md",{"path":95,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":96,"sourceHtmlUrl":97},"templates\u002Fbogus-generate-multiple.md",83,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fbogus-generate-multiple.md",{"path":99,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":100,"sourceHtmlUrl":101},"templates\u002Fbogus-test-data.md",251,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fbogus-test-data.md",{"path":103,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":104,"sourceHtmlUrl":105},"templates\u002Fdata-error-shape.md",604,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fdata-error-shape.md",{"path":107,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":108,"sourceHtmlUrl":109},"templates\u002Fmiddleware-unit-test.md",2147,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fmiddleware-unit-test.md",{"path":111,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":112,"sourceHtmlUrl":113},"templates\u002Fmock-argument-matching.md",190,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fmock-argument-matching.md",{"path":115,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":116,"sourceHtmlUrl":117},"templates\u002Fmock-configure.md",239,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fmock-configure.md",{"path":119,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":120,"sourceHtmlUrl":121},"templates\u002Fmock-create.md",173,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fmock-create.md",{"path":123,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":124,"sourceHtmlUrl":125},"templates\u002Fmock-verify.md",313,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Fmock-verify.md",{"path":127,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":128,"sourceHtmlUrl":129},"templates\u002Ftest-naming.md",208,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Ftest-naming.md",{"path":131,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":132,"sourceHtmlUrl":133},"templates\u002Ftest-structure.md",869,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-unit-testing\u002Ftemplates\u002Ftest-structure.md",[135,158,177,196,224,246],{"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":142,"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",[141],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[143,144,29,27,145,146,39,147,148,149,150,151,152,153,154,155,156,36,157,32],"write tests","write","design","test","test plan","Bash","plan","quality","xunit","read","edit","coverage","engineer","mutation testing","mutation",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"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",[],[165,144,166,41,167,168,169,148,170,171,172,173,152,153,174,36,29,175,176,32],"documentation","write documentation","directory","workflow","architecture","src","repo","decisions","README","files","updates","at",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"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",[],[184,144,185,145,186,169,187,188,189,190,172,152,191,192,36,193,194,32,195],"adr","write adr","docs","architect","decision","choice","grep","architecture decision record","record","software","opus","architecture decision",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":208,"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",[202,203],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":204,"categoryName":205,"taxonomyType":206,"taxonomyTypeDesc":207},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[27,209,210,211,212,35,213,41,214,215,216,217,218,219,220,221,29,222,223,32],"playwright","ui","playwright ui testing","ui testing","tunit playwright ui testing","official","dev","examples","ci","lifecycle","model","page","inheritance","end","object",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":228,"categories":229,"keywords":233,"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",[230],{"categoryNo":231,"categoryName":232,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[226,234,235,236,237,238,239,240,241,242,243,34,244,245],"routing","classification","work","user","dependency","task","priorities","decomposition","user request","mapping","break","request",{"skillNo":247,"name":248,"nameZh":6,"description":249,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":250,"categories":251,"keywords":256,"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",[252,255],{"categoryNo":253,"categoryName":254,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":204,"categoryName":205,"taxonomyType":206,"taxonomyTypeDesc":207},[145,257,258,259,260,261,262,190,152,263,264,265,266,267,268,193,269,270,34,271],"system","system design","web","design systems","learning","haiku","use","design patterns","design principles","expert","patterns","systems","architectures","principles","implementing"]