Skills dotnet-backend-patterns
📦

dotnet-backend-patterns

Content revision r1 Safe ⚙️ External commands📁 Filesystem access

Build Reliable .NET Backends

Modern .NET backend work requires consistent choices for APIs, data access, caching, and tests. This skill gives Claude, Codex, and Claude Code practical patterns for production C# services.

Supports: Claude Codex Code(CC)
🥉 77 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/wshobson-dotnet-backend-patterns.md and its manifest at https://skillstore.io/api/skills/wshobson-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/wshobson-dotnet-backend-patterns.md Signed manifest GET /api/skills/wshobson-dotnet-backend-patterns/manifest Signed lockfile GET /api/skills/wshobson-dotnet-backend-patterns/lockfile

Test it

Using "dotnet-backend-patterns". I need a repository design for product search with EF Core and Dapper.

Expected outcome:

A concise comparison of repository boundaries, parameterized queries, pagination, cancellation, and when each data access tool fits best.

Using "dotnet-backend-patterns". Review this order service for async and validation issues.

Expected outcome:

A review highlighting blocking calls, missing cancellation tokens, validation gaps, Result pattern usage, and targeted test cases.

Using "dotnet-backend-patterns". Plan caching for product lookups in an API.

Expected outcome:

A cache design covering memory cache, Redis, expiration policy, invalidation, stale reads, and logging considerations.

Security Audit

Safe
v7 • 7/7/2026 Open versioned report

The audit found no confirmed security issues after manual adjudication. Static alerts are false positives caused by Markdown code fences, C# syntax, .NET prose, and educational database examples. No evidence found for prompt injection, malicious command execution, data exfiltration, or host reconnaissance.

5
Files scanned
2,578
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (24)
SKILL.md:25-47 SKILL.md:47-51 SKILL.md:51-101 SKILL.md:101-105 SKILL.md:105-150 SKILL.md:150-154 SKILL.md:154-227 SKILL.md:227-231 SKILL.md:231-293 SKILL.md:293-299 SKILL.md:299-374 SKILL.md:374-378 SKILL.md:378-478 SKILL.md:478-484 SKILL.md:484-597 SKILL.md:597-603 SKILL.md:603-708 SKILL.md:708-712 SKILL.md:712-772 SKILL.md:772-789 SKILL.md:789 SKILL.md:794-796 SKILL.md:796-802 SKILL.md:802-803
📁 Filesystem access (2)
SKILL.md:3 SKILL.md:8
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
Security Assessment

Copy report link

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

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/wshobson-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

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

BibTeX citation

@techreport{wshobson-wshobson-dotnet-backend-patterns-2026, author = {wshobson}, title = {dotnet-backend-patterns security audit report (audit version 7)}, institution = {Skillstore}, year = {2026}, number = {7}, url = {https://skillstore.io/skills/wshobson-dotnet-backend-patterns/audits/7}, 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 7)" version: "unspecified" type: report authors: - name: "wshobson" date-released: "2026-07-07" url: "https://skillstore.io/skills/wshobson-dotnet-backend-patterns/audits/7" identifiers: - type: other value: "skillstore:wshobson-dotnet-backend-patterns:audit:7" 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
sickn33 Recommended

sickn33-dotnet-backend-patterns

Skillstore Score 78
Evidence Confidence High
Skillstore usage 14
Updated

2026-08-21

wshobson Current

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
55
Architecture
85
Maintainability
85
Content
72
Community
74
Spec Compliance

What You Can Build

Design a New API

Plan folders, services, repositories, validation, caching, and tests for a new ASP.NET Core service.

Review Data Access Choices

Compare EF Core and Dapper patterns for query performance, maintainability, transactions, and repository boundaries.

Standardize Team Guidance

Create shared .NET backend conventions for dependency injection, configuration, testing, and common anti-patterns.

Try These Prompts

Create a Web API Skeleton 
Use this skill to outline a .NET Web API for products. Include folders, service lifetimes, DTOs, validation, and test strategy.
Review Async Service Code 
Review this C# service for async, cancellation, dependency injection, and Result pattern issues. Suggest concrete improvements with rationale.
Choose EF Core or Dapper 
Design a data access layer for high-read product search. Compare EF Core and Dapper, then recommend repositories and caching boundaries.
Plan a Production Backend 
Plan a production .NET backend for orders. Cover service boundaries, transactions, resilience, caching, tests, configuration, and operational risks.

Best Practices

  • Validate generated patterns against your domain model, database provider, and deployment constraints.
  • Ask for tests and failure cases when using the skill for service or repository design.
  • Review security-sensitive flows separately, especially authentication, authorization, secrets, and external integrations.

Avoid

  • Do not copy sample domains directly into production without adapting names, validation, and policies.
  • Do not mix synchronous blocking calls into async request flows.
  • Do not choose Dapper or EF Core based only on preference; match the tool to query complexity.

Frequently Asked Questions

What does this skill help build?
It helps design and review .NET backend services, APIs, repositories, caching layers, configuration, and tests.
Does it support ASP.NET Core?
Yes. The guidance targets modern ASP.NET Core APIs and related service architecture patterns.
Can it generate complete applications?
It can guide structure and sample implementation, but you must integrate, compile, test, and secure the final application.
When should I use EF Core instead of Dapper?
Use EF Core for rich domain models and change tracking. Use Dapper for focused, performance-sensitive queries.
Does it include testing guidance?
Yes. It covers xUnit, mocking, validation tests, integration tests, and WebApplicationFactory patterns.
Is it safe to use with Claude Code or Codex?
The reviewed content is documentation and templates only. Generated code still requires normal project review before use.

Developer Details

Author

wshobson

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/wshobson/agents/tree/main/plugins/dotnet-contribution/skills/dotnet-backend-patterns

Ref

36e07d5e13068e5be64447e8f20b427cf2cbd21a

Maintenance freshness

7/18/2026

Usage

18 downloads · 359 views

File structure

📁 assets/

📄 repository-template.cs

📄 service-template.cs

📁 references/

📄 dapper-patterns.md

📄 ef-core-best-practices.md

📄 SKILL.md