Skills dotnet-backend-patterns

📦

dotnet-backend-patterns

Name: dotnet-backend-patterns
Author: sickn33

Content revision r2 Safe ⚙️ External commands📁 Filesystem access

Build Production-Ready .NET Backends

Complex .NET backends need consistent architecture, data access, resilience, and testing patterns. This skill supplies focused guidance and reusable C# templates for those decisions.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "dotnet-backend-patterns" from https://skillstore.io/skills/sickn33-dotnet-backend-patterns.md and its manifest at https://skillstore.io/api/skills/sickn33-dotnet-backend-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-dotnet-backend-patterns.md Signed manifest GET /api/skills/sickn33-dotnet-backend-patterns/manifest Signed lockfile GET /api/skills/sickn33-dotnet-backend-patterns/lockfile

Test it

Using "dotnet-backend-patterns". Plan the backend structure for a product catalog API using EF Core and Redis.

Expected outcome:

Architecture: Keep API endpoints, application services, domain rules, and infrastructure adapters in separate layers.
Data access: Use projections and no-tracking queries for reads, with explicit transactions for multi-step writes.
Caching: Cache product reads with bounded lifetimes and invalidate affected keys after successful writes.
Testing: Cover domain behavior with unit tests and API flows with isolated integration tests.

Using "dotnet-backend-patterns". Review a Dapper repository that builds filters and ignores cancellation.

Expected outcome:

High priority: Parameterize every filter value and allow-list any dynamic table or column identifiers.
Medium priority: Pass cancellation tokens through CommandDefinition for every asynchronous database operation.
Medium priority: Define transaction ownership and connection disposal at a consistent application boundary.

Using "dotnet-backend-patterns". Recommend improvements for a service that blocks on asynchronous calls and creates HttpClient instances.

Expected outcome:

Use asynchronous calls through the full request path, propagate cancellation, and obtain clients through IHttpClientFactory. Add timeout, retry, and failure-path tests.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All 32 static findings are false positives caused by ordinary C# identifiers, Markdown code spans, and the term .NET. The reviewed content provides documentation and templates, with no command execution, hidden-file access, system reconnaissance, prompt injection, or malicious intent.

Files scanned

2,608

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (2)

SKILL.md:36 SKILL.md:40

📁 Filesystem access (2)

SKILL.md:3 SKILL.md:11

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-dotnet-backend-patterns/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-dotnet-backend-patterns/security.svg)](https://skillstore.io/skills/sickn33-dotnet-backend-patterns?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-dotnet-backend-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-dotnet-backend-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-dotnet-backend-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). dotnet-backend-patterns security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-dotnet-backend-patterns/audits/5

BibTeX citation

@techreport{sickn33-sickn33-dotnet-backend-patterns-2026,
  author = {sickn33},
  title = {dotnet-backend-patterns security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-dotnet-backend-patterns/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "dotnet-backend-patterns security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-dotnet-backend-patterns/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-dotnet-backend-patterns:audit:5"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

sickn33 Recommended Current

sickn33-dotnet-backend-patterns

Skillstore Score 78

Evidence Confidence High

Skillstore usage 14

Updated

2026-08-21

wshobson

wshobson-dotnet-backend-patterns

Skillstore Score 77

Evidence Confidence High

Skillstore usage 22

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Plan a New API

Create architecture boundaries, dependency registrations, data access choices, caching, error handling, and tests for a new .NET API.

Review Data Access

Assess EF Core and Dapper code for query efficiency, parameterization, tracking, transactions, indexing, and cancellation support.

Modernize a Service

Replace blocking calls, weak configuration, fragile caching, and missing tests with current .NET backend patterns.

Try These Prompts

Explain a Backend Pattern

Explain the [pattern] for a developer new to .NET. Include its purpose, appropriate use cases, tradeoffs, and a short implementation outline.

Design an API Feature

Design a .NET implementation for [feature]. Cover architecture boundaries, dependency injection, async behavior, validation, data access, errors, caching, and tests.

Review Repository Code

Review the provided EF Core or Dapper repository. Identify correctness, performance, security, cancellation, transaction, and maintainability issues. Prioritize findings and suggest focused changes.

Plan a Backend Modernization

Create a phased modernization plan for this .NET backend and its constraints. Compare architecture options and identify migration risks. Include tests, observability, rollout, and rollback.

Best Practices

Provide the target .NET version, database provider, deployment model, performance goals, and relevant code.
Ask for prioritized findings with explicit correctness, security, performance, and maintainability impacts.
Validate suggested patterns with project tests, query plans, benchmarks, and production-like integration environments.

Avoid

Do not apply repository, caching, or resilience patterns without a concrete requirement and measured benefit.
Do not copy templates without adapting ownership, transactions, validation, authorization, and failure handling.
Do not treat example configuration values or provider-specific APIs as production defaults.

Frequently Asked Questions

Which .NET versions does this skill support?

The material uses modern .NET patterns, but each recommendation must be checked against the project version and package APIs.

Does it cover both EF Core and Dapper?

Yes. It covers EF Core optimization and configuration, plus Dapper queries, mappings, transactions, type handlers, and repositories.

Can it generate complete production code?

It provides implementation guidance and templates. Production code still needs domain requirements, security controls, project conventions, and validation.

Does it include testing guidance?

Yes. It includes unit testing with xUnit and Moq, plus API integration testing with WebApplicationFactory.

Does it implement MCP servers?

It identifies MCP servers as a use case, but the included resources lack detailed protocol and transport implementation guidance.

Will it optimize database performance automatically?

No. It recommends patterns, but optimization requires real query plans, workloads, indexes, provider behavior, and measured benchmarks.