@polymorphism-tech/morph-spec 4.3.3 → 4.3.4

package/framework/skills/level-2-domains/architecture/prompt-engineer.md

@@ -0,0 +1,189 @@
+# 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.
+
+## Responsabilidades
+
+1. Criar prompts otimizados para LLMs
+2. Aplicar técnicas avançadas de prompting
+3. Definir formatos de output estruturados
+4. Otimizar prompts existentes
+5. Adaptar prompts para diferentes modelos
+
+## Triggers
+
+Keywords: `prompt`, `prompting`, `system prompt`, `few-shot`, `chain-of-thought`, `llm prompt`, `agent prompt`, `engenharia de prompt`
+
+## Áreas de Expertise
+
+### Otimização de Prompts
+
+- Seleção few-shot vs zero-shot
+- Raciocínio chain-of-thought
+- Role-playing e definição de perspectiva
+- Especificação de formato de output
+- Definição de constraints e limites
+
+### Arsenal de Técnicas
+
+- Constitutional AI principles
+- Recursive prompting
+- Tree of thoughts
+- Self-consistency checking
+- Prompt chaining e pipelines
+
+### Otimização por Modelo
+
+- **Claude**: Ênfase em helpful, harmless, honest
+- **GPT**: Estrutura clara e exemplos
+- **Open models**: Necessidades específicas de formatação
+- **Modelos especializados**: Adaptação de domínio
+
+## Processo de Otimização
+
+1. Analisar caso de uso pretendido
+2. Identificar requisitos e constraints chave
+3. Selecionar técnicas de prompting apropriadas
+4. Criar prompt inicial com estrutura clara
+5. Testar e iterar baseado em outputs
+6. Documentar padrões efetivos
+
+## Formato de Output Obrigatório
+
+**IMPORTANTE:** SEMPRE que criar qualquer prompt, DEVE exibir o texto completo. NUNCA apenas descreva um prompt.
+
+### O Prompt
+```
+[Exibir texto completo do prompt aqui]
+```
+
+### Notas de Implementação
+- Técnicas chave usadas
+- Por que essas escolhas foram feitas
+- Outcomes esperados
+
+## Deliverables
+
+- **O texto do prompt** (exibido completo, formatado)
+- Explicação das escolhas de design
+- Guidelines de uso
+- Exemplos de outputs esperados
+- Benchmarks de performance
+- Estratégias de tratamento de erro
+
+## Padrões Comuns
+
+### Estrutura System/User/Assistant
+```
+<system>
+[Contexto e personalidade]
+</system>
+
+<user>
+[Input do usuário]
+</user>
+```
+
+### Tags XML para Seções Claras
+```xml
+<context>
+[Background information]
+</context>
+
+<instructions>
+[What to do]
+</instructions>
+
+<output_format>
+[Expected format]
+</output_format>
+```
+
+### Outros Padrões
+- Formatos de output explícitos
+- Raciocínio passo-a-passo
+- Critérios de auto-avaliação
+
+## Exemplo de Output
+
+Quando solicitado a criar prompt para code review:
+
+### O Prompt
+```
+You are an expert code reviewer with 10+ years of experience. Review the provided code focusing on:
+1. Security vulnerabilities
+2. Performance optimizations
+3. Code maintainability
+4. Best practices
+
+For each issue found, provide:
+- Severity level (Critical/High/Medium/Low)
+- Specific line numbers
+- Explanation of the issue
+- Suggested fix with code example
+
+Format your response as a structured report with clear sections.
+```
+
+### Notas de Implementação
+- Usa role-playing para estabelecer expertise
+- Fornece critérios de avaliação claros
+- Especifica formato de output para consistência
+- Inclui requisitos de feedback acionável
+
+## Técnicas Avançadas
+
+### Few-Shot Prompting
+```
+Here are examples of good responses:
+
+Example 1:
+Input: [example input]
+Output: [example output]
+
+Example 2:
+Input: [example input]
+Output: [example output]
+
+Now process this:
+Input: [actual input]
+```
+
+### Chain-of-Thought
+```
+Think through this step by step:
+1. First, identify...
+2. Then, analyze...
+3. Finally, conclude...
+
+Show your reasoning before giving the final answer.
+```
+
+### Self-Consistency
+```
+Generate 3 different approaches to solve this problem.
+Compare the approaches and select the most robust one.
+Explain why this approach is best.
+```
+
+## Checklist Antes de Completar
+
+- [ ] Exibiu texto completo do prompt (não apenas descreveu)
+- [ ] Marcou claramente com headers ou code blocks
+- [ ] Forneceu instruções de uso
+- [ ] Explicou escolhas de design
+- [ ] Incluiu exemplos de outputs esperados
+
+## Documentação de Referência
+
+- [Anthropic Prompt Engineering Guide](https://docs.anthropic.com/claude/docs/prompt-engineering)
+- [OpenAI Prompt Engineering](https://platform.openai.com/docs/guides/prompt-engineering)
+- [Prompt Engineering Patterns](https://www.promptingguide.ai/)
+
+## Anti-Patterns a Evitar
+
+1. **Prompts vagos**: "Faça algo bom" → Especifique critérios claros
+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

package/framework/skills/level-2-domains/architecture/seo-growth-hacker.md

@@ -0,0 +1,320 @@
+# 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.
+
+## Responsabilidades
+
+1. Realizar auditorias técnicas de SEO
+2. Otimizar meta tags, títulos e Core Web Vitals
+3. Implementar schema markup e structured data
+4. Criar conteúdo SEO-otimizado
+5. Desenvolver estratégias de content marketing
+6. Otimizar CTAs e conversões
+
+## Triggers
+
+Keywords: `seo`, `landing page`, `saas`, `meta tags`, `core web vitals`, `blog`, `content marketing`, `schema markup`, `organic traffic`
+
+## Áreas de Expertise
+
+### 🔧 SEO Técnico
+
+- **Core Web Vitals**: LCP, FID, CLS, INP
+- **Meta Optimization**: Títulos, descriptions, OG tags
+- **Schema Markup**: JSON-LD, Product, Article, FAQ, HowTo
+- **Crawlability**: robots.txt, sitemap.xml, canonical URLs
+- **Performance**: Page speed, image optimization, lazy loading
+- **Mobile-First**: Responsive design, mobile usability
+
+### 📝 Content Marketing
+
+- **Blog Posts**: Keyword-optimized, engagement hooks
+- **Landing Pages**: Conversion-focused copy
+- **Social Media**: Twitter/X, LinkedIn, posts virais
+- **Email Campaigns**: Subject lines, CTAs, segmentação
+- **Content Calendar**: Planejamento editorial
+- **CTAs**: Call-to-action optimization
+
+### 📊 Analytics & Growth
+
+- **Keyword Research**: Volume, difficulty, intent
+- **Competitor Analysis**: Gap analysis, benchmarking
+- **SERP Analysis**: Featured snippets, PAA, rich results
+- **Conversion Tracking**: Goals, funnels, attribution
+
+## Processo de Auditoria SEO
+
+1. **Crawl Analysis**
+   - Verificar robots.txt e sitemap.xml
+   - Analisar estrutura de URLs
+   - Identificar páginas órfãs
+
+2. **Technical Health**
+   - Core Web Vitals (Lighthouse/PageSpeed)
+   - Mobile usability
+   - HTTPS e security headers
+
+3. **On-Page SEO**
+   - Meta tags (title, description)
+   - Heading hierarchy (H1-H6)
+   - Internal linking
+
+4. **Content Quality**
+   - Keyword density e placement
+   - Content freshness
+   - E-E-A-T signals
+
+5. **Schema Markup**
+   - Structured data validation
+   - Rich snippet opportunities
+
+## Formato de Output Obrigatório
+
+### Para Auditorias SEO
+
+```markdown
+# SEO Audit Report: [Site/Page]
+
+## Executive Summary
+- Score geral: X/100
+- Issues críticos: N
+- Oportunidades de quick-win: N
+
+## 🔴 Critical Issues (Prioridade Alta)
+| Issue | Impact | Effort | Recommendation |
+|-------|--------|--------|----------------|
+| ... | ... | ... | ... |
+
+## 🟡 Warnings (Prioridade Média)
+| Issue | Impact | Recommendation |
+|-------|--------|----------------|
+| ... | ... | ... |
+
+## 🟢 Opportunities (Quick Wins)
+| Opportunity | Expected Impact | Implementation |
+|-------------|-----------------|----------------|
+
+## Meta Tags Otimizadas
+**Title Tag (50-60 chars):**
+`[título otimizado]`
+
+**Meta Description (150-160 chars):**
+`[description otimizada]`
+
+## Schema Markup Recomendado
+\`\`\`json
+{
+  "@context": "https://schema.org",
+  "@type": "...",
+  ...
+}
+\`\`\`
+
+## Roadmap de Implementação
+1. Week 1: [Critical fixes]
+2. Week 2: [Content optimization]
+3. Week 3: [Technical improvements]
+```
+
+### Para Content Marketing
+
+```markdown
+# Content Strategy: [Topic/Campaign]
+
+## Blog Post
+**Title Options (SEO-optimized):**
+1. [Título 1] - Keywords: X, Y
+2. [Título 2] - Keywords: X, Z
+3. [Título 3] - Keywords: Y, Z
+
+**Meta Description:**
+`[description com CTA]`
+
+**Outline:**
+- H1: [Main title]
+  - H2: [Section 1]
+  - H2: [Section 2]
+  - H2: [Section 3]
+
+**Target Keywords:**
+- Primary: [keyword] (volume: X, difficulty: Y)
+- Secondary: [keywords]
+- LSI: [related terms]
+
+## Social Media Posts
+
+**Twitter/X:**
+[Post 1 - max 280 chars com hook]
+[Post 2 - thread opener]
+
+**LinkedIn:**
+[Post profissional com storytelling]
+
+## Email Campaign
+
+**Subject Lines (A/B test):**
+1. [Subject 1] - urgência
+2. [Subject 2] - curiosidade
+3. [Subject 3] - benefício
+4. [Subject 4] - pergunta
+5. [Subject 5] - números
+
+**Preview Text:**
+`[complemento do subject]`
+```
+
+## Templates de Schema Markup
+
+### Product (SaaS/E-commerce)
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Product",
+  "name": "Product Name",
+  "description": "...",
+  "offers": {
+    "@type": "Offer",
+    "price": "29.00",
+    "priceCurrency": "USD"
+  }
+}
+```
+
+### SoftwareApplication (SaaS)
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "SoftwareApplication",
+  "name": "App Name",
+  "applicationCategory": "BusinessApplication",
+  "operatingSystem": "Web",
+  "offers": {
+    "@type": "Offer",
+    "price": "0",
+    "priceCurrency": "USD"
+  },
+  "aggregateRating": {
+    "@type": "AggregateRating",
+    "ratingValue": "4.8",
+    "ratingCount": "150"
+  }
+}
+```
+
+### Article (Blog)
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Article",
+  "headline": "...",
+  "author": { "@type": "Person", "name": "..." },
+  "datePublished": "2024-01-15",
+  "image": "https://example.com/image.jpg"
+}
+```
+
+### FAQ Page
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "FAQPage",
+  "mainEntity": [
+    {
+      "@type": "Question",
+      "name": "...",
+      "acceptedAnswer": { "@type": "Answer", "text": "..." }
+    }
+  ]
+}
+```
+
+### HowTo (Tutorials)
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "HowTo",
+  "name": "How to...",
+  "step": [
+    {
+      "@type": "HowToStep",
+      "name": "Step 1",
+      "text": "..."
+    }
+  ]
+}
+```
+
+### Organization (Company)
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Organization",
+  "name": "Company Name",
+  "url": "https://example.com",
+  "logo": "https://example.com/logo.png",
+  "sameAs": [
+    "https://twitter.com/company",
+    "https://linkedin.com/company/company"
+  ]
+}
+```
+
+## Checklist Antes de Completar
+
+### Para Auditorias
+- [ ] Analisou Core Web Vitals
+- [ ] Verificou meta tags de todas as páginas principais
+- [ ] Validou schema markup existente
+- [ ] Identificou oportunidades de quick-win
+- [ ] Criou roadmap priorizado
+
+### Para Content
+- [ ] Incluiu keywords naturalmente
+- [ ] Criou múltiplas variantes de títulos
+- [ ] Gerou posts para social media
+- [ ] Criou subject lines para email
+- [ ] Definiu CTAs claros
+
+## Ferramentas de Referência
+
+- [Google PageSpeed Insights](https://pagespeed.web.dev/)
+- [Schema.org Validator](https://validator.schema.org/)
+- [Google Rich Results Test](https://search.google.com/test/rich-results)
+- [Google Search Console](https://search.google.com/search-console)
+- [Ahrefs](https://ahrefs.com/) - Keyword research
+- [Semrush](https://semrush.com/) - SEO analysis
+- [Screaming Frog](https://www.screamingfrog.co.uk/) - Crawl analysis
+- [GTmetrix](https://gtmetrix.com/) - Performance testing
+
+## Anti-Patterns a Evitar
+
+1. **Keyword stuffing**: Keywords devem fluir naturalmente
+2. **Duplicate content**: Cada página deve ter meta tags únicas
+3. **Missing alt text**: Todas as imagens precisam de alt descritivo
+4. **Broken internal links**: Verificar 404s regularmente
+5. **Thin content**: Mínimo 300 palavras para páginas indexáveis
+6. **Missing schema**: Landing pages e produtos DEVEM ter structured data
+7. **Slow page speed**: LCP > 2.5s é crítico
+8. **Mobile unfriendly**: Design responsivo é obrigatório
+9. **Missing canonical**: Páginas com parâmetros devem ter canonical
+10. **No sitemap**: sitemap.xml deve existir e estar no robots.txt
+
+## Métricas de Sucesso
+
+### SEO Técnico
+- Core Web Vitals: LCP < 2.5s, FID < 100ms, CLS < 0.1
+- Mobile usability: 100% mobile-friendly
+- Indexação: 100% páginas importantes indexadas
+- Schema: Rich results em todas as páginas elegíveis
+
+### Content Marketing
+- Organic traffic: +X% mês a mês
+- Keyword rankings: Top 10 para keywords principais
+- CTR: > 3% no Search Console
+- Engagement: Tempo na página > 2min, bounce < 50%
+
+### Conversão
+- Landing page conversion: > 3%
+- Email open rate: > 25%
+- Email CTR: > 3%
+- Social engagement: > 2% engagement rate

package/framework/skills/level-2-domains/architecture/standards-architect.md

@@ -0,0 +1,156 @@
+# 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/coding.md` for complete C# naming conventions and .editorconfig template.
+> **Ref:** `framework/standards/architecture.md` for Clean Architecture layers, SOLID, service patterns.
+
+## Responsabilidades
+
+1. **Garantir aderencia aos padroes** definidos em `framework/standards/` e `.morph/project/standards/`
+2. **Validar nomenclatura** contra `coding.md` (PascalCase, _camelCase, etc.)
+3. **Revisar codigo** antes de aprovar merges
+4. **Definir convencoes** de projeto
+5. **Orquestrar validacao:** Standards Architect (naming) -> Code Analyzer (architecture) -> Code Review (runtime patterns)
+
+## Triggers
+
+Ativado automaticamente em todo projeto MORPH-SPEC (Core Agent).
+
+Keywords: `standards`, `naming`, `convention`, `pattern`, `review`, `quality`, `editorconfig`, `style`
+
+---
+
+## Naming Quick Reference
+
+> Full reference: `framework/standards/coding.md`
+
+| Element | Convention | Example |
+|---------|-----------|---------|
+| Classes, Methods, Properties | PascalCase | `OrderService`, `GetOrderAsync` |
+| Interfaces | `I` + PascalCase | `IOrderService` |
+| Constants | PascalCase | `DefaultPageSize`, `MaxRetryCount` |
+| Private fields | `_camelCase` | `_repository`, `_logger` |
+| Parameters, locals | camelCase | `orderId`, `orderTotal` |
+| Enums | PascalCase | `OrderStatus.PendingPayment` |
+| Async methods | PascalCase + `Async` | `ProcessPaymentAsync` |
+
+**CRITICAL:** Constants use PascalCase, NOT UPPER_SNAKE_CASE. This follows Microsoft .NET guidelines.
+
+---
+
+## Instant-Fail Rules (Severity: Error)
+
+These rules MUST be satisfied. Code that violates them cannot be merged.
+
+| # | Rule | Signal | Ref |
+|---|------|--------|-----|
+| 1 | **Constants in ALL_CAPS** | `MAX_RETRY_COUNT` instead of `MaxRetryCount` | coding.md |
+| 2 | **Hungarian notation** | `strName`, `iCount`, `btnSubmit` | coding.md |
+| 3 | **Missing CancellationToken** | Async method without `ct` parameter | coding.md |
+| 4 | **`.Result` or `.Wait()`** | Synchronous blocking on async (deadlock) | coding.md |
+| 5 | **Scoped DbContext in background** | Direct `DbContext` in Task.Run/Hangfire | blazor-efcore.md |
+| 6 | **Empty catch block** | `catch { }` or `catch (Exception) { }` | coding.md |
+| 7 | **Domain referencing Infrastructure** | `using MyApp.Infrastructure` in Domain project | architecture.md |
+| 8 | **Hardcoded secrets** | Connection strings, API keys in code | architecture.md |
+| 9 | **Missing `sealed`** | Non-abstract class without `sealed` | coding.md |
+| 10 | **Generic `Exception` throw** | `throw new Exception("...")` | coding.md |
+
+---
+
+## Warning Rules (Severity: Warning)
+
+| # | Rule | Signal |
+|---|------|--------|
+| 1 | Method > 30 lines | Needs extraction |
+| 2 | Class > 300 lines | SRP violation, split |
+| 3 | > 4 constructor parameters | Consider grouping or splitting |
+| 4 | Missing structured logging | Service method without `ILogger` usage |
+| 5 | `string.Format` or `$""` in log | Use message templates |
+| 6 | Abbreviations in names | `repo`, `ctx`, `mgr` (use full words) |
+| 7 | Missing `null` check | Parameter not validated at boundary |
+| 8 | Unused `using` | Dead imports |
+
+---
+
+## Enforcement
+
+### .editorconfig
+
+Every project MUST have an `.editorconfig` in the root. Template in `coding.md`.
+
+```bash
+# Validate naming rules at build time
+dotnet build /warnaserror:IDE1006
+```
+
+### Validation Workflow
+
+```
+1. Standards Architect    → Naming, style, conventions (coding.md)
+2. Code Analyzer          → Architecture, clean code, duplication (architecture.md)
+3. Code Review Checklist  → Runtime patterns: async, DI, logging (code-review.md)
+```
+
+This pipeline runs:
+- **Automatically** at FASE 5 completion and at every checkpoint (every 3 tasks)
+- **Manually** when requested via `review`, `analyze`, `check standards`
+
+---
+
+## Estrutura de Projeto
+
+> Full reference: `framework/standards/architecture.md`
+
+```
+src/
+├── {Project}.Domain/          # Entidades, Value Objects, Enums
+├── {Project}.Application/     # Services, DTOs, Interfaces
+├── {Project}.Infrastructure/  # EF Core, External Services
+├── {Project}.Web/             # Blazor, API Controllers
+└── tests/                     # Unit, Integration tests
+```
+
+---
+
+## Padroes Blazor
+
+```razor
+@* Componentes: PascalCase.razor *@
+@* Parameters: [Parameter] obrigatorio *@
+@* EventCallbacks: On{Event}Async *@
+
+<OrderList Orders="@_orders" OnSelectAsync="HandleSelectAsync" />
+```
+
+---
+
+## Documentacao de Referencia
+
+- `framework/standards/coding.md` — C# naming, style, .editorconfig
+- `framework/standards/architecture.md` — Clean Architecture, SOLID, DI
+- `framework/standards/blazor-efcore.md` — DbContext, Repository Factory
+- `framework/standards/blazor-pitfalls.md` — Common Blazor issues
+- [Microsoft C# Coding Conventions](https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions)
+- [.NET Naming Guidelines](https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/naming-guidelines)
+
+---
+
+## Checklist de Revisao
+
+- [ ] Nomenclatura segue `coding.md` (PascalCase constants, _camelCase fields)
+- [ ] `.editorconfig` presente no projeto
+- [ ] Async/await com CancellationToken
+- [ ] Nullable reference types habilitado
+- [ ] DI registrado corretamente (lifetimes corretos)
+- [ ] Logs estruturados com `ILogger<T>` (message templates)
+- [ ] Exceptions tratadas adequadamente (Result pattern para business)
+- [ ] Classes `sealed` por padrao
+- [ ] Codigo sem warnings (IDE1006 enforced)
+- [ ] Arquitetura segue `architecture.md` (layers, SOLID)
+
+---
+
+*MORPH-SPEC by Polymorphism Tech*