[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KWA82CC51B121N3G712ZS3":3,"skill-same:01M6KWA82CC51B121N3G712ZS3":160},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6KWA82CC51B121N3G712ZS3","csharp-integration-testing",null,"Comprehensive guidance for writing C# integration tests using TUnit, TestWebApplicationFactory, Testcontainers, Bogus, and TUnit.Assertions.Should — no mocks, real infrastructure","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-integration-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],"testing","csharp","integration","integration testing","csharp integration testing","writing","integration tests","infrastructure","guidance","tests","tunit","testcontainers","C#","for","assertions","mocks","2026-11-10 10:12:30",false,"---\nname: csharp-integration-testing\ndescription: Comprehensive guidance for writing C# integration tests using TUnit, TestWebApplicationFactory, Testcontainers, Bogus, and TUnit.Assertions.Should — no mocks, real infrastructure\n---\n\n# csharp-integration-testing\n\nThis skill encodes best practices for writing C# integration tests in the HypermediaEngine project. Integration tests exercise the system end-to-end through real infrastructure — they do not use mocks. The standardized stack is **TUnit** for the test framework, **TUnit's `TestWebApplicationFactory\u003CTEntryPoint>`** for ASP.NET Core hosting, **Testcontainers** for spinning up real databases, queues, caches, and other dependencies, **Bogus** for test data generation, and **TUnit.Assertions.Should** for assertions. Project conventions like the `{ data, error }` return shape and `Assert.Multiple()` failure collection still apply.\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   - Integration test host: TUnit.AspNet (`TestWebApplicationFactory\u003CTEntryPoint>`) — never plain `WebApplicationFactory`\n   - Infrastructure: Testcontainers (PostgreSQL, Redis, Kafka, etc.) — never mocks in integration tests\n   - Test data: Bogus\n   - Assertions: TUnit.Assertions.Should\n\n---\n\n## Phase 1 — Integration vs. Unit Tests\n\nBefore writing any integration test, confirm it belongs in the integration suite:\n\n| Concern | Unit test | Integration test |\n| --- | --- | --- |\n| Scope | One class, one method | HTTP request → middleware pipeline → DB → response |\n| Dependencies | Mocked with `TUnit.Mocks` | **Real**, started via Testcontainers |\n| Hosting | None — direct construction | `TestWebApplicationFactory\u003CProgram>` |\n| Cost | Microseconds | Seconds (container startup amortised across session) |\n| Failure signal | Logic regression | Wiring, configuration, contract, or schema regression |\n\n**Rule:** if a test would still pass with the database swapped for an in-memory dictionary, it is a unit test — write it in the unit suite using `csharp-unit-testing`. Integration tests must exercise the real wire.\n\n**No mocks in integration tests.** If you find yourself reaching for `IFoo.Mock()` in an integration test, you are writing the wrong kind of test. Stop, decide whether the behaviour belongs in the unit suite or whether the dependency needs a Testcontainer.\n\n---\n\n## Phase 2 — C# Integration Testing Conventions\n\n### Test Hosting: TestWebApplicationFactory\n\nUse `TUnit.AspNet`'s `TestWebApplicationFactory\u003CTEntryPoint>` rather than the vanilla ASP.NET `WebApplicationFactory`. It gives you trace correlation, per-test logging, and `TestContext.Current` access for free.\n\n**Pattern 1: Define the factory once per project**\n\n[`templates\u002Ffactory-definition.md`](templates\u002Ffactory-definition.md)\n\n**Pattern 2: Define a base class so every test inherits the factory**\n\n[`templates\u002Fbase-class.md`](templates\u002Fbase-class.md)\n\n**Pattern 3: Per-test service overrides (use sparingly)**\n\n[`templates\u002Fconfigure-test-services.md`](templates\u002Fconfigure-test-services.md)\n\n**Why TestWebApplicationFactory:** It wires OpenTelemetry headers, captures HTTP exchanges, and routes server-side `ILogger` output to the originating test — without these, parallel test runs interleave logs and you cannot tell which test produced which line.\n\n### Real Infrastructure: Testcontainers\n\nTestcontainers spins up real Docker containers for the lifetime of the test session. **Never use mocks for the database, message broker, cache, or any other infrastructure** — that is the entire point of integration testing.\n\n**Pattern 1: Wrap a container as an `IAsyncInitializer` \u002F `IAsyncDisposable` fixture**\n\n[`templates\u002Fpostgres-fixture.md`](templates\u002Fpostgres-fixture.md)\n\n**Pattern 2: Inject the fixture into the factory with `[ClassDataSource]`**\n\n[`templates\u002Fclassdatasource-injection.md`](templates\u002Fclassdatasource-injection.md)\n\n`SharedType.PerTestSession` means the container starts once for the entire test run, not once per test class. Every test borrows the same instance.\n\n**Pattern 3: Multi-container topology with a shared Docker network**\n\n[`templates\u002Fmulti-container-topology.md`](templates\u002Fmulti-container-topology.md)\n\nTUnit resolves the dependency chain (network → kafka → factory) automatically — initialization runs in dependency order, disposal in reverse.\n\n**Pattern 4: Per-test isolation on shared infrastructure**\n\nBecause `SharedType.PerTestSession` reuses the same database across tests, parallel tests will collide unless each test owns its own slice of state. Use TUnit's `GetIsolatedName()` \u002F `GetIsolatedPrefix()` helpers from `WebApplicationTest`:\n\n[`templates\u002Fper-test-schema-isolation.md`](templates\u002Fper-test-schema-isolation.md)\n\n**Golden rule:** if a resource is shared, every test must address its own slice of it (schema, table prefix, queue name, cache prefix, blob path). Otherwise parallel tests will flake.\n\n**Why Testcontainers:** Mocks lie about what the database accepts; integration tests with the real engine catch broken migrations, missing indexes, dialect-specific SQL, contract violations between services, and serialization mismatches that mocks cannot see.\n\n### Lifecycle Hooks: `[Before]` and `[After]`\n\nTUnit's `[Before(scope)]` and `[After(scope)]` hooks replace NUnit's `[SetUp]`\u002F`[TearDown]` family. They are method attributes — async-first, no naming convention required.\n\n| Attribute | Scope | Runs | NUnit equivalent |\n|---|---|---|---|\n| `[Before(Test)]` | Per test | Before each test method | `[SetUp]` |\n| `[After(Test)]` | Per test | After each test method | `[TearDown]` |\n| `[Before(Class)]` | Per class | Once before all tests in the class | `[OneTimeSetUp]` |\n| `[After(Class)]` | Per class | Once after all tests in the class | `[OneTimeTearDown]` |\n| `[Before(Assembly)]` | Per assembly | Once for the whole assembly (static only) | `[SetUpFixture]` |\n| `[After(Assembly)]` | Per assembly | Once for the whole assembly (static only) | `[SetUpFixture]` teardown |\n\n**Pattern 1: Create and dispose a `TestWebApplicationFactory` at class scope**\n\n[`templates\u002Fbefore-after-factory.md`](templates\u002Fbefore-after-factory.md)\n\n**Pattern 2: Create and dispose a test container at class scope**\n\n[`templates\u002Fbefore-after-container.md`](templates\u002Fbefore-after-container.md)\n\n**Pattern 3: Inject resolved services in `[Before(Test)]`**\n\nAfter the factory and container are live at class scope, use `[Before(Test)]` to resolve per-test dependencies from the factory's DI container and create a fresh HTTP client per test:\n\n[`templates\u002Fbefore-after-service-injection.md`](templates\u002Fbefore-after-service-injection.md)\n\n**Pattern 4: Full explicit stack — container + factory + per-test injection**\n\nUse when you own the full lifecycle and are not inheriting from `WebApplicationTest\u003CT>`:\n\n[`templates\u002Fbefore-after-full-stack.md`](templates\u002Fbefore-after-full-stack.md)\n\n**Pattern 5: Assembly-wide shared resources (static hooks)**\n\nAssembly hooks must be `static` methods in a `static class`. Use them only for truly global resources that every test class in the assembly shares:\n\n[`templates\u002Fbefore-after-assembly.md`](templates\u002Fbefore-after-assembly.md)\n\n**When to use `[Before\u002FAfter]` vs. `[ClassDataSource]`**\n\n| Scenario | Prefer |\n|---|---|\n| Session-shared infrastructure (one container for all classes) | `[ClassDataSource\u003CT>(Shared = SharedType.PerTestSession)]` |\n| Class-owned infrastructure (container per test class) | `[Before(Class)]` \u002F `[After(Class)]` |\n| Per-test setup (client, schema, resolved services) | `[Before(Test)]` \u002F `[After(Test)]` |\n| Assembly-wide global resources | `[Before(Assembly)]` \u002F `[After(Assembly)]` (static) |\n\n**Disposal order rule:** always dispose in reverse construction order — if you created factory after container, dispose factory before container.\n\n### Aspire-Hosted Stacks\n\nIf the system under test is composed via .NET Aspire, prefer `TUnit.Aspire`'s `AspireFixture\u003CTAppHost>` — it builds the AppHost, boots every container, waits for health checks, and exposes typed HTTP clients for each resource.\n\n**Pattern: Direct fixture usage**\n\n[`templates\u002Faspire-fixture-direct.md`](templates\u002Faspire-fixture-direct.md)\n\n**Pattern: Customise the fixture**\n\n[`templates\u002Faspire-fixture-custom.md`](templates\u002Faspire-fixture-custom.md)\n\n**Why Aspire fixtures:** the AppHost already encodes the production topology — re-using it in tests removes drift between \"what we test\" and \"what we ship\".\n\n### Test Data Generation: Bogus\n\nBogus still applies. Hardcoded seed data hides bugs and makes integration tests brittle.\n\n[`templates\u002Fbogus-test-data.md`](templates\u002Fbogus-test-data.md)\n\nWhen seeding the database directly, generate full aggregates with Bogus and persist them through the production repository — never via raw SQL. Round-tripping through the real persistence layer is part of what you are validating.\n\n### Assertion Library: TUnit.Assertions.Should\n\nSame library, same patterns as unit tests. Quick reference for integration-flavoured cases:\n\n**Pattern 1: HTTP response assertions**\n\n[`templates\u002Fassert-http-response.md`](templates\u002Fassert-http-response.md)\n\n**Pattern 2: Deserialised body**\n\n[`templates\u002Fassert-deserialized-body.md`](templates\u002Fassert-deserialized-body.md)\n\n**Pattern 3: Side-effect verification**\n\nIntegration tests check observable side effects — never internal state.\n\n[`templates\u002Fassert-side-effects.md`](templates\u002Fassert-side-effects.md)\n\n**Pattern 4: Async exceptions** — same as unit tests\n\n[`templates\u002Fassert-async-exception.md`](templates\u002Fassert-async-exception.md)\n\nUse `.Should().Throw\u003C>()` for both `Action` and `Func\u003CTask>` — never `.ThrowAsync\u003C>()`, never try\u002Fcatch.\n\n### Assert.Multiple: Collect All Failures\n\nAlways wrap related assertions in `Assert.Multiple()`. In integration tests this matters even more — a single test exercises many layers, and you want to see *all* the things that broke at once instead of fixing them one by one across long container-startup cycles.\n\n[`templates\u002Fassert-multiple.md`](templates\u002Fassert-multiple.md)\n\n### The `{ data, error }` Return Shape\n\nEvery API response — including those reached via the HTTP pipeline — must be asserted on both `Data` and `Error`. No exceptions for integration tests.\n\n[`templates\u002Fdata-error-shape.md`](templates\u002Fdata-error-shape.md)\n\n### Test Naming Convention\n\nUse the same `Method_Scenario_Outcome` shape as unit tests, but the \"method\" is usually the HTTP verb + route:\n\n[`templates\u002Ftest-naming.md`](templates\u002Ftest-naming.md)\n\nIf the suite ties to a numbered AC, prefix the display name with the AC ID (`[AC-3] PostTodos_...`).\n\n### Test Structure: Arrange, Act, Assert (AAA)\n\nSame discipline as unit tests:\n\n- **Arrange** — seed any required state through the production repository (not raw SQL); generate request payloads with Bogus; build the HTTP client from the factory.\n- **Act** — issue **one** HTTP call (or one operation) per test.\n- **Assert** — verify the response, then verify the persisted side effect, then verify any emitted events.\n\n**One Act per test.** If you find yourself making two HTTP calls \"to set up state, then verify\", the first call is arrangement — split it into a separate test or do the seeding directly through a fixture helper.\n\n---\n\n## Phase 3 — Complete Example: Endpoint Integration Test\n\n[`templates\u002Fendpoint-integration-test.md`](templates\u002Fendpoint-integration-test.md)\n\n---\n\n## Phase 4 — Operational Concerns\n\n### Performance & Parallelism\n\n- Container startup is the dominant cost. Always use `SharedType.PerTestSession` for infrastructure fixtures.\n- TUnit runs tests in parallel by default. Pair `PerTestSession` containers with per-test isolation (`GetIsolatedName`, `GetIsolatedPrefix`) — never assume serial execution.\n- If a test must run alone, mark it `[NotInParallel]` — but treat that as a bug to fix, not a default.\n\n### CI\u002FCD\n\n- Integration tests require a running Docker daemon on the build agent.\n- Set `ASPIRE_ALLOW_UNSECURED_TRANSPORT=true` in CI when using `AspireFixture` without trusted certificates.\n- Increase `ResourceTimeout` to 2–5 minutes on shared CI runners.\n\n### Diagnostics\n\n- `WatchResourceLogs(\"apiservice\")` streams a container's logs into the test output — invaluable when a test fails and you need to know what the app saw.\n- `EnableHttpExchangeCapture = true` records every request\u002Fresponse pair the test issued — assert against `HttpCapture!.Last` when the response object alone is not enough.\n\n### What NOT to do\n\n- Do **not** seed test data with raw SQL when a repository exists — round-trip through the real code path.\n- Do **not** mock anything in an integration test. If you need a deterministic clock or a fake email sender, use `ConfigureTestServices` to replace it with a real test double, not a mock.\n- Do **not** share mutable state between tests via static fields — use TUnit's isolation helpers instead.\n- Do **not** skip `Assert.Multiple()` because \"the test only has two assertions\". The discipline is uniform.\n\n---\n\n## Phase 5 — Key Takeaways\n\nWhen writing C# integration tests for HypermediaEngine:\n\n1. **Host with `TestWebApplicationFactory\u003CProgram>`** — never the vanilla ASP.NET factory.\n2. **Use Testcontainers for real infrastructure** — Postgres, Redis, Kafka, all of it.\n3. **No mocks** — if you need one, the test belongs in the unit suite.\n4. **Share containers across the session, isolate state per test** — `PerTestSession` + `GetIsolatedName`.\n5. **Use Aspire fixtures** when the system is already composed with Aspire.\n6. **Generate test data with Bogus** — round-trip seeds through the production repository.\n7. **Assert with TUnit.Assertions.Should** — `.Should().Throw\u003C>()` for both sync and async.\n8. **Wrap related assertions in `Assert.Multiple()`** — see all failures from one container cycle.\n9. **Always assert both `Data` and `Error`** — the `{ data, error }` shape is mandatory end-to-end.\n10. **Verify side effects** — read the database, check emitted events, inspect captured exchanges.\n\nFollow these patterns consistently across all integration suites.\n","# csharp-integration-testing\n\nThis skill encodes best practices for writing C# integration tests in the HypermediaEngine project. Integration tests exercise the system end-to-end through real infrastructure — they do not use mocks. The standardized stack is **TUnit** for the test framework, **TUnit's `TestWebApplicationFactory\u003CTEntryPoint>`** for ASP.NET Core hosting, **Testcontainers** for spinning up real databases, queues, caches, and other dependencies, **Bogus** for test data generation, and **TUnit.Assertions.Should** for assertions. Project conventions like the `{ data, error }` return shape and `Assert.Multiple()` failure collection still apply.\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   - Integration test host: TUnit.AspNet (`TestWebApplicationFactory\u003CTEntryPoint>`) — never plain `WebApplicationFactory`\n   - Infrastructure: Testcontainers (PostgreSQL, Redis, Kafka, etc.) — never mocks in integration tests\n   - Test data: Bogus\n   - Assertions: TUnit.Assertions.Should\n\n---\n\n## Phase 1 — Integration vs. Unit Tests\n\nBefore writing any integration test, confirm it belongs in the integration suite:\n\n| Concern | Unit test | Integration test |\n| --- | --- | --- |\n| Scope | One class, one method | HTTP request → middleware pipeline → DB → response |\n| Dependencies | Mocked with `TUnit.Mocks` | **Real**, started via Testcontainers |\n| Hosting | None — direct construction | `TestWebApplicationFactory\u003CProgram>` |\n| Cost | Microseconds | Seconds (container startup amortised across session) |\n| Failure signal | Logic regression | Wiring, configuration, contract, or schema regression |\n\n**Rule:** if a test would still pass with the database swapped for an in-memory dictionary, it is a unit test — write it in the unit suite using `csharp-unit-testing`. Integration tests must exercise the real wire.\n\n**No mocks in integration tests.** If you find yourself reaching for `IFoo.Mock()` in an integration test, you are writing the wrong kind of test. Stop, decide whether the behaviour belongs in the unit suite or whether the dependency needs a Testcontainer.\n\n---\n\n## Phase 2 — C# Integration Testing Conventions\n\n### Test Hosting: TestWebApplicationFactory\n\nUse `TUnit.AspNet`'s `TestWebApplicationFactory\u003CTEntryPoint>` rather than the vanilla ASP.NET `WebApplicationFactory`. It gives you trace correlation, per-test logging, and `TestContext.Current` access for free.\n\n**Pattern 1: Define the factory once per project**\n\n[`templates\u002Ffactory-definition.md`](templates\u002Ffactory-definition.md)\n\n**Pattern 2: Define a base class so every test inherits the factory**\n\n[`templates\u002Fbase-class.md`](templates\u002Fbase-class.md)\n\n**Pattern 3: Per-test service overrides (use sparingly)**\n\n[`templates\u002Fconfigure-test-services.md`](templates\u002Fconfigure-test-services.md)\n\n**Why TestWebApplicationFactory:** It wires OpenTelemetry headers, captures HTTP exchanges, and routes server-side `ILogger` output to the originating test — without these, parallel test runs interleave logs and you cannot tell which test produced which line.\n\n### Real Infrastructure: Testcontainers\n\nTestcontainers spins up real Docker containers for the lifetime of the test session. **Never use mocks for the database, message broker, cache, or any other infrastructure** — that is the entire point of integration testing.\n\n**Pattern 1: Wrap a container as an `IAsyncInitializer` \u002F `IAsyncDisposable` fixture**\n\n[`templates\u002Fpostgres-fixture.md`](templates\u002Fpostgres-fixture.md)\n\n**Pattern 2: Inject the fixture into the factory with `[ClassDataSource]`**\n\n[`templates\u002Fclassdatasource-injection.md`](templates\u002Fclassdatasource-injection.md)\n\n`SharedType.PerTestSession` means the container starts once for the entire test run, not once per test class. Every test borrows the same instance.\n\n**Pattern 3: Multi-container topology with a shared Docker network**\n\n[`templates\u002Fmulti-container-topology.md`](templates\u002Fmulti-container-topology.md)\n\nTUnit resolves the dependency chain (network → kafka → factory) automatically — initialization runs in dependency order, disposal in reverse.\n\n**Pattern 4: Per-test isolation on shared infrastructure**\n\nBecause `SharedType.PerTestSession` reuses the same database across tests, parallel tests will collide unless each test owns its own slice of state. Use TUnit's `GetIsolatedName()` \u002F `GetIsolatedPrefix()` helpers from `WebApplicationTest`:\n\n[`templates\u002Fper-test-schema-isolation.md`](templates\u002Fper-test-schema-isolation.md)\n\n**Golden rule:** if a resource is shared, every test must address its own slice of it (schema, table prefix, queue name, cache prefix, blob path). Otherwise parallel tests will flake.\n\n**Why Testcontainers:** Mocks lie about what the database accepts; integration tests with the real engine catch broken migrations, missing indexes, dialect-specific SQL, contract violations between services, and serialization mismatches that mocks cannot see.\n\n### Lifecycle Hooks: `[Before]` and `[After]`\n\nTUnit's `[Before(scope)]` and `[After(scope)]` hooks replace NUnit's `[SetUp]`\u002F`[TearDown]` family. They are method attributes — async-first, no naming convention required.\n\n| Attribute | Scope | Runs | NUnit equivalent |\n|---|---|---|---|\n| `[Before(Test)]` | Per test | Before each test method | `[SetUp]` |\n| `[After(Test)]` | Per test | After each test method | `[TearDown]` |\n| `[Before(Class)]` | Per class | Once before all tests in the class | `[OneTimeSetUp]` |\n| `[After(Class)]` | Per class | Once after all tests in the class | `[OneTimeTearDown]` |\n| `[Before(Assembly)]` | Per assembly | Once for the whole assembly (static only) | `[SetUpFixture]` |\n| `[After(Assembly)]` | Per assembly | Once for the whole assembly (static only) | `[SetUpFixture]` teardown |\n\n**Pattern 1: Create and dispose a `TestWebApplicationFactory` at class scope**\n\n[`templates\u002Fbefore-after-factory.md`](templates\u002Fbefore-after-factory.md)\n\n**Pattern 2: Create and dispose a test container at class scope**\n\n[`templates\u002Fbefore-after-container.md`](templates\u002Fbefore-after-container.md)\n\n**Pattern 3: Inject resolved services in `[Before(Test)]`**\n\nAfter the factory and container are live at class scope, use `[Before(Test)]` to resolve per-test dependencies from the factory's DI container and create a fresh HTTP client per test:\n\n[`templates\u002Fbefore-after-service-injection.md`](templates\u002Fbefore-after-service-injection.md)\n\n**Pattern 4: Full explicit stack — container + factory + per-test injection**\n\nUse when you own the full lifecycle and are not inheriting from `WebApplicationTest\u003CT>`:\n\n[`templates\u002Fbefore-after-full-stack.md`](templates\u002Fbefore-after-full-stack.md)\n\n**Pattern 5: Assembly-wide shared resources (static hooks)**\n\nAssembly hooks must be `static` methods in a `static class`. Use them only for truly global resources that every test class in the assembly shares:\n\n[`templates\u002Fbefore-after-assembly.md`](templates\u002Fbefore-after-assembly.md)\n\n**When to use `[Before\u002FAfter]` vs. `[ClassDataSource]`**\n\n| Scenario | Prefer |\n|---|---|\n| Session-shared infrastructure (one container for all classes) | `[ClassDataSource\u003CT>(Shared = SharedType.PerTestSession)]` |\n| Class-owned infrastructure (container per test class) | `[Before(Class)]` \u002F `[After(Class)]` |\n| Per-test setup (client, schema, resolved services) | `[Before(Test)]` \u002F `[After(Test)]` |\n| Assembly-wide global resources | `[Before(Assembly)]` \u002F `[After(Assembly)]` (static) |\n\n**Disposal order rule:** always dispose in reverse construction order — if you created factory after container, dispose factory before container.\n\n### Aspire-Hosted Stacks\n\nIf the system under test is composed via .NET Aspire, prefer `TUnit.Aspire`'s `AspireFixture\u003CTAppHost>` — it builds the AppHost, boots every container, waits for health checks, and exposes typed HTTP clients for each resource.\n\n**Pattern: Direct fixture usage**\n\n[`templates\u002Faspire-fixture-direct.md`](templates\u002Faspire-fixture-direct.md)\n\n**Pattern: Customise the fixture**\n\n[`templates\u002Faspire-fixture-custom.md`](templates\u002Faspire-fixture-custom.md)\n\n**Why Aspire fixtures:** the AppHost already encodes the production topology — re-using it in tests removes drift between \"what we test\" and \"what we ship\".\n\n### Test Data Generation: Bogus\n\nBogus still applies. Hardcoded seed data hides bugs and makes integration tests brittle.\n\n[`templates\u002Fbogus-test-data.md`](templates\u002Fbogus-test-data.md)\n\nWhen seeding the database directly, generate full aggregates with Bogus and persist them through the production repository — never via raw SQL. Round-tripping through the real persistence layer is part of what you are validating.\n\n### Assertion Library: TUnit.Assertions.Should\n\nSame library, same patterns as unit tests. Quick reference for integration-flavoured cases:\n\n**Pattern 1: HTTP response assertions**\n\n[`templates\u002Fassert-http-response.md`](templates\u002Fassert-http-response.md)\n\n**Pattern 2: Deserialised body**\n\n[`templates\u002Fassert-deserialized-body.md`](templates\u002Fassert-deserialized-body.md)\n\n**Pattern 3: Side-effect verification**\n\nIntegration tests check observable side effects — never internal state.\n\n[`templates\u002Fassert-side-effects.md`](templates\u002Fassert-side-effects.md)\n\n**Pattern 4: Async exceptions** — same as unit tests\n\n[`templates\u002Fassert-async-exception.md`](templates\u002Fassert-async-exception.md)\n\nUse `.Should().Throw\u003C>()` for both `Action` and `Func\u003CTask>` — never `.ThrowAsync\u003C>()`, never try\u002Fcatch.\n\n### Assert.Multiple: Collect All Failures\n\nAlways wrap related assertions in `Assert.Multiple()`. In integration tests this matters even more — a single test exercises many layers, and you want to see *all* the things that broke at once instead of fixing them one by one across long container-startup cycles.\n\n[`templates\u002Fassert-multiple.md`](templates\u002Fassert-multiple.md)\n\n### The `{ data, error }` Return Shape\n\nEvery API response — including those reached via the HTTP pipeline — must be asserted on both `Data` and `Error`. No exceptions for integration tests.\n\n[`templates\u002Fdata-error-shape.md`](templates\u002Fdata-error-shape.md)\n\n### Test Naming Convention\n\nUse the same `Method_Scenario_Outcome` shape as unit tests, but the \"method\" is usually the HTTP verb + route:\n\n[`templates\u002Ftest-naming.md`](templates\u002Ftest-naming.md)\n\nIf the suite ties to a numbered AC, prefix the display name with the AC ID (`[AC-3] PostTodos_...`).\n\n### Test Structure: Arrange, Act, Assert (AAA)\n\nSame discipline as unit tests:\n\n- **Arrange** — seed any required state through the production repository (not raw SQL); generate request payloads with Bogus; build the HTTP client from the factory.\n- **Act** — issue **one** HTTP call (or one operation) per test.\n- **Assert** — verify the response, then verify the persisted side effect, then verify any emitted events.\n\n**One Act per test.** If you find yourself making two HTTP calls \"to set up state, then verify\", the first call is arrangement — split it into a separate test or do the seeding directly through a fixture helper.\n\n---\n\n## Phase 3 — Complete Example: Endpoint Integration Test\n\n[`templates\u002Fendpoint-integration-test.md`](templates\u002Fendpoint-integration-test.md)\n\n---\n\n## Phase 4 — Operational Concerns\n\n### Performance & Parallelism\n\n- Container startup is the dominant cost. Always use `SharedType.PerTestSession` for infrastructure fixtures.\n- TUnit runs tests in parallel by default. Pair `PerTestSession` containers with per-test isolation (`GetIsolatedName`, `GetIsolatedPrefix`) — never assume serial execution.\n- If a test must run alone, mark it `[NotInParallel]` — but treat that as a bug to fix, not a default.\n\n### CI\u002FCD\n\n- Integration tests require a running Docker daemon on the build agent.\n- Set `ASPIRE_ALLOW_UNSECURED_TRANSPORT=true` in CI when using `AspireFixture` without trusted certificates.\n- Increase `ResourceTimeout` to 2–5 minutes on shared CI runners.\n\n### Diagnostics\n\n- `WatchResourceLogs(\"apiservice\")` streams a container's logs into the test output — invaluable when a test fails and you need to know what the app saw.\n- `EnableHttpExchangeCapture = true` records every request\u002Fresponse pair the test issued — assert against `HttpCapture!.Last` when the response object alone is not enough.\n\n### What NOT to do\n\n- Do **not** seed test data with raw SQL when a repository exists — round-trip through the real code path.\n- Do **not** mock anything in an integration test. If you need a deterministic clock or a fake email sender, use `ConfigureTestServices` to replace it with a real test double, not a mock.\n- Do **not** share mutable state between tests via static fields — use TUnit's isolation helpers instead.\n- Do **not** skip `Assert.Multiple()` because \"the test only has two assertions\". The discipline is uniform.\n\n---\n\n## Phase 5 — Key Takeaways\n\nWhen writing C# integration tests for HypermediaEngine:\n\n1. **Host with `TestWebApplicationFactory\u003CProgram>`** — never the vanilla ASP.NET factory.\n2. **Use Testcontainers for real infrastructure** — Postgres, Redis, Kafka, all of it.\n3. **No mocks** — if you need one, the test belongs in the unit suite.\n4. **Share containers across the session, isolate state per test** — `PerTestSession` + `GetIsolatedName`.\n5. **Use Aspire fixtures** when the system is already composed with Aspire.\n6. **Generate test data with Bogus** — round-trip seeds through the production repository.\n7. **Assert with TUnit.Assertions.Should** — `.Should().Throw\u003C>()` for both sync and async.\n8. **Wrap related assertions in `Assert.Multiple()`** — see all failures from one container cycle.\n9. **Always assert both `Data` and `Error`** — the `{ data, error }` shape is mandatory end-to-end.\n10. **Verify side effects** — read the database, check emitted events, inspect captured exchanges.\n\nFollow these patterns consistently across all integration suites.\n",{"name":5,"description":7},"main","00b2c68281930728ee390bb16cec32b88d2caac7",".github\u002Fskills\u002Fcsharp-integration-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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add rafsanulhasan\u002FHypermediaEngine --skill csharp-integration-testing",{"tool":58,"command":59},"bunx","bunx skills add rafsanulhasan\u002FHypermediaEngine --skill csharp-integration-testing",{"tool":61,"command":62},"pnpm","pnpm dlx skills add rafsanulhasan\u002FHypermediaEngine --skill csharp-integration-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002FSKILL.md",true,[66,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"templates\u002Faspire-fixture-custom.md","REFERENCE","参考文档",523,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Faspire-fixture-custom.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"templates\u002Faspire-fixture-direct.md",533,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Faspire-fixture-direct.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"templates\u002Fassert-async-exception.md",156,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fassert-async-exception.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"templates\u002Fassert-deserialized-body.md",349,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fassert-deserialized-body.md",{"path":85,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":86,"sourceHtmlUrl":87},"templates\u002Fassert-http-response.md",162,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fassert-http-response.md",{"path":89,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":90,"sourceHtmlUrl":91},"templates\u002Fassert-multiple.md",264,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fassert-multiple.md",{"path":93,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":94,"sourceHtmlUrl":95},"templates\u002Fassert-side-effects.md",292,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fassert-side-effects.md",{"path":97,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":98,"sourceHtmlUrl":99},"templates\u002Fbase-class.md",128,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fbase-class.md",{"path":101,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":102,"sourceHtmlUrl":103},"templates\u002Fbefore-after-assembly.md",511,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fbefore-after-assembly.md",{"path":105,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":106,"sourceHtmlUrl":107},"templates\u002Fbefore-after-container.md",546,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fbefore-after-container.md",{"path":109,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":110,"sourceHtmlUrl":111},"templates\u002Fbefore-after-factory.md",398,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fbefore-after-factory.md",{"path":113,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":114,"sourceHtmlUrl":115},"templates\u002Fbefore-after-full-stack.md",1451,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fbefore-after-full-stack.md",{"path":117,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":118,"sourceHtmlUrl":119},"templates\u002Fbefore-after-service-injection.md",1221,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fbefore-after-service-injection.md",{"path":121,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":122,"sourceHtmlUrl":123},"templates\u002Fbogus-test-data.md",269,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fbogus-test-data.md",{"path":125,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":126,"sourceHtmlUrl":127},"templates\u002Fclassdatasource-injection.md",170,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fclassdatasource-injection.md",{"path":129,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":130,"sourceHtmlUrl":131},"templates\u002Fconfigure-test-services.md",261,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fconfigure-test-services.md",{"path":133,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":134,"sourceHtmlUrl":135},"templates\u002Fdata-error-shape.md",346,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fdata-error-shape.md",{"path":137,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":138,"sourceHtmlUrl":139},"templates\u002Fendpoint-integration-test.md",2640,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fendpoint-integration-test.md",{"path":141,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":142,"sourceHtmlUrl":143},"templates\u002Ffactory-definition.md",631,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Ffactory-definition.md",{"path":145,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":146,"sourceHtmlUrl":147},"templates\u002Fmulti-container-topology.md",952,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fmulti-container-topology.md",{"path":149,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":150,"sourceHtmlUrl":151},"templates\u002Fper-test-schema-isolation.md",605,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fper-test-schema-isolation.md",{"path":153,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":154,"sourceHtmlUrl":155},"templates\u002Fpostgres-fixture.md",512,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Fpostgres-fixture.md",{"path":157,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":158,"sourceHtmlUrl":159},"templates\u002Ftest-naming.md",215,"https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcsharp-integration-testing\u002Ftemplates\u002Ftest-naming.md",[161,186,205,224,252,275],{"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":168,"publishedAt":40},"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",[167],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[169,170,33,24,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,37],"write tests","write","design","test","project conventions","test plan","Bash","plan","quality","xunit","read","edit","coverage","engineer","mutation testing","project","mutation",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":40},"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",[],[193,170,194,29,195,196,197,175,198,199,200,201,179,180,202,184,33,203,204,37],"documentation","write documentation","directory","workflow","architecture","src","repo","decisions","README","files","updates","at",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":211,"publishedAt":40},"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",[],[212,170,213,171,214,197,215,216,217,218,200,179,219,220,184,221,222,37,223],"adr","write adr","docs","architect","decision","choice","grep","architecture decision record","record","software","opus","architecture decision",{"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":236,"publishedAt":40},"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",[230,231],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":232,"categoryName":233,"taxonomyType":234,"taxonomyTypeDesc":235},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[24,237,238,239,240,34,241,29,242,243,244,245,246,247,248,249,33,250,251,37],"playwright","ui","playwright ui testing","ui testing","tunit playwright ui testing","official","dev","examples","ci","lifecycle","model","page","inheritance","end","object",{"skillNo":253,"name":254,"nameZh":6,"description":255,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":256,"categories":257,"keywords":261,"publishedAt":40},"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",[258],{"categoryNo":259,"categoryName":260,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[254,262,263,264,265,266,267,268,269,270,271,272,273,274],"routing","classification","work","user","dependency","task","priorities","decomposition","user request","mapping","with","break","request",{"skillNo":276,"name":277,"nameZh":6,"description":278,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":279,"categories":280,"keywords":285,"publishedAt":40},"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",[281,284],{"categoryNo":282,"categoryName":283,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":232,"categoryName":233,"taxonomyType":234,"taxonomyTypeDesc":235},[171,286,287,288,289,290,291,218,179,292,293,294,295,296,297,221,298,299,272,300],"system","system design","web","design systems","learning","haiku","use","design patterns","design principles","expert","patterns","systems","architectures","principles","implementing"]