dotnet-architect
Design Production-Ready .NET Backends
Complex .NET systems need clear architecture, reliable data access, and measurable performance. This skill guides production-ready C#, ASP.NET Core, testing, caching, and deployment decisions.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "dotnet-architect" from https://skillstore.io/skills/sickn33-dotnet-architect.md and its manifest at https://skillstore.io/api/skills/sickn33-dotnet-architect/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.
Test it
Using "dotnet-architect". Design caching for a product catalog with 100,000 items.
Expected outcome:
- Use local memory for short-lived hot data and Redis as the shared cache.
- Apply cache-aside reads, event-driven invalidation, randomized expiration, and explicit stale-data limits.
- Measure hit rate, latency, eviction, and database fallback behavior before release.
Using "dotnet-architect". Review an asynchronous order handler for reliability and performance.
Expected outcome:
- Pass cancellation tokens through every asynchronous dependency and avoid blocking calls.
- Define transaction boundaries around durable state changes and make retries idempotent.
- Add structured logs, latency metrics, integration tests, and failure-path tests.
Using "dotnet-architect". Choose between EF Core and Dapper for a reporting service.
Expected outcome:
- Use EF Core for transactional workflows and maintainable domain persistence.
- Use Dapper for measured reporting queries that need precise SQL and mapping control.
- Keep transaction ownership explicit and benchmark representative workloads before adopting a mixed approach.
Security Audit
SafeBoth static findings are false positives caused by Markdown backticks: a file reference on line 24 and a C# fence beginning on line 150. The skill contains architectural guidance and example C#; no executable shell command or malicious intent was found. No semantic security findings were identified.
Risk Factors
⚙️ External commands (2)
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.
Copy report link
https://skillstore.io/skills/sickn33-dotnet-architect/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-dotnet-architect?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-dotnet-architect?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-dotnet-architect/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-dotnet-architect.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-architect security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-dotnet-architect/audits/5BibTeX citation
@techreport{sickn33-sickn33-dotnet-architect-2026,
author = {sickn33},
title = {dotnet-architect security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-dotnet-architect/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-architect 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-architect/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-dotnet-architect:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Modernize an ASP.NET Core API
Review an existing API and create a prioritized plan for structure, async behavior, data access, testing, security, and performance.
Define Enterprise Service Boundaries
Compare modular monolith, vertical slice, and microservice options using scale, ownership, consistency, and operational constraints.
Prepare a .NET Service for Production
Plan containers, health checks, telemetry, resilience, configuration, and deployment controls for a production service.
Try These Prompts
Explain a suitable ASP.NET Core structure for [application]. Cover projects, dependency injection, configuration, validation, and testing.
Review this C# or ASP.NET Core design: [details]. Identify correctness, async, security, maintainability, and performance issues. Prioritize recommendations.
Design data access for [workload] using EF Core, Dapper, or both. Address transactions, query performance, migrations, testing, and failure handling.
Create an architecture proposal for [system] at [scale]. Include service boundaries, caching, resilience, observability, security, deployment, tradeoffs, and validation steps.
Best Practices
- Provide workload, latency, consistency, deployment, and team constraints before requesting an architecture.
- Share relevant code and observed metrics when asking for performance or reliability reviews.
- Request tradeoffs, validation steps, and test coverage with every recommended design.
Avoid
- Do not request a complete architecture without business boundaries, scale, or operational constraints.
- Do not apply microservices, repositories, CQRS, or caching without a demonstrated need.
- Do not treat generated examples as production-ready before testing security, failure behavior, and performance.