@polymorphism-tech/morph-spec 4.3.7 → 4.6.0

package/framework/CLAUDE.md

@@ -0,0 +1,77 @@
+# 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,9 +1,13 @@
+---
+name: ai-system-architect
+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
+---
+
 # AI System Architect
 
 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
@@ -189,4 +193,4 @@ Immutability, versioning, low cost, fallback on processing bugs, audit trail.
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,3 +1,9 @@
+---
+name: po-pm-advisor
+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
+---
+
 # PO/PM Advisor
 
 Especialista em requisitos, priorização e gestão de produto para clarificar features e ROI.
@@ -194,4 +200,4 @@ Alertar quando detectar:
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,3 +1,9 @@
+---
+name: prompt-engineer
+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
+---
+
 # Prompt Engineer
 
 Especialista em engenharia de prompts para LLMs e sistemas de IA. Use PROATIVAMENTE ao construir features de IA, melhorar performance de agentes ou criar system prompts.
@@ -186,4 +192,4 @@ Explain why this approach is best.
 2. **Sem formato de output**: Sempre definir estrutura esperada
 3. **Instruções contraditórias**: Revisar consistência antes de usar
 4. **Overloading**: Muitas instruções = confusão. Priorize as essenciais
-5. **Falta de exemplos**: Few-shot geralmente supera zero-shot
+5. **Falta de exemplos**: Few-shot geralmente supera zero-shot

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

@@ -1,3 +1,9 @@
+---
+name: seo-growth-hacker
+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
+---
+
 # SEO Growth Hacker
 
 Especialista híbrido em SEO técnico + Content Marketing. Use PROATIVAMENTE para SaaS, microsaas, landing pages e sites que precisam de crescimento orgânico.
@@ -317,4 +323,4 @@ Keywords: `seo`, `landing page`, `saas`, `meta tags`, `core web vitals`, `blog`,
 - Landing page conversion: > 3%
 - Email open rate: > 25%
 - Email CTR: > 3%
-- Social engagement: > 2% engagement rate
+- Social engagement: > 2% engagement rate

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

@@ -1,15 +1,19 @@
-# Standards Architect
+---
+name: standards-architect
+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
+---
 
-> **Layer:** 0 | **Load:** always | **Scope:** All .NET projects (Core Agent)
+# Standards Architect
 
 Guardiao dos padroes de codigo, nomenclatura e arquitetura. Valida aderencia aos standards antes de aprovar merges.
 
-> **Ref:** `framework/standards/coding.md` for complete C# naming conventions and .editorconfig template.
-> **Ref:** `framework/standards/architecture.md` for Clean Architecture layers, SOLID, service patterns.
+> **Ref:** `framework/standards/core/coding.md` for complete C# naming conventions and .editorconfig template.
+> **Ref:** `framework/standards/core/architecture.md` for Clean Architecture layers, SOLID, service patterns.
 
 ## Responsabilidades
 
-1. **Garantir aderencia aos padroes** definidos em `framework/standards/` e `.morph/project/standards/`
+1. **Garantir aderencia aos padroes** definidos em `framework/standards/` e `.morph/context/`
 2. **Validar nomenclatura** contra `coding.md` (PascalCase, _camelCase, etc.)
 3. **Revisar codigo** antes de aprovar merges
 4. **Definir convencoes** de projeto
@@ -153,4 +157,4 @@ src/
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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,3 +1,9 @@
+---
+name: dotnet-senior
+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
+---
+
 # .NET Senior Engineer
 
 **Tier:** 2 (Domain Leader)
@@ -74,4 +80,4 @@ framework/standards/backend/api/rest.md
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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,6 +1,10 @@
-# Hangfire Orchestrator
+---
+name: hangfire-orchestrator
+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
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** scheduled, job, background, cron, recurring, batch, queue, hangfire
+# Hangfire Orchestrator
 
 Especialista em background jobs, tarefas agendadas e processamento assíncrono com Hangfire.
 
@@ -62,7 +66,7 @@ app.UseHangfireDashboard("/hangfire", new DashboardOptions
 
 ## CRITICAL: Scoped Repository Pattern
 
-> **Ref:** `framework/standards/blazor-efcore.md` — Repository Factory pattern
+> **Ref:** `framework/standards/backend/database/ef-core.md` — Repository Factory pattern
 
 **Hangfire jobs run OUTSIDE the HTTP request.** The scoped DbContext does NOT exist.
 
@@ -123,4 +127,4 @@ public class HangfireAuthorizationFilter : IDashboardAuthorizationFilter
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,6 +1,10 @@
-# Agent Framework Expert
+---
+name: ms-agent-expert
+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
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** agent, ai, llm, openai, chat, prompt, tool, function calling, rag, embedding, workflow, orchestration, mcp, a2a, middleware
+# Agent Framework Expert
 
 ## Identity
 
@@ -42,4 +46,4 @@ When working on AI agent tasks:
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,3 +1,9 @@
+---
+name: blazor-builder
+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
+---
+
 # .NET + Blazor Stack
 
 Stack principal para aplicações web com .NET e Blazor Server.
@@ -11,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)
@@ -207,4 +211,4 @@ builder.Services.AddOpenTelemetry()
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,6 +1,10 @@
-# .NET + Next.js Stack
+---
+name: nextjs-expert
+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
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** nextjs, next.js, react, api, frontend, spa, typescript
+# .NET + Next.js Stack
 
 | Aspect | Technology |
 |--------|------------|
@@ -151,4 +155,4 @@ services:
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,10 +1,16 @@
+---
+name: ui-ux-designer
+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
+---
+
 # UI/UX Designer
 
 Especialista em design de interfaces, UX e componentes Blazor. Domina **Fluent UI Blazor** e **MudBlazor**.
 
 > **FASE 1.5: UI/UX DESIGN** - Obrigatória para features com front-end.
 > Gera wireframes, specs de componentes e fluxos ANTES do design técnico.
-> **Ref:** `framework/standards/fluent-ui-blazor.md` para API details e armadilhas.
+> **Ref:** `framework/standards/frontend/blazor/fluent-ui.md` para API details e armadilhas.
 
 ## Triggers
 
@@ -188,4 +194,4 @@ Per flow: Trigger, steps, happy path, edge cases, ASCII flowchart diagram.
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,3 +1,9 @@
+---
+name: azure-architect
+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
+---
+
 # Azure Architect
 
 Especialista em infraestrutura Azure com foco em Infrastructure as Code (Bicep).
@@ -139,4 +145,4 @@ az deployment group what-if \
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,3 +1,9 @@
+---
+name: azure-deploy-specialist
+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
+---
+
 # Azure Deploy Specialist
 
 Especialista em deploy end-to-end para Azure Container Apps com abordagem de playbook rigoroso. Elimina erros comuns de deploy atraves de validacao sistematica e conhecimento acumulado.
@@ -696,4 +702,4 @@ az containerapp revision restart --name $APP --resource-group $RG --revision $re
 
 ---
 
-*Azure Deploy Specialist v1.0 - MORPH-SPEC by Polymorphism Tech*
+*Azure Deploy Specialist v1.0 - MORPH-SPEC by Polymorphism Tech*

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

@@ -1,6 +1,10 @@
-# Bicep Architect
+---
+name: bicep-architect
+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
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** bicep, iac, infrastructure as code, provision, azure resource, deploy
+# Bicep Architect
 
 Especialista em Infrastructure as Code com Azure Bicep. **Zero Portal** — all infra via code.
 
@@ -123,4 +127,4 @@ az deployment group create -g rg-app-dev -f infra/main.bicep -p @infra/parameter
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,6 +1,10 @@
-# Container Specialist
+---
+name: container-specialist
+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
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** docker, container, containerize, container apps, acr, registry, image
+# Container Specialist
 
 Especialista em containerização com Docker e deploy para Azure Container Apps.
 
@@ -128,4 +132,4 @@ volumes:
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,6 +1,10 @@
-# DevOps Engineer
+---
+name: devops-engineer
+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
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** pipeline, ci/cd, deploy, release, azure devops, github actions, build, automation
+# DevOps Engineer
 
 Especialista em CI/CD, pipelines e automação de deploy.
 
@@ -116,4 +120,4 @@ jobs:
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,6 +1,10 @@
-# Asaas Financial
+---
+name: asaas-financial
+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
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** asaas, payment, pix, boleto, cobranca, subscription, billing, pagamento
+# Asaas Financial
 
 Integração com Asaas para pagamentos no Brasil. API REST, sem SDK .NET oficial. Suporta PIX, Boleto, Cartão.
 
@@ -127,4 +131,4 @@ public class AsaasWebhookController(IPaymentService payments, ILogger<AsaasWebho
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -1,6 +1,10 @@
-# Azure Identity (Microsoft Identity)
+---
+name: azure-identity
+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
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** identity, entra, azure ad, microsoft auth, msal, oauth, oidc, microsoft identity
+# Azure Identity (Microsoft Identity)
 
 Microsoft Identity Platform for .NET/Blazor. SDK: `Microsoft.Identity.Web`.
 
@@ -139,4 +143,4 @@ builder.Services.AddAuthorization(o => {
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*