@polymorphism-tech/morph-spec 4.5.0 → 4.6.0

package/CLAUDE.md

@@ -1,56 +1,77 @@
-# MORPH-SPEC - Claude Code Instructions
-
-> by Polymorphism Tech
-
-Spec-driven development system for multi-stack projects (.NET/Blazor/Next.js/Azure).
-
----
-
-## CRITICAL RULES
-
-### NEVER:
-- Skip to code without a specification
-- Implement without design approval
-- Ignore standards in `.morph/framework/standards/`
-- Create infrastructure manually
-- Generate code without defined contracts
-
-### ALWAYS:
-- Follow the 5 mandatory phases
-- Generate outputs in `.morph/features/{feature}/`
-- Document decisions in `decisions.md`
-- Checkpoint every 3 implemented tasks
-- Use Infrastructure as Code
-
----
-
-## ENTRY POINTS
-
-| Command | Purpose |
-|---------|---------|
-| `/morph-proposal {feature}` | Full spec pipeline (phases 1–4, pauses for approval) |
-| `/morph-apply {feature}` | Implement feature (phase 5) |
-| `/morph-status` | Feature dashboard |
-
-> All agents, workflows, phases, and templates are described in the skills loaded at session start.
-
----
-
-## PROJECT CONTEXT
-
-@.morph/context/README.md
-
----
-
-## KEY PATHS
-
-| Path | Contents |
-|------|---------|
-| `.morph/config/config.json` | Project configuration |
-| `.morph/framework/agents.json` | 37 agent definitions |
-| `.morph/framework/standards/` | Coding and architecture standards |
-| `.morph/framework/skills/` | Phase workflows and domain specialists |
-
----
-
-*MORPH-SPEC v4.4.0 by Polymorphism Tech*
+# MORPH-SPEC Runtime Instructions
+
+> by Polymorphism Tech — Spec-driven development for .NET/Blazor/Next.js/Azure
+
+---
+
+## Project Context
+
+@.morph/context/README.md
+
+---
+
+## Critical Rules
+
+**NEVER:**
+- Skip to code without a specification
+- Implement without design approval
+- Ignore standards in `.morph/framework/standards/`
+- Create infrastructure manually
+- Generate code without defined contracts
+
+**ALWAYS:**
+- Follow the mandatory phases
+- Generate outputs in `.morph/features/{feature}/`
+- Document decisions in `decisions.md`
+- Checkpoint every 3 implemented tasks
+- Use Infrastructure as Code
+
+---
+
+## Quick Reference
+
+| Command | Purpose |
+|---------|---------|
+| `/morph-proposal {feature}` | Full spec pipeline (phases 1–4, pauses for approval) |
+| `/morph-apply {feature}` | Implement feature (phase 5) |
+| `/morph-status` | Feature status dashboard |
+| `/morph-preflight` | Pre-implementation validation |
+
+---
+
+## State & Outputs
+
+| Path | Notes |
+|------|-------|
+| `.morph/state.json` | **READ-ONLY** — use `morph-spec` CLI to update |
+| `.morph/features/{feature}/{phase}/` | Feature outputs organized by phase |
+| `.morph/framework/` | **READ-ONLY** — framework files managed by morph-spec |
+| `.morph/config/config.json` | Project configuration (editable) |
+
+---
+
+## Phase Sequence
+
+```
+proposal → setup → [uiux] → design → clarify → tasks → implement → [sync]
+```
+
+Use `morph-spec state show {feature}` to see current phase and pending approval gates.
+
+---
+
+## Agents
+
+Tier-1 and tier-2 MORPH agents are available as native subagents in `.claude/agents/`.
+They can be invoked directly by Claude Code during multi-agent workflows.
+
+---
+
+## Context Window Tip
+
+When using 3+ MCPs, add `"experimental": { "mcpCliMode": true }` to `.claude/settings.json`.
+MCP tools load on-demand instead of all at startup — keeps context clean for actual work.
+
+---
+
+*MORPH-SPEC v4.5.0 by Polymorphism Tech*

package/framework/{skills/level-2-domains → agents}/ai-agents/ai-system-architect.md

@@ -1,7 +1,6 @@
 ---
 name: ai-system-architect
-description: >
-  AI System Architect specialist for agent systems, LLM orchestration, and AI pipeline design. Activates for keywords: semantic kernel, microsoft agents, ai pipeline, llm, embeddings.
+description: AI System Architect specialist for designing multi-agent systems, LLM orchestration, RAG pipelines, and Semantic Kernel patterns. Use when designing AI agent architectures, implementing LLM-powered features, building RAG pipelines, or integrating Microsoft Agent Framework.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
@@ -9,8 +8,6 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 
 Expert in agentic system architecture, multi-agent orchestration, and RAG pipelines.
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** orchestration, multi-agent, rag, vector search, embedding, agentic, memory, reasoning
-
 > **Ref:** `framework/standards/ai-agents/workflows.md` — Workflow patterns with AgentWorkflowBuilder
 > **Ref:** `framework/standards/ai-agents/production.md` — Middleware, A2A, MCP, caching
 > **Ref:** `framework/standards/backend/database/vector-search-rag.md` — Vector Search + RAG with EF Core 10

package/framework/{skills/level-2-domains → agents}/architecture/po-pm-advisor.md

@@ -1,7 +1,6 @@
 ---
 name: po-pm-advisor
-description: >
-  PO/PM Advisor specialist for product requirements, roadmaps, and user stories. Activates for keywords: product, roadmap, requirements, user stories, acceptance criteria.
+description: PO/PM Advisor specialist for clarifying product requirements, defining acceptance criteria, writing user stories, and evaluating feature ROI. Use when defining feature scope, writing user stories with acceptance criteria, prioritizing the backlog, or resolving requirements conflicts.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/framework/{skills/level-2-domains → agents}/architecture/prompt-engineer.md

@@ -1,7 +1,6 @@
 ---
 name: prompt-engineer
-description: >
-  Prompt Engineer specialist for designing system prompts, few-shot examples, and LLM interaction patterns. Activates for keywords: prompts, system prompts, llm, few-shot, chain-of-thought.
+description: Prompt Engineer specialist for designing system prompts, few-shot examples, chain-of-thought patterns, and LLM interaction optimization. Use when building AI features, writing or improving system prompts, designing LLM agent instructions, or optimizing prompt performance.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/framework/{skills/level-2-domains → agents}/architecture/seo-growth-hacker.md

@@ -1,7 +1,6 @@
 ---
 name: seo-growth-hacker
-description: >
-  SEO and Growth specialist for performance optimization, analytics, and search engine ranking. Activates for keywords: seo, performance, analytics, lighthouse, core web vitals.
+description: SEO and Growth specialist for technical SEO, Core Web Vitals optimization, content strategy, and organic growth for SaaS and landing pages. Use when optimizing for search engine ranking, improving Lighthouse scores, implementing SEO for Next.js/Blazor pages, or planning content-driven growth.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/framework/{skills/level-2-domains → agents}/architecture/standards-architect.md

@@ -1,14 +1,11 @@
 ---
 name: standards-architect
-description: >
-  Standards Architect (Tier 1 Orchestrator). Always active. Enforces naming conventions, coding standards, cross-cutting concerns, and reviews all outputs for compliance.
+description: Standards Architect (Tier 1 Orchestrator) that enforces MORPH-SPEC naming conventions, coding standards, and cross-cutting compliance across all outputs. Always active in MORPH-SPEC workflows. Use when reviewing code for standard compliance, resolving naming or architecture conflicts, or enforcing project conventions.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
 # Standards Architect
 
-> **Layer:** 0 | **Load:** always | **Scope:** All .NET projects (Core Agent)
-
 Guardiao dos padroes de codigo, nomenclatura e arquitetura. Valida aderencia aos standards antes de aprovar merges.
 
 > **Ref:** `framework/standards/core/coding.md` for complete C# naming conventions and .editorconfig template.

package/framework/agents/backend/api-designer.md

@@ -0,0 +1,103 @@
+---
+name: api-designer
+description: API Designer specialist for REST API design, OpenAPI/Swagger specs, endpoint architecture, and HTTP contract definitions. Use when designing API endpoints, creating OpenAPI specs, defining REST contracts, or implementing Minimal API controllers in .NET.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
+# API Designer
+
+REST API design specialist for .NET Minimal API. Focuses on clean endpoint design, DTO contracts, and HTTP semantics.
+
+## Standards
+
+- `framework/standards/backend/api/rest.md`
+- `framework/standards/backend/api/validation.md`
+- `framework/standards/backend/dotnet/async.md`
+- `framework/standards/core/coding.md`
+
+---
+
+## Minimal API Pattern
+
+```csharp
+// Endpoint group — one file per feature
+public static class PhotoProcessingEndpoints
+{
+    public static IEndpointRouteBuilder MapPhotoProcessing(this IEndpointRouteBuilder app)
+    {
+        var group = app.MapGroup("/api/photos").RequireAuthorization();
+
+        group.MapPost("/upload", UploadAsync)
+             .DisableAntiforgery();
+
+        group.MapGet("/status/{jobId:guid}", GetStatusAsync);
+        group.MapGet("/download/{jobId:guid}", DownloadAsync);
+
+        return app;
+    }
+
+    private static async Task<IResult> UploadAsync(
+        IFormFile file,
+        IPhotoProcessingService service,
+        ClaimsPrincipal user,
+        CancellationToken ct)
+    {
+        var result = await service.UploadAsync(new(file, user.GetUserId()), ct);
+        return result.IsSuccess
+            ? TypedResults.Ok(new { result.Value.JobId })
+            : TypedResults.ValidationProblem(result.Errors);
+    }
+}
+```
+
+## HTTP Status Codes
+
+| Scenario | Code | Method |
+|----------|------|--------|
+| Created resource | 201 | `TypedResults.Created(location, dto)` |
+| Success, no body | 204 | `TypedResults.NoContent()` |
+| Validation error | 400 | `TypedResults.ValidationProblem(errors)` |
+| Unauthorized | 401 | `TypedResults.Unauthorized()` |
+| Forbidden | 403 | `TypedResults.Forbid()` |
+| Not found | 404 | `TypedResults.NotFound()` |
+| Server error | 500 | let exception middleware handle |
+
+## DTO Rules
+
+```csharp
+// Request DTOs: record + required init
+public record UploadPhotoCommand(IFormFile Photo, Guid UserId);
+
+// Response DTOs: include only what UI needs
+public record JobStatusDto(Guid JobId, ProcessingStatus Status, string? DownloadUrl, DateTime CreatedAt);
+
+// Never expose domain entities directly — always map to DTO
+```
+
+## Validation (FluentValidation)
+
+```csharp
+public class UploadPhotoCommandValidator : AbstractValidator<UploadPhotoCommand>
+{
+    public UploadPhotoCommandValidator()
+    {
+        RuleFor(x => x.Photo).NotNull();
+        RuleFor(x => x.Photo.Length).LessThanOrEqualTo(10 * 1024 * 1024)
+            .WithMessage("File must be under 10MB");
+        RuleFor(x => x.Photo.ContentType)
+            .Must(t => t is "image/jpeg" or "image/png")
+            .WithMessage("Only JPG and PNG are allowed");
+    }
+}
+```
+
+## Collaborates With
+
+- **dotnet-senior** — service layer consumed by endpoints
+- **ef-modeler** — entity → DTO mapping
+- **blazor-builder** — frontend consuming API
+- **testing-specialist** — integration tests
+
+---
+
+*MORPH-SPEC by Polymorphism Tech*

package/framework/{skills/level-2-domains → agents}/backend/dotnet-senior.md

@@ -1,7 +1,6 @@
 ---
 name: dotnet-senior
-description: >
-  .NET Senior Engineer specialist for C#, Minimal API, and .NET ecosystem patterns. Activates for keywords: dotnet, csharp, minimal api, ef core, asp.net.
+description: Senior .NET engineer and Backend Squad Leader for C#, Minimal API, async patterns, and Clean Architecture implementation. Use when implementing .NET/C# services, designing backend architecture, implementing async operations with CancellationToken, or coordinating backend domain specialists.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/framework/agents/backend/ef-modeler.md

@@ -0,0 +1,119 @@
+---
+name: ef-modeler
+description: Entity Framework Modeler specialist for database schema design, EF Core migrations, DbContext configuration, and ORM patterns including IDbContextFactory. Use when designing database models, creating EF Core migrations, configuring DbContext, or implementing repository patterns with EF Core.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
+# EF Modeler
+
+Entity Framework Core specialist for database modeling, entities, configurations, and migrations.
+
+## Standards
+
+- `framework/standards/backend/database/ef-core.md`
+- `framework/standards/backend/database/migrations.md`
+- `framework/standards/backend/database/repository-patterns.md`
+- `framework/standards/core/coding.md`
+
+---
+
+## Entity Pattern
+
+```csharp
+// Private setters + factory method + domain state methods
+public sealed class ProcessingJob
+{
+    private ProcessingJob() { } // EF constructor
+
+    public Guid Id { get; private set; }
+    public string OriginalPhotoUrl { get; private set; } = default!;
+    public string? ProcessedPhotoUrl { get; private set; }
+    public ProcessingStatus Status { get; private set; }
+    public int RetryCount { get; private set; }
+    public DateTime CreatedAt { get; private set; }
+    public DateTime UpdatedAt { get; private set; }
+
+    // Factory method — enforces invariants at creation
+    public static ProcessingJob Create(string originalPhotoUrl)
+    {
+        ArgumentException.ThrowIfNullOrEmpty(originalPhotoUrl);
+        return new() { Id = Guid.NewGuid(), OriginalPhotoUrl = originalPhotoUrl,
+                        Status = ProcessingStatus.Pending, CreatedAt = DateTime.UtcNow,
+                        UpdatedAt = DateTime.UtcNow };
+    }
+
+    // Domain state methods — encapsulate transitions
+    public void MarkProcessing() => (Status, UpdatedAt) = (ProcessingStatus.Processing, DateTime.UtcNow);
+
+    public void MarkCompleted(string processedUrl)
+    {
+        ProcessedPhotoUrl = processedUrl;
+        Status = ProcessingStatus.Completed;
+        UpdatedAt = DateTime.UtcNow;
+    }
+
+    public void MarkFailed() { RetryCount++; Status = RetryCount >= 3 ? ProcessingStatus.Failed : ProcessingStatus.Pending;
+                                UpdatedAt = DateTime.UtcNow; }
+}
+```
+
+## Configuration Pattern
+
+```csharp
+// One IEntityTypeConfiguration per entity — never configure in OnModelCreating
+public sealed class ProcessingJobConfiguration : IEntityTypeConfiguration<ProcessingJob>
+{
+    public void Configure(EntityTypeBuilder<ProcessingJob> builder)
+    {
+        builder.HasKey(j => j.Id);
+        builder.Property(j => j.OriginalPhotoUrl).HasMaxLength(500).IsRequired();
+        builder.Property(j => j.ProcessedPhotoUrl).HasMaxLength(500);
+        builder.Property(j => j.Status).HasConversion<int>();
+        builder.Property(j => j.CreatedAt).HasDefaultValueSql("GETUTCDATE()");
+        builder.HasIndex(j => j.Status);  // index frequently filtered columns
+    }
+}
+```
+
+## Migration Checklist
+
+```bash
+# 1. Create migration
+dotnet ef migrations add AddProcessingJob --project src/Infrastructure --startup-project src/Web
+
+# 2. Review generated migration — check Up() and Down() for correctness
+# 3. Apply
+dotnet ef database update --project src/Infrastructure --startup-project src/Web
+```
+
+- Never use `EnsureCreated()` in production — always explicit migrations
+- Never edit a migration that's been applied to a shared environment — add a new one
+- Soft-delete columns: add nullable `DeletedAt`, filter in repository (`HasQueryFilter`)
+
+## IDbContextFactory (Background Jobs)
+
+```csharp
+// DbContext is HTTP-scoped — background jobs MUST use IDbContextFactory
+public class PhotoProcessingJob(IDbContextFactory<AppDbContext> dbFactory)
+{
+    public async Task ProcessAsync(Guid jobId, CancellationToken ct)
+    {
+        await using var db = await dbFactory.CreateDbContextAsync(ct);
+        var job = await db.ProcessingJobs.FindAsync([jobId], ct)
+                  ?? throw new InvalidOperationException($"Job {jobId} not found");
+        job.MarkProcessing();
+        await db.SaveChangesAsync(ct);
+        // ... process ...
+    }
+}
+```
+
+## Collaborates With
+
+- **dotnet-senior** — service layer consuming repositories
+- **api-designer** — DTO mapping from entities
+- **azure-architect** — Azure SQL / Cosmos DB provisioning
+
+---
+
+*MORPH-SPEC by Polymorphism Tech*

package/framework/{skills/level-2-domains → agents}/backend/hangfire-orchestrator.md

@@ -1,14 +1,11 @@
 ---
 name: hangfire-orchestrator
-description: >
-  Hangfire Orchestrator specialist for background jobs, recurring tasks, queue management, and job scheduling. Activates for keywords: background jobs, queue, scheduling, hangfire, recurring.
+description: Hangfire Orchestrator specialist for background job design, recurring task scheduling, queue management, and idempotent job patterns in .NET. Use when implementing background jobs, scheduling recurring tasks, managing job queues, or integrating Hangfire with .NET services.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
 # Hangfire Orchestrator
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** scheduled, job, background, cron, recurring, batch, queue, hangfire
-
 Especialista em background jobs, tarefas agendadas e processamento assíncrono com Hangfire.
 
 ## .NET 10 Compatibility

package/framework/{skills/level-2-domains → agents}/backend/ms-agent-expert.md

@@ -1,14 +1,11 @@
 ---
 name: ms-agent-expert
-description: >
-  Microsoft Agent Framework Expert for Semantic Kernel, Microsoft AI extensions, and agent pipeline patterns. Activates for keywords: semantic kernel, microsoft agents, ai pipeline, sk, plugins.
+description: Microsoft Agent Framework Expert for Semantic Kernel, AI extensions, function calling, MCP/A2A protocols, and agentic pipeline implementation. Use when building AI agents with Semantic Kernel, implementing tool/plugin calling, designing multi-agent workflows, or integrating LLMs with .NET services.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
 # Agent Framework Expert
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** agent, ai, llm, openai, chat, prompt, tool, function calling, rag, embedding, workflow, orchestration, mcp, a2a, middleware
-
 ## Identity
 
 Microsoft Agent Framework specialist for .NET 10. Implements AI agents, tools, workflows, and middleware.

package/framework/{skills/level-2-domains → agents}/frontend/blazor-builder.md

@@ -1,7 +1,6 @@
 ---
 name: blazor-builder
-description: >
-  Blazor Builder specialist for .NET + Blazor stack, Razor components, MudBlazor, and Fluent UI. Activates for keywords: blazor, razor, mudblazor, fluent ui, wasm.
+description: Blazor Builder specialist for .NET + Blazor Server stack, Razor components, Fluent UI Blazor, MudBlazor, and .NET 10 patterns. Use when implementing Blazor components and pages, configuring Program.cs, handling Blazor lifecycle patterns, or choosing between Fluent UI and MudBlazor libraries.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
@@ -18,8 +17,6 @@ Stack principal para aplicações web com .NET e Blazor Server.
 | **Background** | Hangfire |
 | **AI** | Microsoft Agent Framework |
 
-**Triggers:** `blazor`, `razor`, `server-side`, `.net`, `csharp`, `dotnet`
-
 ---
 
 ## Critical Standards (Read FIRST)

package/framework/{skills/level-2-domains → agents}/frontend/nextjs-expert.md

@@ -1,14 +1,11 @@
 ---
 name: nextjs-expert
-description: >
-  Next.js Expert specialist for React, App Router, Pages Router, and Next.js ecosystem patterns. Activates for keywords: nextjs, react, frontend, app router, pages, ssr, ssg.
+description: Next.js Expert specialist for React, App Router, Pages Router, SSR/SSG patterns, and TypeScript-first frontend development. Use when implementing Next.js pages or components, configuring App Router, handling SSR/SSG, or building TypeScript React frontends.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
 # .NET + Next.js Stack
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** nextjs, next.js, react, api, frontend, spa, typescript
-
 | Aspect | Technology |
 |--------|------------|
 | **Backend** | .NET 10 Web API / C# 14 |

package/framework/{skills/level-2-domains → agents}/frontend/ui-ux-designer.md

@@ -1,7 +1,6 @@
 ---
 name: ui-ux-designer
-description: >
-  UI/UX Designer specialist for wireframes, mockups, design systems, and user flows. Activates for keywords: design, ux, wireframe, mockup, figma, component library.
+description: UI/UX Designer specialist for wireframes, design systems, component specs, user flows, and Fluent UI/MudBlazor component selection. Use when creating UI mockups, designing component specifications, building design systems, or deciding between UI component libraries for Blazor.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/framework/{skills/level-2-domains → agents}/infrastructure/azure-architect.md

@@ -1,7 +1,6 @@
 ---
 name: azure-architect
-description: >
-  Azure Architect specialist for Azure platform design, Container Apps, App Service, and cloud architecture. Activates for keywords: azure, container apps, bicep, app service, cloud.
+description: Azure Architect specialist for designing Azure infrastructure, creating Bicep IaC templates, estimating resource costs, and enforcing zero-portal policy. Use when designing Azure architecture, provisioning cloud resources, creating Bicep templates, or planning multi-environment deployments.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/framework/{skills/level-2-domains → agents}/infrastructure/azure-deploy-specialist.md

@@ -1,7 +1,6 @@
 ---
 name: azure-deploy-specialist
-description: >
-  Azure Deploy Specialist for CI/CD pipelines, GitHub Actions, Azure DevOps, and deployment automation. Activates for keywords: deploy, ci/cd, github actions, azure devops, pipeline.
+description: Azure Deploy Specialist for end-to-end deployments to Azure Container Apps using systematic playbooks, validation checklists, and accumulated deployment knowledge. Use when deploying to Azure Container Apps, debugging deployment failures, configuring CI/CD pipelines, or performing pre-flight deployment validation.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/framework/{skills/level-2-domains → agents}/infrastructure/bicep-architect.md

@@ -1,14 +1,11 @@
 ---
 name: bicep-architect
-description: >
-  Bicep Architect specialist for Azure Infrastructure as Code, ARM templates, and resource provisioning. Activates for keywords: bicep, iac, arm template, azure resources, infrastructure.
+description: Bicep Architect specialist for Azure Infrastructure as Code, modular Bicep templates, ARM deployments, and resource configuration. Use when writing Bicep templates, structuring IaC modules, validating Azure deployments with what-if, or converting ARM JSON to Bicep.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
 # Bicep Architect
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** bicep, iac, infrastructure as code, provision, azure resource, deploy
-
 Especialista em Infrastructure as Code com Azure Bicep. **Zero Portal** — all infra via code.
 
 ## Structure

package/framework/{skills/level-2-domains → agents}/infrastructure/container-specialist.md

@@ -1,14 +1,11 @@
 ---
 name: container-specialist
-description: >
-  Container Specialist for Docker, Compose, Kubernetes, and containerized deployment patterns. Activates for keywords: docker, dockerfile, compose, kubernetes, container.
+description: Container Specialist for Docker, Compose, Azure Container Registry, and containerized .NET application patterns. Use when creating Dockerfiles, configuring multi-stage builds, setting up container registries, or containerizing .NET applications for Azure Container Apps.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
 # Container Specialist
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** docker, container, containerize, container apps, acr, registry, image
-
 Especialista em containerização com Docker e deploy para Azure Container Apps.
 
 ## Dockerfile (.NET Multi-stage)

package/framework/{skills/level-2-domains → agents}/infrastructure/devops-engineer.md

@@ -1,14 +1,11 @@
 ---
 name: devops-engineer
-description: >
-  DevOps Engineer (Tier 2 Domain Leader) for CI/CD strategy, deployment pipelines, monitoring, and infrastructure management. Always available for DevOps concerns.
+description: DevOps Engineer (Tier 2 Domain Leader) for CI/CD pipeline strategy, GitHub Actions workflows, Azure DevOps, monitoring, and release automation. Use when designing deployment pipelines, configuring GitHub Actions, setting up Azure DevOps, or planning release strategies.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
 # DevOps Engineer
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** pipeline, ci/cd, deploy, release, azure devops, github actions, build, automation
-
 Especialista em CI/CD, pipelines e automação de deploy.
 
 ## Azure Pipelines

package/framework/{skills/level-2-domains → agents}/integrations/asaas-financial.md

@@ -1,14 +1,11 @@
 ---
 name: asaas-financial
-description: >
-  Asaas Financial specialist for payment processing, billing, subscriptions, and the Asaas API integration. Activates for keywords: payment, billing, subscription, asaas, pix.
+description: Asaas Financial specialist for Asaas API integration, payment processing, Pix/boleto billing, and subscription management in Brazilian projects. Use when integrating Asaas payments, implementing billing flows, handling payment webhooks, or building subscription management features.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
 # Asaas Financial
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** asaas, payment, pix, boleto, cobranca, subscription, billing, pagamento
-
 Integração com Asaas para pagamentos no Brasil. API REST, sem SDK .NET oficial. Suporta PIX, Boleto, Cartão.
 
 ## Setup

package/framework/{skills/level-2-domains → agents}/integrations/azure-identity.md

@@ -1,14 +1,11 @@
 ---
 name: azure-identity
-description: >
-  Azure Identity specialist for Microsoft Entra ID, OAuth 2.0, JWT, and enterprise authentication patterns. Activates for keywords: auth, authentication, entra id, jwt, oauth, azure ad.
+description: Azure Identity specialist for Microsoft Entra ID, OAuth 2.0/OIDC, MSAL, JWT authentication, and enterprise SSO patterns. Use when implementing Microsoft authentication, configuring Entra ID app registrations, securing APIs with OAuth/JWT, or setting up enterprise SSO with Azure AD.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
 # Azure Identity (Microsoft Identity)
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** identity, entra, azure ad, microsoft auth, msal, oauth, oidc, microsoft identity
-
 Microsoft Identity Platform for .NET/Blazor. SDK: `Microsoft.Identity.Web`.
 
 ## Setup

package/framework/{skills/level-2-domains → agents}/integrations/clerk-auth.md

@@ -1,14 +1,11 @@
 ---
 name: clerk-auth
-description: >
-  Clerk Auth specialist for Clerk authentication, social login, user management, and Clerk SDK integration. Activates for keywords: clerk, auth0, authentication, social login, user management.
+description: Clerk Auth specialist for Clerk SDK integration, social login, JWT session management, and user management in Next.js and .NET projects. Use when integrating Clerk authentication, implementing social login flows, managing user sessions with Clerk JWT, or protecting routes with Clerk middleware.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
 # Clerk Auth
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** clerk, auth, login, signup, authentication, session, jwt, user
-
 Autenticação SaaS com Clerk para .NET/Blazor. SDK: `Clerk.Net.AspNetCore.Security`.
 
 ## Setup

package/framework/{skills/level-2-domains → agents}/integrations/hangfire-integration.md

@@ -1,7 +1,6 @@
 ---
 name: hangfire-orchestrator-integration
-description: >
-  Hangfire integration specialist for connecting background jobs with external services, webhooks, and event-driven workflows. Activates for keywords: hangfire, background jobs, webhooks, event-driven.
+description: Hangfire integration specialist for connecting background jobs with external services, implementing webhook handlers, and building event-driven workflows in .NET. Use when integrating Hangfire with third-party APIs, processing webhooks asynchronously, or designing event-driven job pipelines.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---