persistence-shared-infrastructure-dotnet10

Manage shared database connections and Dapper usage in .NET applications.

3|1|Updated Apr 17, 2026

Search Tags:#persistence #dotnet #dapper #database access #shared infrastructure

Ready to run

npx skills add https://github.com/diegoknsk/workflow-work-ia --skill persistence-shared-infrastructure-dotnet10

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: persistence-shared-infrastructure-dotnet10
Source: https://github.com/diegoknsk/workflow-work-ia/tree/main/skills/persistence-shared-infrastructure-dotnet10
Command: npx skills add https://github.com/diegoknsk/workflow-work-ia --skill persistence-shared-infrastructure-dotnet10

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenges of implementing efficient database persistence in .NET applications by providing shared infrastructure and Dapper patterns.

Core Features & Use Cases

Shared Persistence Infrastructure: Leverages existing internal infrastructure for database connections, unit of work, and repositories.
Dapper Standardization: Enforces the use of Dapper as the default ORM for data access.
Connection Strategy Flexibility: Supports both shared internal databases and separate databases for isolation.
Use Case: When building a .NET application that requires a robust and scalable data access layer, this Skill can be used to quickly set up and manage database operations without duplicating common infrastructure.

Quick Start

Run the script to create a new database connection using the shared infrastructure.

Frequently Asked Questions about persistence-shared-infrastructure-dotnet10

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up shared database connection management in .NET using Dapper?▼

Dapper standardization for .NET persistence is achieved by enforcing Dapper as the default ORM for data access within a shared infrastructure layer. This approach standardizes database operations and repository patterns, preventing duplicated persistence code across your application.

When do I need shared persistence infrastructure for .NET applications?▼

This shared persistence infrastructure supports flexible connection strategies for both shared internal databases and separate external databases for isolation. You can configure the connection strategy to target either environment based on your application's specific data isolation requirements.

Can I use this shared infrastructure with separate external databases for isolation?▼

You need shared persistence infrastructure when building a .NET application that requires a robust and scalable data access layer. It solves the problem of duplicated infrastructure by providing standardized database connections, unit of work, and repository management for both internal and external databases.

What is the best way to standardize Dapper usage across a .NET application?▼

The best way to standardize Dapper usage is by leveraging a shared persistence infrastructure that enforces Dapper as the default ORM. This provides standardized database connection management, unit of work, and repository patterns to prevent duplicated data access code.

Does this .NET persistence infrastructure support both internal and external databases?▼

Yes, this .NET persistence infrastructure supports both internal and external databases through flexible connection strategies. It is optimized for applications that require a shared persistence layer while maintaining the ability to isolate data access in separate external databases.