Results for “struct”

Optimizes .NET allocations and throughput. Span, ArrayPool, ref struct, sealed, stackalloc.

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

Builds .NET MAUI mobile apps. Project structure, XAML/MVVM, platform services, caveats.

The English summary is being prepared. Showing the original description.

Using records, pattern matching, primary constructors, collection expressions. C# 12-15 by TFM.

The English summary is being prepared. Showing the original description.

Adds test infrastructure to a .NET project. Scaffolds xUnit project, coverlet, layout.

The English summary is being prepared. Showing the original description.

Structures CLI app layers. Command/handler/service separation, clig.dev principles, exit codes.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Build a minimal context pack and recommend the correct specialist path for token-efficient execution. Use when the task is non-trivial, spans multiple domains, or should reduce token usage before implementation.

The English summary is being prepared. Showing the original description.

Build and maintain CI/CD pipelines, containerization, Kubernetes manifests, and quality gates. Use when tasks involve Docker, Kubernetes, GitHub Actions/Azure DevOps pipelines, deployment, reliability, or static analysis workflows.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Design and implement observability and SRE controls including SLO/SLI, OpenTelemetry instrumentation, alerting, dashboards, and incident readiness. Use when tasks involve telemetry coverage, operational reliability metrics, incident response, or runbook quality.

The English summary is being prepared. Showing the original description.

Build and maintain CI/CD pipelines, containerization, Kubernetes manifests, and quality gates for this repository. Use when the user asks for Docker, Kubernetes, GitHub Actions/Azure DevOps pipelines, deployment, reliability, or static analysis workflows.

The English summary is being prepared. Showing the original description.

Plan and sequence complex implementation work into deterministic, testable steps. Use when the user asks for planning, roadmap breakdown, execution strategy, effort estimation, or multi-step delivery coordination across domains.

The English summary is being prepared. Showing the original description.

Design and enforce privacy and data protection controls across application, API, and database layers. Use when tasks involve PII handling, retention/deletion policies, consent, data minimization, auditability, or compliance-oriented architecture changes.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Mandatory final risk-focused review for any repository change. Checks security, architecture boundaries, test coverage, and release readiness before closeout.

The English summary is being prepared. Showing the original description.

Creates or updates the active planning artifact under planning/active/ for any change-bearing workstream. Consumes the active spec when one exists. Defines ordered tasks, target paths, commands, and checkpoints.

The English summary is being prepared. Showing the original description.

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is reached.

The English summary is being prepared. Showing the original description.

Perform repository-aware code reviews focused on bugs, regressions, architectural violations, missing tests, and operational risks. Use when the user asks for review of diffs, pull requests, patches, or implementation quality.

The English summary is being prepared. Showing the original description.

Assembles the minimal context pack for a given task. Use when the task spans multiple domains or the context set has obvious redundancy. Do not trim required working context by default.

The English summary is being prepared. Showing the original description.

Create safe, deterministic git worktrees for large or risky workstreams using the repository-owned runtime helper and Windows-safe defaults.

The English summary is being prepared. Showing the original description.

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is ready.

The English summary is being prepared. Showing the original description.