「with」の検索結果

Generate comprehensive investor-ready business case document with market, solution, financials, and strategy

日本語の概要は準備中です。原文の説明を表示しています。

Test Data Builder Pattern complete implementation guide. Used when using builder pattern to create maintainable test data or simplify complex object test preparation. Covers fluent interface, semantic methods, default value design, and Builder composition patterns. Keywords: test data builder, builder pattern test, test data builder, object mother, fluent interface, fluent interface, UserBuilder, ProductBuilder, .With(), .Build(), AUser(), test data preparation, complex object creation, semantic testing

日本語の概要は準備中です。原文の説明を表示しています。

Builds .NET CLI apps with System.CommandLine 2.0. Commands, options, SetAction, parsing, testing.

日本語の概要は準備中です。原文の説明を表示しています。

Verifies complex outputs with Verify. API responses, scrubbing non-deterministic values.

日本語の概要は準備中です。原文の説明を表示しています。

Symbol-level refactoring with automatic reference updates using Serena MCP

日本語の概要は準備中です。原文の説明を表示しています。

Creates a new .NET project. Generates solution with CPM, analyzers, editorconfig, SourceLink.

日本語の概要は準備中です。原文の説明を表示しています。

Complete guide for AutoFixture and Bogus integration. Use when you need to combine AutoFixture with Bogus to generate test data that is both anonymous and realistic. Covers SpecimenBuilder integration, hybrid generators, test data factories, and circular reference handling. Keywords: autofixture bogus integration, autofixture bogus, bogus integration, Faker, EmailSpecimenBuilder, PhoneSpecimenBuilder, NameSpecimenBuilder, realistic test data, semantic data, hybrid generator, HybridTestDataGenerator, OmitOnRecursionBehavior, circular reference

日本語の概要は準備中です。原文の説明を表示しています。

Complete guide for TUnit new-generation testing framework. Use when creating test projects with TUnit or migrating from xUnit to TUnit. Covers Source Generator driven test discovery, AOT compilation support, fluent async assertions. Includes project creation, [Test] attribute, lifecycle management, parallel control, and xUnit syntax comparison. Keywords: TUnit, tunit testing, source generator testing, AOT testing, new generation testing framework, [Test], [Arguments], TUnit.Assertions, Assert.That, Before(Test), After(Test), NotInParallel, TUnit.Templates, Microsoft.Testing.Platform, TUnit vs xUnit, parallel execution

日本語の概要は準備中です。原文の説明を表示しています。

Specialized skill for handling complex object comparison and deep validation. Use when you need to compare deep objects, exclude specific properties, handle circular references, or validate DTOs/Entities. Covers BeEquivalentTo, Excluding, Including, custom comparison rules, etc. Keywords: object comparison, deep comparison, BeEquivalentTo, DTO comparison, Entity validation, excluding properties, circular reference, Excluding, Including, ExcludingNestedObjects, RespectingRuntimeTypes, WithStrictOrdering, ignore timestamp, exclude timestamp

日本語の概要は準備中です。原文の説明を表示しています。

Registers and resolves services with MS DI. Keyed services, scopes, decoration, lifetimes.

日本語の概要は準備中です。原文の説明を表示しています。

Tests with real infrastructure. WebApplicationFactory, Testcontainers, Aspire, fixtures.

日本語の概要は準備中です。原文の説明を表示しています。

Offline mode with local caching for air-gapped environments

日本語の概要は準備中です。原文の説明を表示しています。

Offline mode with local caching for air-gapped environments

日本語の概要は準備中です。原文の説明を表示しています。

AI-powered wiki generation for code repositories with commands, agents, and skills

日本語の概要は準備中です。原文の説明を表示しています。

Audit and remediate dependency/package vulnerabilities across .NET backend, frontend (npm/pnpm/yarn), and Rust projects with severity-based quality gates. Use when the user asks for SCA checks, dependency hardening, or release security gates before build/package.

日本語の概要は準備中です。原文の説明を表示しています。

Extend dev-software-engineer with .NET/C# backend specialization for Clean Architecture, CQRS, EF Core, and production-ready API practices. Use when tasks involve ASP.NET endpoints, handlers, services, dependency injection, MediatR, migrations, or backend performance/resilience.

日本語の概要は準備中です。原文の説明を表示しています。

Base implementation skill for this repository across .NET/C#, backend APIs, database/ORM, frontend Vue/Quasar, and Rust with Clean Architecture rules. Use when the user asks to build features, fix bugs, refactor modules, or improve code-level performance, and use specialized skills as inheritance layers when available.

日本語の概要は準備中です。原文の説明を表示しています。

Use for non-trivial feature, behavior, workflow, or architecture work before execution planning. Create or update a versioned spec under planning/specs/active with design intent, alternatives, risks, acceptance criteria, and planning readiness.

日本語の概要は準備中です。原文の説明を表示しています。

Use for non-trivial, design-bearing, or architecture-affecting work before execution planning. Creates or updates a versioned spec under planning/specs/active/ with design intent, alternatives, risks, and acceptance criteria.

日本語の概要は準備中です。原文の説明を表示しています。

Extend dev-software-engineer with .NET/C# backend specialization for Clean Architecture, CQRS, EF Core, and production-ready API practices. Use when tasks involve ASP.NET endpoints, handlers, services, dependency injection, MediatR, migrations, or backend performance/resilience and should follow the base implementation workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Audit and remediate dependency/package vulnerabilities across .NET backend, frontend (npm/pnpm/yarn), and Rust projects with severity-based quality gates. Use when the user asks for SCA checks, dependency hardening, or release security gates.

日本語の概要は準備中です。原文の説明を表示しています。

Build and harden high-performance APIs with strong security controls, endpoint budgets, rate limiting, and resilience patterns. Use when tasks involve API latency/throughput tuning, abuse resistance, authz hardening, or API release gates.

日本語の概要は準備中です。原文の説明を表示しています。

Implement and refactor frontend features using Vue and Quasar with repository architecture, theming, UX, and performance standards. Use when tasks involve components, composables, Pinia, routing, i18n/UI behavior, responsive layouts, or frontend clean architecture changes.

日本語の概要は準備中です。原文の説明を表示しています。

Improve platform resilience with timeout/retry/circuit-breaker strategy, capacity controls, chaos testing, and disaster recovery readiness. Use when tasks involve reliability hardening, failure-mode testing, incident prevention, or recovery objectives.

日本語の概要は準備中です。原文の説明を表示しています。