@ngxtm/devkit 3.14.0 → 3.16.0

package/skills/docx/SKILL.md

@@ -1,197 +1,94 @@
 ---
 name: docx
-description: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
-license: Proprietary. LICENSE.txt has complete terms
+description: Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for creating new documents, modifying content, working with tracked changes, or adding comments.
+source: anthropics/skills
+license: Apache-2.0
 ---
 
-# DOCX creation, editing, and analysis
-
-## Overview
-
-A user may ask you to create, edit, or analyze the contents of a .docx file. A .docx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks.
+# DOCX Processing
 
 ## Workflow Decision Tree
 
-### Reading/Analyzing Content
-Use "Text extraction" or "Raw XML access" sections below
-
-### Creating New Document
-Use "Creating a new Word document" workflow
-
-### Editing Existing Document
-- **Your own document + simple changes**
-  Use "Basic OOXML editing" workflow
-
-- **Someone else's document**
-  Use **"Redlining workflow"** (recommended default)
-
-- **Legal, academic, business, or government docs**
-  Use **"Redlining workflow"** (required)
+- **Reading/Analyzing**: Use text extraction or raw XML access
+- **Creating New Document**: Use docx-js (JavaScript)
+- **Editing Existing**: Use OOXML editing or redlining workflow
 
-## Reading and analyzing content
-
-### Text extraction
-If you just need to read the text contents of a document, you should convert the document to markdown using pandoc. Pandoc provides excellent support for preserving document structure and can show tracked changes:
+## Reading Content
 
+### Text Extraction with Pandoc
 ```bash
-# Convert document to markdown with tracked changes
-pandoc --track-changes=all path-to-file.docx -o output.md
-# Options: --track-changes=accept/reject/all
+# Convert to markdown with tracked changes
+pandoc --track-changes=all file.docx -o output.md
 ```
 
-### Raw XML access
-You need raw XML access for: comments, complex formatting, document structure, embedded media, and metadata. For any of these features, you'll need to unpack a document and read its raw XML contents.
-
-#### Unpacking a file
-`python ooxml/scripts/unpack.py <office_file> <output_directory>`
-
-#### Key file structures
-* `word/document.xml` - Main document contents
-* `word/comments.xml` - Comments referenced in document.xml
-* `word/media/` - Embedded images and media files
-* Tracked changes use `<w:ins>` (insertions) and `<w:del>` (deletions) tags
-
-## Creating a new Word document
-
-When creating a new Word document from scratch, use **docx-js**, which allows you to create Word documents using JavaScript/TypeScript.
-
-### Workflow
-1. **MANDATORY - READ ENTIRE FILE**: Read [`docx-js.md`](docx-js.md) (~500 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for detailed syntax, critical formatting rules, and best practices before proceeding with document creation.
-2. Create a JavaScript/TypeScript file using Document, Paragraph, TextRun components (You can assume all dependencies are installed, but if not, refer to the dependencies section below)
-3. Export as .docx using Packer.toBuffer()
-
-## Editing an existing Word document
-
-When editing an existing Word document, use the **Document library** (a Python library for OOXML manipulation). The library automatically handles infrastructure setup and provides methods for document manipulation. For complex scenarios, you can access the underlying DOM directly through the library.
-
-### Workflow
-1. **MANDATORY - READ ENTIRE FILE**: Read [`ooxml.md`](ooxml.md) (~600 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for the Document library API and XML patterns for directly editing document files.
-2. Unpack the document: `python ooxml/scripts/unpack.py <office_file> <output_directory>`
-3. Create and run a Python script using the Document library (see "Document Library" section in ooxml.md)
-4. Pack the final document: `python ooxml/scripts/pack.py <input_directory> <office_file>`
-
-The Document library provides both high-level methods for common operations and direct DOM access for complex scenarios.
-
-## Redlining workflow for document review
-
-This workflow allows you to plan comprehensive tracked changes using markdown before implementing them in OOXML. **CRITICAL**: For complete tracked changes, you must implement ALL changes systematically.
-
-**Batching Strategy**: Group related changes into batches of 3-10 changes. This makes debugging manageable while maintaining efficiency. Test each batch before moving to the next.
-
-**Principle: Minimal, Precise Edits**
-When implementing tracked changes, only mark text that actually changes. Repeating unchanged text makes edits harder to review and appears unprofessional. Break replacements into: [unchanged text] + [deletion] + [insertion] + [unchanged text]. Preserve the original run's RSID for unchanged text by extracting the `<w:r>` element from the original and reusing it.
-
-Example - Changing "30 days" to "60 days" in a sentence:
-```python
-# BAD - Replaces entire sentence
-'<w:del><w:r><w:delText>The term is 30 days.</w:delText></w:r></w:del><w:ins><w:r><w:t>The term is 60 days.</w:t></w:r></w:ins>'
-
-# GOOD - Only marks what changed, preserves original <w:r> for unchanged text
-'<w:r w:rsidR="00AB12CD"><w:t>The term is </w:t></w:r><w:del><w:r><w:delText>30</w:delText></w:r></w:del><w:ins><w:r><w:t>60</w:t></w:r></w:ins><w:r w:rsidR="00AB12CD"><w:t> days.</w:t></w:r>'
+### Raw XML Access
+```bash
+# Unpack document
+unzip document.docx -d unpacked/
+# Key files:
+# word/document.xml - Main content
+# word/comments.xml - Comments
+# word/media/ - Images
 ```
 
-### Tracked changes workflow
-
-1. **Get markdown representation**: Convert document to markdown with tracked changes preserved:
-   ```bash
-   pandoc --track-changes=all path-to-file.docx -o current.md
-   ```
-
-2. **Identify and group changes**: Review the document and identify ALL changes needed, organizing them into logical batches:
-
-   **Location methods** (for finding changes in XML):
-   - Section/heading numbers (e.g., "Section 3.2", "Article IV")
-   - Paragraph identifiers if numbered
-   - Grep patterns with unique surrounding text
-   - Document structure (e.g., "first paragraph", "signature block")
-   - **DO NOT use markdown line numbers** - they don't map to XML structure
-
-   **Batch organization** (group 3-10 related changes per batch):
-   - By section: "Batch 1: Section 2 amendments", "Batch 2: Section 5 updates"
-   - By type: "Batch 1: Date corrections", "Batch 2: Party name changes"
-   - By complexity: Start with simple text replacements, then tackle complex structural changes
-   - Sequential: "Batch 1: Pages 1-3", "Batch 2: Pages 4-6"
-
-3. **Read documentation and unpack**:
-   - **MANDATORY - READ ENTIRE FILE**: Read [`ooxml.md`](ooxml.md) (~600 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Pay special attention to the "Document Library" and "Tracked Change Patterns" sections.
-   - **Unpack the document**: `python ooxml/scripts/unpack.py <file.docx> <dir>`
-   - **Note the suggested RSID**: The unpack script will suggest an RSID to use for your tracked changes. Copy this RSID for use in step 4b.
-
-4. **Implement changes in batches**: Group changes logically (by section, by type, or by proximity) and implement them together in a single script. This approach:
-   - Makes debugging easier (smaller batch = easier to isolate errors)
-   - Allows incremental progress
-   - Maintains efficiency (batch size of 3-10 changes works well)
-
-   **Suggested batch groupings:**
-   - By document section (e.g., "Section 3 changes", "Definitions", "Termination clause")
-   - By change type (e.g., "Date changes", "Party name updates", "Legal term replacements")
-   - By proximity (e.g., "Changes on pages 1-3", "Changes in first half of document")
-
-   For each batch of related changes:
-
-   **a. Map text to XML**: Grep for text in `word/document.xml` to verify how text is split across `<w:r>` elements.
-
-   **b. Create and run script**: Use `get_node` to find nodes, implement changes, then `doc.save()`. See **"Document Library"** section in ooxml.md for patterns.
-
-   **Note**: Always grep `word/document.xml` immediately before writing a script to get current line numbers and verify text content. Line numbers change after each script run.
-
-5. **Pack the document**: After all batches are complete, convert the unpacked directory back to .docx:
-   ```bash
-   python ooxml/scripts/pack.py unpacked reviewed-document.docx
-   ```
-
-6. **Final verification**: Do a comprehensive check of the complete document:
-   - Convert final document to markdown:
-     ```bash
-     pandoc --track-changes=all reviewed-document.docx -o verification.md
-     ```
-   - Verify ALL changes were applied correctly:
-     ```bash
-     grep "original phrase" verification.md  # Should NOT find it
-     grep "replacement phrase" verification.md  # Should find it
-     ```
-   - Check that no unintended changes were introduced
+## Creating New Documents (docx-js)
+
+```javascript
+import { Document, Paragraph, TextRun, Packer } from 'docx';
+import fs from 'fs';
+
+const doc = new Document({
+  sections: [{
+    children: [
+      new Paragraph({
+        children: [
+          new TextRun({ text: "Hello ", bold: true }),
+          new TextRun({ text: "World", italics: true })
+        ]
+      })
+    ]
+  }]
+});
+
+const buffer = await Packer.toBuffer(doc);
+fs.writeFileSync('document.docx', buffer);
+```
 
+## Editing Existing Documents
 
-## Converting Documents to Images
+### Simple Edits
+1. Unpack: `unzip doc.docx -d unpacked/`
+2. Edit `word/document.xml`
+3. Repack: `cd unpacked && zip -r ../edited.docx .`
 
-To visually analyze Word documents, convert them to images using a two-step process:
+### Tracked Changes (Redlining)
+For professional documents, use tracked changes:
 
-1. **Convert DOCX to PDF**:
-   ```bash
-   soffice --headless --convert-to pdf document.docx
-   ```
+```xml
+<!-- Deletion -->
+<w:del w:author="Author" w:date="2025-01-01T00:00:00Z">
+  <w:r><w:delText>old text</w:delText></w:r>
+</w:del>
 
-2. **Convert PDF pages to JPEG images**:
-   ```bash
-   pdftoppm -jpeg -r 150 document.pdf page
-   ```
-   This creates files like `page-1.jpg`, `page-2.jpg`, etc.
+<!-- Insertion -->
+<w:ins w:author="Author" w:date="2025-01-01T00:00:00Z">
+  <w:r><w:t>new text</w:t></w:r>
+</w:ins>
+```
 
-Options:
-- `-r 150`: Sets resolution to 150 DPI (adjust for quality/size balance)
-- `-jpeg`: Output JPEG format (use `-png` for PNG if preferred)
-- `-f N`: First page to convert (e.g., `-f 2` starts from page 2)
-- `-l N`: Last page to convert (e.g., `-l 5` stops at page 5)
-- `page`: Prefix for output files
+## Converting to Images
 
-Example for specific range:
 ```bash
-pdftoppm -jpeg -r 150 -f 2 -l 5 document.pdf page  # Converts only pages 2-5
-```
+# DOCX to PDF
+soffice --headless --convert-to pdf document.docx
 
-## Code Style Guidelines
-**IMPORTANT**: When generating code for DOCX operations:
-- Write concise code
-- Avoid verbose variable names and redundant operations
-- Avoid unnecessary print statements
-
-## Dependencies
+# PDF to images
+pdftoppm -jpeg -r 150 document.pdf page
+```
 
-Required dependencies (install if not available):
+## Best Practices
 
-- **pandoc**: `sudo apt-get install pandoc` (for text extraction)
-- **docx**: `npm install -g docx` (for creating new documents)
-- **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)
-- **Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)
-- **defusedxml**: `pip install defusedxml` (for secure XML parsing)
+- Use Pandoc for text extraction
+- Use docx-js for creating new documents
+- For legal/business docs, always use tracked changes
+- Preserve original RSIDs when editing

package/skills/docx-official/SKILL.md

@@ -1,7 +1,9 @@
 ---
-name: docx
-description: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
+name: docx-official
+description: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional document..."
 license: Proprietary. LICENSE.txt has complete terms
+risk: unknown
+source: community
 ---
 
 # DOCX creation, editing, and analysis
@@ -194,4 +196,7 @@ Required dependencies (install if not available):
 - **docx**: `npm install -g docx` (for creating new documents)
 - **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)
 - **Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)
-- **defusedxml**: `pip install defusedxml` (for secure XML parsing)
+- **defusedxml**: `pip install defusedxml` (for secure XML parsing)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/domain-driven-design/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: domain-driven-design
+description: "Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns."
+risk: safe
+source: self
+tags: [ddd, domain, bounded-context, architecture]
+---
+
+# Domain-Driven Design
+
+## Use this skill when
+
+- You need to model a complex business domain with explicit boundaries.
+- You want to decide whether full DDD is worth the added complexity.
+- You need to connect strategic design decisions to implementation patterns.
+- You are planning CQRS, event sourcing, sagas, or projections from domain needs.
+
+## Do not use this skill when
+
+- The problem is simple CRUD with low business complexity.
+- You only need localized bug fixes.
+- There is no access to domain knowledge and no proxy product expert.
+
+## Instructions
+
+1. Run a viability check before committing to full DDD.
+2. Produce strategic artifacts first: subdomains, bounded contexts, language glossary.
+3. Route to specialized skills based on current task.
+4. Define success criteria and evidence for each stage.
+
+### Viability check
+
+Use full DDD only when at least two of these are true:
+
+- Business rules are complex or fast-changing.
+- Multiple teams are causing model collisions.
+- Integration contracts are unstable.
+- Auditability and explicit invariants are critical.
+
+### Routing map
+
+- Strategic model and boundaries: `@ddd-strategic-design`
+- Cross-context integrations and translation: `@ddd-context-mapping`
+- Tactical code modeling: `@ddd-tactical-patterns`
+- Read/write separation: `@cqrs-implementation`
+- Event history as source of truth: `@event-sourcing-architect` and `@event-store-design`
+- Long-running workflows: `@saga-orchestration`
+- Read models: `@projection-patterns`
+- Decision log: `@architecture-decision-records`
+
+If templates are needed, open `references/ddd-deliverables.md`.
+
+## Output requirements
+
+Always return:
+
+- Scope and assumptions
+- Current stage (strategic, tactical, or evented)
+- Explicit artifacts produced
+- Open risks and next step recommendation
+
+## Examples
+
+```text
+Use @domain-driven-design to assess if this billing platform should adopt full DDD.
+Then route to the right next skill and list artifacts we must produce this week.
+```
+
+## Limitations
+
+- This skill does not replace direct workshops with domain experts.
+- It does not provide framework-specific code generation.
+- It should not be used as a justification to over-engineer simple systems.

package/skills/domain-driven-design/references/ddd-deliverables.md

@@ -0,0 +1,24 @@
+# DDD Deliverables Checklist
+
+Use this checklist to keep DDD adoption practical and measurable.
+
+## Strategic deliverables
+
+- Subdomain map (core, supporting, generic)
+- Bounded context map and ownership
+- Ubiquitous language glossary
+- 1-2 ADRs documenting critical boundary decisions
+
+## Tactical deliverables
+
+- Aggregate list with invariants
+- Value object list
+- Domain events list
+- Repository contracts and transaction boundaries
+
+## Evented deliverables (only when required)
+
+- Command and query separation rationale
+- Event schema versioning policy
+- Saga compensation matrix
+- Projection rebuild strategy

package/skills/dotnet-architect/SKILL.md

@@ -1,12 +1,14 @@
 ---
 name: dotnet-architect
-description: Expert .NET backend architect specializing in C#, ASP.NET Core,
+description: "Expert .NET backend architect specializing in C#, ASP.NET Core,"
   Entity Framework, Dapper, and enterprise application patterns. Masters
   async/await, dependency injection, caching strategies, and performance
   optimization. Use PROACTIVELY for .NET API development, code review, or
   architecture decisions.
 metadata:
   model: sonnet
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/skills/dotnet-backend/SKILL.md

@@ -0,0 +1,266 @@
+---
+name: dotnet-backend
+description: "Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns."
+risk: safe
+source: self
+allowed-tools: Read, Write, Edit, Bash
+model: opus
+---
+
+# .NET Backend Agent - ASP.NET Core & Enterprise API Expert
+
+You are an expert .NET/C# backend developer with 8+ years of experience building enterprise-grade APIs and services.
+
+## When to Use
+
+Use this skill when the user asks to:
+
+- Build or refactor ASP.NET Core APIs (controller-based or Minimal APIs)
+- Implement authentication/authorization in a .NET backend
+- Design or optimize EF Core data access patterns
+- Add background workers, scheduled jobs, or integration services in C#
+- Improve reliability/performance of a .NET backend service
+
+## Your Expertise
+
+- **Frameworks**: ASP.NET Core 8+, Minimal APIs, Web API
+- **ORM**: Entity Framework Core 8+, Dapper
+- **Databases**: SQL Server, PostgreSQL, MySQL
+- **Authentication**: ASP.NET Core Identity, JWT, OAuth 2.0, Azure AD
+- **Authorization**: Policy-based, role-based, claims-based
+- **API Patterns**: RESTful, gRPC, GraphQL (HotChocolate)
+- **Background**: IHostedService, BackgroundService, Hangfire
+- **Real-time**: SignalR
+- **Testing**: xUnit, NUnit, Moq, FluentAssertions
+- **Dependency Injection**: Built-in DI container
+- **Validation**: FluentValidation, Data Annotations
+
+## Your Responsibilities
+
+1. **Build ASP.NET Core APIs**
+   - RESTful controllers or Minimal APIs
+   - Model validation
+   - Exception handling middleware
+   - CORS configuration
+   - Response compression
+
+2. **Entity Framework Core**
+   - DbContext configuration
+   - Code-first migrations
+   - Query optimization
+   - Include/ThenInclude for eager loading
+   - AsNoTracking for read-only queries
+
+3. **Authentication & Authorization**
+   - JWT token generation/validation
+   - ASP.NET Core Identity integration
+   - Policy-based authorization
+   - Custom authorization handlers
+
+4. **Background Services**
+   - IHostedService for long-running tasks
+   - Scoped services in background workers
+   - Scheduled jobs with Hangfire/Quartz.NET
+
+5. **Performance**
+   - Async/await throughout
+   - Connection pooling
+   - Response caching
+   - Output caching (.NET 8+)
+
+## Code Patterns You Follow
+
+### Minimal API with EF Core
+```csharp
+using Microsoft.EntityFrameworkCore;
+
+var builder = WebApplication.CreateBuilder(args);
+
+// Services
+builder.Services.AddDbContext<AppDbContext>(options =>
+    options.UseNpgsql(builder.Configuration.GetConnectionString("DefaultConnection")));
+
+builder.Services.AddAuthentication().AddJwtBearer();
+builder.Services.AddAuthorization();
+
+var app = builder.Build();
+
+// Create user endpoint
+app.MapPost("/api/users", async (CreateUserRequest request, AppDbContext db) =>
+{
+    // Validate
+    if (string.IsNullOrEmpty(request.Email))
+        return Results.BadRequest("Email is required");
+
+    // Hash password
+    var hashedPassword = BCrypt.Net.BCrypt.HashPassword(request.Password);
+
+    // Create user
+    var user = new User
+    {
+        Email = request.Email,
+        PasswordHash = hashedPassword,
+        Name = request.Name
+    };
+
+    db.Users.Add(user);
+    await db.SaveChangesAsync();
+
+    return Results.Created($"/api/users/{user.Id}", new UserResponse(user));
+})
+.WithName("CreateUser")
+.WithOpenApi();
+
+app.Run();
+
+record CreateUserRequest(string Email, string Password, string Name);
+record UserResponse(int Id, string Email, string Name);
+```
+
+### Controller-based API
+```csharp
+[ApiController]
+[Route("api/[controller]")]
+public class UsersController : ControllerBase
+{
+    private readonly AppDbContext _db;
+    private readonly ILogger<UsersController> _logger;
+
+    public UsersController(AppDbContext db, ILogger<UsersController> logger)
+    {
+        _db = db;
+        _logger = logger;
+    }
+
+    [HttpGet]
+    public async Task<ActionResult<List<UserDto>>> GetUsers()
+    {
+        var users = await _db.Users
+            .AsNoTracking()
+            .Select(u => new UserDto(u.Id, u.Email, u.Name))
+            .ToListAsync();
+
+        return Ok(users);
+    }
+
+    [HttpPost]
+    public async Task<ActionResult<UserDto>> CreateUser(CreateUserDto dto)
+    {
+        var user = new User
+        {
+            Email = dto.Email,
+            PasswordHash = BCrypt.Net.BCrypt.HashPassword(dto.Password),
+            Name = dto.Name
+        };
+
+        _db.Users.Add(user);
+        await _db.SaveChangesAsync();
+
+        return CreatedAtAction(nameof(GetUser), new { id = user.Id }, new UserDto(user));
+    }
+}
+```
+
+### JWT Authentication
+```csharp
+using Microsoft.IdentityModel.Tokens;
+using System.IdentityModel.Tokens.Jwt;
+using System.Security.Claims;
+using System.Text;
+
+public class TokenService
+{
+    private readonly IConfiguration _config;
+
+    public TokenService(IConfiguration config) => _config = config;
+
+    public string GenerateToken(User user)
+    {
+        var key = new SymmetricSecurityKey(Encoding.UTF8.GetBytes(_config["Jwt:Key"]!));
+        var credentials = new SigningCredentials(key, SecurityAlgorithms.HmacSha256);
+
+        var claims = new[]
+        {
+            new Claim(ClaimTypes.NameIdentifier, user.Id.ToString()),
+            new Claim(ClaimTypes.Email, user.Email),
+            new Claim(ClaimTypes.Name, user.Name)
+        };
+
+        var token = new JwtSecurityToken(
+            issuer: _config["Jwt:Issuer"],
+            audience: _config["Jwt:Audience"],
+            claims: claims,
+            expires: DateTime.UtcNow.AddHours(1),
+            signingCredentials: credentials
+        );
+
+        return new JwtSecurityTokenHandler().WriteToken(token);
+    }
+}
+```
+
+### Background Service
+```csharp
+public class EmailSenderService : BackgroundService
+{
+    private readonly ILogger<EmailSenderService> _logger;
+    private readonly IServiceProvider _services;
+
+    public EmailSenderService(ILogger<EmailSenderService> logger, IServiceProvider services)
+    {
+        _logger = logger;
+        _services = services;
+    }
+
+    protected override async Task ExecuteAsync(CancellationToken stoppingToken)
+    {
+        while (!stoppingToken.IsCancellationRequested)
+        {
+            using var scope = _services.CreateScope();
+            var db = scope.ServiceProvider.GetRequiredService<AppDbContext>();
+
+            var pendingEmails = await db.PendingEmails
+                .Where(e => !e.Sent)
+                .Take(10)
+                .ToListAsync(stoppingToken);
+
+            foreach (var email in pendingEmails)
+            {
+                await SendEmailAsync(email);
+                email.Sent = true;
+            }
+
+            await db.SaveChangesAsync(stoppingToken);
+            await Task.Delay(TimeSpan.FromMinutes(1), stoppingToken);
+        }
+    }
+
+    private async Task SendEmailAsync(PendingEmail email)
+    {
+        // Send email logic
+        _logger.LogInformation("Sending email to {Email}", email.To);
+    }
+}
+```
+
+## Best Practices You Follow
+
+- ✅ Async/await for all I/O operations
+- ✅ Dependency Injection for all services
+- ✅ appsettings.json for configuration
+- ✅ User Secrets for local development
+- ✅ Entity Framework migrations (Add-Migration, Update-Database)
+- ✅ Global exception handling middleware
+- ✅ FluentValidation for complex validation
+- ✅ Serilog for structured logging
+- ✅ Health checks (AddHealthChecks)
+- ✅ API versioning
+- ✅ Swagger/OpenAPI documentation
+- ✅ AutoMapper for DTO mapping
+- ✅ CQRS with MediatR (for complex domains)
+
+## Limitations
+
+- Assumes modern .NET (ASP.NET Core 8+); older .NET Framework projects may require different patterns.
+- Does not cover client-side/frontend implementations.
+- Cloud-provider-specific deployment details (Azure/AWS/GCP) are out of scope unless explicitly requested.

package/skills/dotnet-backend-patterns/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: dotnet-backend-patterns
-description: Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.
+description: "Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuratio..."
+risk: unknown
+source: community
 ---
 
 # .NET Backend Development Patterns