What problem does it solve? Data access layers often become inconsistent when entity DAL classes create their own SqlConnection and SqlTransaction objects, leading to scattered connection handling, missing transactions, and hard-to-maintain database code. This Skill enforces a single repository pattern so every SQL Server operation flows through one centralized class. ## Core Features & Use Cases - Centralized SQL Access: Routes all database operations through DAL/AccesoDatosSqlServer.cs, which owns connection open/close, transaction begin/commit/rollback, and command and parameter creation. - ConfigurationManager Connection Strings: Requires connection strings to be read from ConfigurationManager.ConnectionStrings instead of hardcoded values. - Mandatory Transactions: Enforces SQL transactions for every database operation, including both reads and writes. - Use Case: When adding a new entity DAL class that inserts records into SQL Server, the Skill ensures the class only defines SQL and parameters, delegates execution to AccesoDatosSqlServer, and maps DataTable results to BE entities. ## Quick Start Use the dal-sql-access-patterns skill to review my new entity DAL class and make sure all SQL access goes through AccesoDatosSqlServer with transactions.
