Specify a webhook-driven task for OpenClaw
Describe event inputs, validation, deduplication, and intended actions before integration work.
4,924,171 AI resources indexedWorking toward the world’s largest AI resource index.
Master C#/.NET patterns for building production-grade APIs, MCP servers, and enterprise backends with modern best practices (2024/2025).
--- name: dotnet-backend-patterns-5dd8cc2e02f3 description: "Master C#/.NET patterns for building production-grade APIs, MCP servers, and enterprise backends with modern best practices (2024/2025)." risk: safe source: community date_added: "2026-02-27" --- # .NET Backend Development Patterns Master C#/.NET patterns for building production-grade APIs, MCP servers, and enterprise backends with modern best practices (2024/2025). ## Use this skill when - Developing new .NET Web APIs or MCP servers - Reviewing C# code for quality and performance - Designing service architectures with dependency injection - Implementing caching strategies with Redis - Writing unit and integration tests - Optimizing database access with EF Core or Dapper - Configuring applications with IOptions pattern - Handling errors and implementing resilience patterns ## Do not use this skill when - The project is not using .NET or C# - You only need frontend or client guidance - The task is unrelated to backend architecture ## Instructions - Define architecture boundaries, modules, and layering. - Apply DI, async patterns, and resilience strategies. - Validate data access performance and caching. - Add tests and observability for critical flows. - If detailed patterns are required, open `resources/implementation-playbook.md`. ## Resources - `resources/implementation-playbook.md` for detailed .NET patterns and examples. --- <!-- AGI-INTEGRATION-START --> ## AGI Framework Integration > **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)** > Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills) ### Memory-First Protocol Retrieve prior API design decisions, database schema choices, and error handling patterns. Cache API response templates for consistent error formatting. ```bash # Check for prior backend/API context before starting python3 execution/memory_manager.py auto --query "API design patterns and architecture decisions for Dotnet Backend Patterns" ``` ### Storing Results After completing work, store backend/API decisions for future sessions: ```bash python3 execution/memory_manager.py store \ --content "API architecture: REST with HATEOAS, JWT auth, rate limiting at 100 req/min per tenant" \ --type decision --project <project> \ --tags dotnet-backend-patterns backend ``` ### Multi-Agent Collaboration Share API contract changes with frontend agents so they update their client code, and with QA agents for test coverage. ```bash python3 execution/cross_agent_context.py store \ --agent "<your-agent>" \ --action "Implemented API endpoints — 5 new routes with OpenAPI spec and integration tests" \ --project <project> ``` ### Agent Team: Code Review After implementation, dispatch `code_review_team` for two-stage review (spec compliance + code quality) before merging. <!-- AGI-INTEGRATION-END -->--- name: dotnet-backend-patterns-5dd8cc2e02f3 description: "Master C#/.NET patterns for building production-grade APIs, MCP servers, and enterprise backends with modern best practices (2024/2025)." risk: safe source: community date_added: "2026-02-27" --- # .NET Backend Development Patterns Master C#/.NET patterns for building production-grade APIs, MCP servers, and enterprise backends with modern best practices (2024/2025). ## Use this skill when - Developing new .NET Web APIs or MCP servers - Reviewing C# code for quality and performance - Designing service architectures with dependency injection - Implementing caching strategies with Redis - Writing unit and integration tests - Optimizing database access with EF Core or Dapper - Configuring applications with IOptions pattern - Handling errors and implementing resilience patterns ## Do not use this skill when - The project is not using .NET or C# - You only need frontend or client guidance - The task is unrelated to backend architecture ## Instructions - Define architecture boundaries, modules, and layering. - Apply DI, async patterns, and resilience strategies. - Validate data access performance and caching. - Add tests and observability for critical flows. - If detailed patterns are required, open `resources/implementation-playbook.md`. ## Resources - `resources/implementation-playbook.md` for detailed .NET patterns and examples. --- <!-- AGI-INTEGRATION-START --> ## AGI Framework Integration > **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)** > Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills) ### Memory-First Protocol Retrieve prior API design decisions, database schema choices, and error handling patterns. Cache API response templates for consistent error formatting. ```bash # Check for prior backend/API context before starting python3 execution/memory_manager.py auto --query "API design patterns and architecture decisions for Dotnet Backend Patterns" ``` ### Storing Results After completing work, store backend/API decisions for future sessions: ```bash python3 execution/memory_manager.py store \ --content "API architecture: REST with HATEOAS, JWT auth, rate limiting at 100 req/min per tenant" \ --type decision --project <project> \ --tags dotnet-backend-patterns backend ``` ### Multi-Agent Collaboration Share API contract changes with frontend agents so they update their client code, and with QA agents for test coverage. ```bash python3 execution/cross_agent_context.py store \ --agent "<your-agent>" \ --action "Implemented API endpoints — 5 new routes with OpenAPI spec and integration tests" \ --project <project> ``` ### Agent Team: Code Review After implementation, dispatch `code_review_team` for two-stage review (spec compliance + code quality) before merging. <!-- AGI-INTEGRATION-END -->
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.