Dotnet Backend Patterns
ListedHelps with backend development, patterns as part of developing backend services and APIs workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add sickn33/agentic-awesome-skills --skill dotnet-backend-patterns -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
sickn33
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
Declares what it does: failed
No SKILL.md was found in the skill's directory.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned sickn33/antigravity-awesome-skills at 5a4cdd9df8.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 5a4cdd9df8
- Scanned
- 0 files
- Copies in repo
- 3 — all of them scanned
About this skill
What it does
This skill provides guidance on developing production-grade .NET backend APIs, MCP (Model Context Protocol) servers, and enterprise backends. It focuses on applying modern best practices and C#/.NET patterns for tasks like designing service architectures, implementing caching, and optimizing database access. The skill aims to help developers build robust and efficient backend solutions using current industry standards.
When to use it
- Developing new .NET Web APIs or MCP servers.
- Reviewing existing C# code for quality and performance improvements.
- Designing service architectures that utilize dependency injection.
- Implementing caching strategies, particularly with Redis.
- Optimizing database access using EF Core or Dapper.
Key capabilities
- Guidance on defining architecture boundaries, modules, and layering in .NET applications.
- Application of Dependency Injection (DI), asynchronous patterns, and resilience strategies.
- Validation of data access performance and caching implementations.
- Assistance with writing unit and integration tests.
- Access to a detailed implementation playbook (
resources/implementation-playbook.md) for specific .NET patterns and examples.
Example prompts
- "How can I implement dependency injection in my new .NET API?"
- "What are some best practices for optimizing database access with EF Core?"
- "Can you suggest a caching strategy using Redis for this backend service?"
- “Show me an example of how to configure applications using the IOptions pattern.”
Tips & gotchas
- This skill is specifically designed for projects utilizing .NET and C#. It's not suitable for frontend or non-.NET related tasks.
- Always validate the output with environment-specific testing and expert review, as this skill’s suggestions are not a substitute for those processes.
- If you're unsure about inputs, permissions, safety boundaries, or success criteria, pause and ask for clarification before proceeding.