@polymorphism-tech/morph-spec 9.1.0 → 9.2.0

package/framework/skills/core/morph-media/SKILL.md

@@ -4,7 +4,7 @@ description: Conduz a AUTORIA de mídia gerada por IA — escolher o modelo pelo
 version: core
 when_to_use: Use quando a tarefa for PRODUZIR imagem ou vídeo por IA (catálogo, marketing, asset de LP) e alguém precisar decidir modelo, prompt e aprovação
 user-invocable: true
-cliVersion: "9.1.0"
+cliVersion: "9.2.0"
 stacks:
   - dotnet
   - nextjs

package/framework/skills/core/morph-plan/SKILL.md

@@ -4,7 +4,7 @@ description: Leva uma feature do pedido ao plano aprovado — roteia o tipo de t
 version: core
 when_to_use: Use quando uma feature, bug ou chore começar ("/morph-plan {feature}", "vamos planejar X"), ou ao retomar uma feature cujo gate plan ainda não foi aprovado
 user-invocable: true
-cliVersion: "9.1.0"
+cliVersion: "9.2.0"
 ---
 
 # morph-plan
@@ -66,19 +66,21 @@ Exit ≠ 0 → descarte o mapa e re-despache **uma** vez com as `failures` colad
 
 O `create` já escreveu o esqueleto em `2-plan/plan.md` (leia e preencha; `chore` e `hotfix` nascem com o gate carimbado e criam o arquivo numa única escrita); gramática completa: `morph-spec plan-check --help`. `plan-check` é o único leitor; o que ele não reconhece, ninguém lê.
 
-**Cenários** (`## Cenários`): `- **Cn** — Dado …, quando …, então …`, com `prova:` (`teste` | `e2e` | `eval` | `manual`) **na linha seguinte, sem linha em branco** — linha vazia encerra o cenário.
-- **Observável em teste**: que asserção eu escreveria? Sem resposta, reescreva ou descarte.
+**Cenários** (`## Cenários`): `- **Cn** — Dado …, quando …, então …`, com `prova:` (`teste` | `e2e` | `eval` | `manual` | `leitura`) **na linha seguinte, sem linha em branco** — linha vazia encerra o cenário.
+- **Teste é por risco, não por código novo.** `prova: teste` exige `risco:` (`regra` | `dinheiro` | `contrato` | `concorrência` | `dado` | `regressão`) na linha abaixo: ramo de regra de negócio, valor, contrato externo, corrida, integridade de dado ou o bug real. Sem risco (CRUD, DTO, mapping, wiring, constante, texto, layout) a prova é `leitura` — o verificador fecha citando `arquivo:linha` — ou `e2e` quando o fluxo é o que importa. O `plan-check` recusa `teste` sem `risco:`.
+- **Observável**: que asserção (ou que linha de código) prova? Sem resposta, reescreva ou descarte.
 - **Artefato não é comportamento.** Cenário que cita `grep`, "contém a string", "o binário", "nenhum arquivo", "arquivo/pasta/diretório em" ou glob `**/` descreve o repositório. Tente o efeito em runtime; se o artefato É o entregável, justifique em `> Por que artefato:` logo abaixo (nunca na mesma linha, nunca `> [!note]`).
 - **Saída de LLM** (o que o modelo responde) prova-se por `eval` de runtime, nunca pelo texto do prompt: evidência em `3-implement/evidencias/{Cn}.md`, path listado em `arquivos:` da fatia; com nó `runner: "evals"` (standard `ai-agents-evals-with-cache`) o cenário mora no dataset. No máximo 1 teste de estrutura da fonte do prompt.
 - **"O comando de teste da raiz roda de ponta a ponta"** prova-se pelo `verify {feature}` (o nó `e2e` e o nó de teste `e2e: true` já percorrem a cadeia): nomeie essa rodada como a prova, nunca uma execução avulsa. Precisando mesmo rodar fora dele, numa linha só (o Bash não guarda o env entre chamadas): `eval "$(morph-spec env {feature})" && morph-spec heavy run -- <comando>` — o `COMPOSE_PROJECT_NAME` da feature é o que o `finish` derruba com os volumes. `prova: manual` registra passo e resultado em `3-implement/evidencias/{Cn}.md`.
-- **Orçamento de teste**: um teste por cenário, um de regressão por bug; acima disso, uma linha de porquê. Cenários do mesmo comportamento são linhas de tabela (`[Theory]`/`it.each`); nenhum teste que só fixa texto. O `verify` avisa quando o teste passa de 1,5× a produção.
+- **Orçamento de teste**: um teste por cenário de risco — o cenário é a unidade, nunca a pós-condição nem o componente; variantes são linhas de tabela (`[Theory]`/`it.each`); acima disso, o porquê na linha do cenário. Nenhum teste que só fixa texto, prompt ou constante, nenhum de DTO/mapping, e o mesmo comportamento numa camada só (handler **ou** endpoint). Teste além do orçamento é escopo para o revisor. O `verify` avisa quando o teste passa da produção.
 
 ```markdown
 ## Cenários
 - **C1** — Dado um tenant com `criterion_overrides`, quando ele é publicado, então a publicação é recusada nomeando a chave.
   prova: teste
+  risco: contrato
 - **C2** — Nenhum arquivo em `tenants/**` contém a chave `criterion_overrides`.
-  prova: teste
+  prova: leitura
   > Por que artefato: a chave saiu do contrato; nenhum leitor de runtime a consulta.
 
 ## Fatias
@@ -136,7 +138,7 @@ A pergunta **nomeia a feature**: é por ela que o hook `state-sync` grava a apro
 
 ## 8. Deltas por tipo
 
-- **`bug` (bug-lean):** a varredura roda inteira; a árvore é de repro, diagnóstico e comportamento do sistema, não de negócio; no modo automático, no máximo 1 pergunta de repro, e só se o pedido não deixar claro. `## Problema` traz repro, diagnóstico e causa provável; os cenários são o sintoma ausente e a regressão; `### Conflitos com o acervo` continua presente.
+- **`bug` (bug-lean):** a varredura roda inteira; a árvore é de repro, diagnóstico e comportamento do sistema, não de negócio; no modo automático, no máximo 1 pergunta de repro, e só se o pedido não deixar claro. `## Problema` traz repro, diagnóstico e causa provável; um cenário é o sintoma ausente com `prova: teste` e `risco: regressão` (o `plan-check` recusa bug sem ele) — esse é o teste que fica; `### Conflitos com o acervo` continua presente.
 - **`chore`:** nasce com o gate `plan` carimbado por política. Escreva o plan.md curto numa única escrita (o gate já aprovado congela o arquivo depois de criado): `## Problema`, um ou dois cenários, `## Decisões` só com `### Conflitos com o acervo`, uma fatia. `plan-check` e `Skill(morph-apply)`.
 - **`hotfix`:** é da `morph-hotfix`.
 

package/framework/skills/core/morph-review/SKILL.md

@@ -4,7 +4,7 @@ description: Conduz o Gate 3 — despacha verificador ∥ revisor (∥ seguranç
 version: core
 when_to_use: Use quando a fase review começar, com todas as fatias com relatório final e o verify da feature verde
 user-invocable: true
-cliVersion: "9.1.0"
+cliVersion: "9.2.0"
 ---
 
 # morph-review
@@ -32,14 +32,15 @@ Commite o trabalho da feature (`git add <paths>` + `git commit`) e rode
 `morph-spec verify {feature} --ci --json` com `run_in_background`. Ele empurra a branch, espera o run
 e grava o stamp do artefato que o run publicou; sem CI, roda local e diz por quê.
 **Sem `--filter`, sempre**: o Gate 3 roda a suíte inteira. Esta é a única execução de testes do Gate 3 — nenhum agente
-roda a suíte de novo. `repeatOf` no JSON = nada mudou, use aquela rodada; `reason: "stamp-reused"` = sem CI e
-nada fora de `.morph/` andou desde o último verify verde: ele vale, não rode de novo.
+roda a suíte de novo. `repeatOf` no JSON = nada mudou, use aquela rodada; `reason: "stamp-reused"` = nada
+fora de `.morph/` andou desde o último verify verde (local ou CI): ele vale e o CI não roda de novo.
 - **Quando a saída mostrar `CI rodando`, despache (passo 3) sem esperar o fim**: o push e o
   workflow já estão commitados e a foto da árvore não os acusa. Saiu `verify local`: espere o fim
   antes do passo 3 — suíte local e `mutate` disputam a máquina. Exit 2 = trabalho fora de commit.
 - Nó `e2e`: `pass` local → `morph-spec e2e status {feature} --json` → `baseUrl` vai ao verificador.
   `fail` → correção (CI: `gh run view <id> --log-failed`). `skip` → quem classifica é o `gate-check`
-  (`classifyE2eSkip`): dispensa de projeto passa; ambiente, `--skip-e2e` ou razão desconhecida pausam.
+  (`classifyE2eSkip`): dispensa de projeto e `not applicable` (feature sem UI/spec/container no diff e sem
+  `prova: e2e`) passam; ambiente, `--skip-e2e` ou razão desconhecida pausam.
 - `traceability.warnings` do verify vão ao revisor como sinal.
 
 ## 3. Dispatch — verificador ∥ revisor (∥ segurança)
@@ -49,7 +50,8 @@ Anote `base` (merge-base com a default) e `sha` (`git rev-parse HEAD`). Blast ra
 símbolo público do diff, `morph-spec graph affected <símbolo> --prod --json`; sem grafo
 (`no-graph`/`not-found`/`ambiguous`), siga sem o blast radius — o revisor cai para `git grep` — e
 registre a ausência no recado a ele. Cada agente nasce com contexto fresco e **nunca recebe relatório anterior** (ancoragem).
-Despache todos na mesma resposta:
+`chore` tem review leve: só o revisor (∥ segurança, quando exigida) — sem verificador, sem cobertura de
+`Cn`, sem mutação. Despache todos na mesma resposta:
 ```
 dispatch Agent (subagent_type: "morph-verifier", model: {reviewModels.verifier.model}) with prompt:
   feature, base, sha, JSON do verify (nós, e2e, URL) se já terminou, 1-design/mockups.md e
@@ -92,7 +94,8 @@ retomar, despache um novo.
 ## 5. Bloqueadores
 O avaliador também erra: **antes de editar, reverifique cada bloqueador no código** — evidência que
 não se reproduz vira pergunta ao mesmo agente, não correção. Confirmado: corrija (loop da
-`morph-apply`), commite, rode o `verify {feature} --ci` de novo e uma foto `--before-eval` nova.
+`morph-apply`), commite, rode `verify {feature}` local (o stamp verde dele é a prova: um `--ci` depois
+reusa, não roda de novo) e uma foto `--before-eval` nova.
 Retome por `SendMessage` TODO agente exigido, com o `sha` novo e `tree.dirty`/`tree.commits`: quem
 abriu bloqueadores **confirme só os bloqueadores** (retomando o MESMO agente que os abriu); os outros
 julgam só o delta `{sha anterior}..{sha novo}` — o que a correção abriu. `reviewModels.security.required`

package/framework/skills/core/morph-standards/SKILL.md

@@ -4,7 +4,7 @@ description: Localiza um standard específico via busca server-side (morph-spec
 version: core
 when_to_use: Use quando precisar consultar um standard específico durante a implementação
 user-invocable: true
-cliVersion: "9.1.0"
+cliVersion: "9.2.0"
 ---
 
 # morph-standards

package/framework/skills/core/morph-uiux/SKILL.md

@@ -4,7 +4,7 @@ description: Conduz a fase opcional de UI/UX de uma feature com plano aprovado
 version: core
 when_to_use: Use quando o ramo de design for tomado (morph-spec advance {feature} --design, depois do gate do plano) e antes de /morph-apply
 user-invocable: true
-cliVersion: "9.1.0"
+cliVersion: "9.2.0"
 ---
 
 # morph-uiux

package/framework/standards/STANDARDS.json

@@ -966,7 +966,7 @@
         "errorbody": "#rule-2--error-path-tests-assert-the-response-body-not-just-the-status-code",
         "test-budget": "#test-budget"
       },
-      "digest": "Inject TimeProvider (never DateTime.UtcNow / DateOnly.FromDateTime(DateTime.UtcNow) directly in a handler or validator) and fake it with FakeTimeProvider (Microsoft.Extensions.TimeProvider.Testing) in integration tests — deterministic, no midnight-UTC flake, boundary dates (today vs. yesterday) become facts about the fake clock instead of when the suite happens to run. xUnit + WebApplicationFactory error-path tests (400/404/409) must assert the ProblemDetails response BODY (title/detail/violated field or error code), never just the HTTP status code — a status-only assertion lets the wrong validation rule or the wrong error branch pass silently as long as the status matches. Test budget per task: one test per postcondition plus one regression test per bug, more only with a one-line justification in the task; scenarios of the same behavior (edge cases included) are rows of one [Theory], never copied [Fact]s; no test whose only assertion is a copy, config or prose string (that is an analyzer or a publish-time validation, outside the suite count); shared fixtures before new helpers; bugs and pure logic get tests in any order — the implementer runs its own filter once, never red-green cycles nor production mutation (the Gate 3 mutation proof shows the test bites); a surviving mutant is killed by tightening an assertion or adding a row, not by a new test."
+      "digest": "Inject TimeProvider (never DateTime.UtcNow / DateOnly.FromDateTime(DateTime.UtcNow) directly in a handler or validator) and fake it with FakeTimeProvider (Microsoft.Extensions.TimeProvider.Testing) in integration tests — deterministic, no midnight-UTC flake, boundary dates (today vs. yesterday) become facts about the fake clock instead of when the suite happens to run. xUnit + WebApplicationFactory error-path tests (400/404/409) must assert the ProblemDetails response BODY (title/detail/violated field or error code), never just the HTTP status code — a status-only assertion lets the wrong validation rule or the wrong error branch pass silently as long as the status matches. Tests are paid for by risk, not new code: one test per plan scenario with risco: (rule, money, contract, concurrency, data, regression) plus the regression test of the bug fixed, more only with a one-line justification on the scenario; a scenario without risk (CRUD, DTO, mapping, wiring, constants) is prova: leitura and gets no test; one layer per behavior (handler or endpoint, not both); scenarios of the same behavior (edge cases included) are rows of one [Theory], never copied [Fact]s; no test whose only assertion is a copy, config or prose string (that is an analyzer or a publish-time validation, outside the suite count); shared fixtures before new helpers; bugs and risky scenarios get tests in any order — the implementer runs its own filter once, never red-green cycles nor production mutation (the Gate 3 mutation proof shows the test bites); a surviving mutant is killed by tightening an assertion or adding a row, not by a new test."
     },
     {
       "id": "backend-dotnet-vsa-handler-patterns",
@@ -1516,7 +1516,7 @@
         "e2e": "#test-file-co-location",
         "test-budget": "#test-budget"
       },
-      "digest": "Vitest for unit tests, React Testing Library for component tests. Mock next/navigation with vi.mock. Test Server Actions with direct function calls. Use MSW for API mocking in component tests. Playwright for E2E tests against running app. Never test implementation details — test user behavior and output. Test budget per task: one test per postcondition plus one regression test per bug, more only with a one-line justification in the task; scenarios of the same behavior are rows of one it.each, never copied it() blocks; no test whose only assertion is a copy string (lint or publish-time validation instead); shared wrappers, MSW handlers and factories before new helpers; bugs and pure logic get tests in any order — the implementer runs its own filter once, never red-green cycles nor production mutation."
+      "digest": "Vitest for unit tests, React Testing Library for component tests. Mock next/navigation with vi.mock. Test Server Actions with direct function calls. Use MSW for API mocking in component tests. Playwright for E2E tests against running app. Never test implementation details — test user behavior and output. Tests are paid for by risk, not new code: one test per plan scenario with risco: plus the regression test of the bug fixed, more only with a one-line justification on the scenario; a component is not a budget unit — rendering, layout and copy are prova: leitura or e2e; scenarios of the same behavior are rows of one it.each, never copied it() blocks; no test whose only assertion is a copy string (lint or publish-time validation instead); shared wrappers, MSW handlers and factories before new helpers; bugs and risky scenarios get tests in any order — the implementer runs its own filter once, never red-green cycles nor production mutation."
     },
     {
       "id": "frontend-scroll-driven-frame-scrub",

package/framework/standards/backend/dotnet/testing.md

@@ -115,8 +115,12 @@ respectively and the test suite stays green.
 
 ## Test budget
 
-The plan (`morph-plan`) gives each task a budget: **one test per postcondition, plus one
-regression test per bug fixed**. Going above it takes a one-line justification in the task.
+Tests are paid for by **risk, not by new code**. The plan (`morph-plan`) marks each scenario
+with `prova:` and, for a test, a `risco:` (business rule, money, external contract, concurrency,
+data integrity, regression). The budget is **one test per risky scenario, plus the regression test of
+the bug being fixed**; going above it takes a one-line justification on the scenario. A scenario
+without risk — CRUD, DTO, mapping, wiring, constants, layout — is `prova: leitura`: the Gate 3
+verifier proves it by reading the code, and it gets no test.
 
 - **Table before copy.** Scenarios of the same behavior — including its edge cases (null, empty,
   boundary) — are rows of one `[Theory]` (`[InlineData]`/`[MemberData]`), never N `[Fact]` methods
@@ -125,11 +129,13 @@ regression test per bug fixed**. Going above it takes a one-line justification i
   UI copy, tenant config or prose proves the file's version, not behavior. Enforce it with an
   analyzer, a lint rule or a validation at publish time, outside the suite count. The versioned
   prompt case (at most one structural test) is `ai-agents-testing-ai`.
+- **One layer per behavior.** A rule tested in the handler is not tested again through the
+  endpoint or the SQL integration: pick the cheapest layer that bites (wiring is the verifier's).
 - **Shared fixture by default.** Reuse the project's `WebApplicationFactory` fixture, fakes and
   builders. Before writing a new helper, look for the existing one (`morph-spec graph explain
   <Name>`; fallback without a graph: `grep -rn`).
-- **Order is free, proof is not the implementer's:** a bug gets a regression test, and pure logic
-  gets its tests, in whatever order the code comes out. The implementer does not run red→green
+- **Order is free, proof is not the implementer's:** a bug gets a regression test, and a risky
+  scenario gets its test, in whatever order the code comes out. The implementer does not run red→green
   cycles nor mutate production code to watch a test fail; it runs its own filter once before the
   report, and the Gate 3 mutation proof is what shows the test bites.
 - **A surviving mutant** of the Gate 3 mutation proof is killed by tightening an existing assertion

package/framework/standards/frontend/nextjs/testing.md

@@ -17,7 +17,7 @@ Vitest + React Testing Library for component tests. MSW for API mocking. Co-loca
 - ALWAYS use `@testing-library/user-event` for interactions — not `fireEvent`
 - ALWAYS mock the API layer with MSW — never mock `fetch` directly
 - NEVER test implementation details — test what the user sees
-- ALWAYS test the happy path + one error path per component
+- ONLY test a component when a plan scenario with `risco:` lives in it — a component is not a unit of the budget
 
 ## Test File Co-location
 
@@ -103,9 +103,13 @@ export function QueryClientWrapper({ children }: { children: React.ReactNode })
 
 ## Test Budget
 
-The plan (`morph-plan`) gives each task a budget: **one test per postcondition, plus one
-regression test per bug fixed**. Going above it takes a one-line justification in the task. The
-happy path + one error path per component above is that budget applied to a component.
+Tests are paid for by **risk, not by new code**. The plan (`morph-plan`) marks each scenario
+with `prova:` and, for a test, a `risco:` (business rule, money, external contract, concurrency,
+data integrity, regression). The budget is **one test per risky scenario, plus the regression test of
+the bug being fixed**; going above it takes a one-line justification on the scenario. A scenario
+without risk — CRUD, DTO, mapping, wiring, constants, layout — is `prova: leitura`: the Gate 3
+verifier proves it by reading the code, and it gets no test. Rendering, layout and copy are
+`leitura` or `e2e`, never a unit test per component.
 
 - **Table before copy.** Scenarios of the same behavior — edge cases included — are rows of one
   `it.each`/`test.each`, never N `it()` blocks that differ by one value.
@@ -116,8 +120,8 @@ happy path + one error path per component above is that budget applied to a comp
 - **Shared helpers by default.** Reuse the existing wrappers (`test/helpers.tsx`), MSW handlers and
   factories. Before writing a new one, look for it (`morph-spec graph explain <Name>`; fallback
   without a graph: `grep -rn`).
-- **Order is free, proof is not the implementer's:** a bug gets a regression test, and pure logic
-  (formatters, reducers, schema) gets its tests, in whatever order the code comes out. The
+- **Order is free, proof is not the implementer's:** a bug gets a regression test, and a risky
+  scenario (a formatter of money, a reducer with rules, a schema) gets its test, in whatever order the code comes out. The
   implementer does not run red→green cycles nor mutate production code to watch a test fail; it
   runs its own filter once before the report, and the Gate 3 mutation proof shows the test bites.
 

package/framework/templates/.idea/morph-templates.xml

@@ -0,0 +1,92 @@
+<templateSet group="MORPH Templates">
+  <template name="morph-pascal" value="{{pascalCase $FEATURE_NAME$}}" description="Convert to PascalCase (UserAuth)" toReformat="false" toShortenFQNames="true">
+    <variable name="FEATURE_NAME" expression="" defaultValue="&quot;FEATURE_NAME&quot;" alwaysStopAt="true" />
+    <context>
+      <option name="OTHER" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-camel" value="{{camelCase $FEATURE_NAME$}}" description="Convert to camelCase (userAuth)" toReformat="false" toShortenFQNames="true">
+    <variable name="FEATURE_NAME" expression="" defaultValue="&quot;FEATURE_NAME&quot;" alwaysStopAt="true" />
+    <context>
+      <option name="OTHER" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-snake" value="{{snakeCase $FEATURE_NAME$}}" description="Convert to snake_case (user_auth)" toReformat="false" toShortenFQNames="true">
+    <variable name="FEATURE_NAME" expression="" defaultValue="&quot;FEATURE_NAME&quot;" alwaysStopAt="true" />
+    <context>
+      <option name="OTHER" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-title" value="{{titleCase $FEATURE_NAME$}}" description="Convert to Title Case (User Auth)" toReformat="false" toShortenFQNames="true">
+    <variable name="FEATURE_NAME" expression="" defaultValue="&quot;FEATURE_NAME&quot;" alwaysStopAt="true" />
+    <context>
+      <option name="OTHER" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-kebab" value="{{kebabCase $FEATURE_NAME$}}" description="Convert to kebab-case (user-auth)" toReformat="false" toShortenFQNames="true">
+    <variable name="FEATURE_NAME" expression="" defaultValue="&quot;FEATURE_NAME&quot;" alwaysStopAt="true" />
+    <context>
+      <option name="OTHER" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-if" value="{{#if $CONDITION$}}&#10;  $END$&#10;{{/if}}" description="Handlebars if block" toReformat="false" toShortenFQNames="true">
+    <variable name="CONDITION" expression="" defaultValue="&quot;condition&quot;" alwaysStopAt="true" />
+    <context>
+      <option name="OTHER" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-if-else" value="{{#if $CONDITION$}}&#10;  $TRUE_BRANCH$&#10;{{else}}&#10;  $FALSE_BRANCH$&#10;{{/if}}" description="Handlebars if-else block" toReformat="false" toShortenFQNames="true">
+    <variable name="CONDITION" expression="" defaultValue="&quot;condition&quot;" alwaysStopAt="true" />
+    <variable name="TRUE_BRANCH" expression="" defaultValue="&quot;&quot;" alwaysStopAt="true" />
+    <variable name="FALSE_BRANCH" expression="" defaultValue="&quot;&quot;" alwaysStopAt="true" />
+    <context>
+      <option name="OTHER" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-each" value="{{#each $ITEMS$}}&#10;  {{this.$PROPERTY$}}&#10;{{/each}}" description="Handlebars each loop" toReformat="false" toShortenFQNames="true">
+    <variable name="ITEMS" expression="" defaultValue="&quot;items&quot;" alwaysStopAt="true" />
+    <variable name="PROPERTY" expression="" defaultValue="&quot;name&quot;" alwaysStopAt="true" />
+    <context>
+      <option name="OTHER" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-service" value="namespace {{NAMESPACE}}.Application.Features.{{pascalCase FEATURE_NAME}}.Services;&#10;&#10;public class {{pascalCase FEATURE_NAME}}Service(&#10;    I{{pascalCase FEATURE_NAME}}Repository repository,&#10;    ILogger&lt;{{pascalCase FEATURE_NAME}}Service&gt; logger) : I{{pascalCase FEATURE_NAME}}Service&#10;{&#10;    public async Task&lt;{{pascalCase FEATURE_NAME}}Dto?&gt; GetByIdAsync(int id, CancellationToken cancellationToken = default)&#10;    {&#10;        $END$&#10;    }&#10;}" description="MORPH .NET Service class template" toReformat="false" toShortenFQNames="true">
+    <context>
+      <option name="C_SHARP" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-repository" value="public class {{pascalCase FEATURE_NAME}}Repository(AppDbContext context) : I{{pascalCase FEATURE_NAME}}Repository&#10;{&#10;    private readonly DbSet&lt;{{pascalCase FEATURE_NAME}}&gt; _dbSet = context.Set&lt;{{pascalCase FEATURE_NAME}}&gt;();&#10;&#10;    public async Task&lt;{{pascalCase FEATURE_NAME}}?&gt; GetByIdAsync(int id, CancellationToken cancellationToken = default)&#10;    {&#10;        $END$&#10;    }&#10;}" description="MORPH .NET Repository class template" toReformat="false" toShortenFQNames="true">
+    <context>
+      <option name="C_SHARP" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-component" value="@page &quot;/{{kebabCase FEATURE_NAME}}&quot;&#10;@inject I{{pascalCase FEATURE_NAME}}Service {{pascalCase FEATURE_NAME}}Service&#10;@inject ILogger&lt;{{pascalCase FEATURE_NAME}}Page&gt; Logger&#10;&#10;&lt;PageTitle&gt;{{pascalCase FEATURE_NAME}}&lt;/PageTitle&gt;&#10;&#10;&lt;div class=&quot;container-fluid&quot;&gt;&#10;    $END$&#10;&lt;/div&gt;&#10;&#10;@code {&#10;&#10;}" description="MORPH Blazor component template" toReformat="false" toShortenFQNames="true">
+    <context>
+      <option name="HTML" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-migration" value="public partial class Add{{pascalCase FEATURE_NAME}} : Migration&#10;{&#10;    protected override void Up(MigrationBuilder migrationBuilder)&#10;    {&#10;        migrationBuilder.CreateTable(&#10;            name: &quot;{{pascalCase FEATURE_NAME}}s&quot;,&#10;            columns: table =&gt; new&#10;            {&#10;                Id = table.Column&lt;int&gt;(type: &quot;int&quot;, nullable: false)&#10;                    .Annotation(&quot;SqlServer:Identity&quot;, &quot;1, 1&quot;),&#10;                $END$&#10;            },&#10;            constraints: table =&gt;&#10;            {&#10;                table.PrimaryKey(&quot;PK_{{pascalCase FEATURE_NAME}}s&quot;, x =&gt; x.Id);&#10;            });&#10;    }&#10;&#10;    protected override void Down(MigrationBuilder migrationBuilder)&#10;    {&#10;        migrationBuilder.DropTable(name: &quot;{{pascalCase FEATURE_NAME}}s&quot;);&#10;    }&#10;}" description="MORPH EF Core migration template" toReformat="false" toShortenFQNames="true">
+    <context>
+      <option name="C_SHARP" value="true" />
+    </context>
+  </template>
+
+  <template name="morph-ts-contract" value="export interface {{pascalCase FEATURE_NAME}} {&#10;  id: number;&#10;  $FIELD1$&#10;}&#10;&#10;export interface Create{{pascalCase FEATURE_NAME}}Request {&#10;  $FIELD2$&#10;}&#10;&#10;export interface Update{{pascalCase FEATURE_NAME}}Request {&#10;  $END$&#10;}" description="MORPH TypeScript contract template" toReformat="false" toShortenFQNames="true">
+    <variable name="FIELD1" expression="" defaultValue="&quot;&quot;" alwaysStopAt="true" />
+    <variable name="FIELD2" expression="" defaultValue="&quot;&quot;" alwaysStopAt="true" />
+    <context>
+      <option name="TypeScript" value="true" />
+    </context>
+  </template>
+</templateSet>

package/framework/templates/.vscode/morph-templates.code-snippets

@@ -0,0 +1,186 @@
+{
+  "MORPH Template - PascalCase": {
+    "prefix": "morph-pascal",
+    "body": ["{{pascalCase ${1:FEATURE_NAME}}}"],
+    "description": "Convert to PascalCase (UserAuth)"
+  },
+  "MORPH Template - camelCase": {
+    "prefix": "morph-camel",
+    "body": ["{{camelCase ${1:FEATURE_NAME}}}"],
+    "description": "Convert to camelCase (userAuth)"
+  },
+  "MORPH Template - snake_case": {
+    "prefix": "morph-snake",
+    "body": ["{{snakeCase ${1:FEATURE_NAME}}}"],
+    "description": "Convert to snake_case (user_auth)"
+  },
+  "MORPH Template - Title Case": {
+    "prefix": "morph-title",
+    "body": ["{{titleCase ${1:FEATURE_NAME}}}"],
+    "description": "Convert to Title Case (User Auth)"
+  },
+  "MORPH Template - kebab-case": {
+    "prefix": "morph-kebab",
+    "body": ["{{kebabCase ${1:FEATURE_NAME}}}"],
+    "description": "Convert to kebab-case (user-auth)"
+  },
+  "MORPH Template - UPPER_SNAKE_CASE": {
+    "prefix": "morph-upper-snake",
+    "body": ["{{upperSnakeCase ${1:FEATURE_NAME}}}"],
+    "description": "Convert to UPPER_SNAKE_CASE (USER_AUTH)"
+  },
+  "MORPH Template - Conditional If": {
+    "prefix": "morph-if",
+    "body": [
+      "{{#if ${1:condition}}}",
+      "  $2",
+      "{{/if}}"
+    ],
+    "description": "Handlebars if block"
+  },
+  "MORPH Template - Conditional If-Else": {
+    "prefix": "morph-if-else",
+    "body": [
+      "{{#if ${1:condition}}}",
+      "  $2",
+      "{{else}}",
+      "  $3",
+      "{{/if}}"
+    ],
+    "description": "Handlebars if-else block"
+  },
+  "MORPH Template - Each Loop": {
+    "prefix": "morph-each",
+    "body": [
+      "{{#each ${1:items}}}",
+      "  {{this.$2}}",
+      "{{/each}}"
+    ],
+    "description": "Handlebars each loop"
+  },
+  "MORPH Template - Unless": {
+    "prefix": "morph-unless",
+    "body": [
+      "{{#unless ${1:condition}}}",
+      "  $2",
+      "{{/unless}}"
+    ],
+    "description": "Handlebars unless block"
+  },
+  "MORPH Template - .NET Service Class": {
+    "prefix": "morph-service",
+    "body": [
+      "namespace {{NAMESPACE}}.Application.Features.{{pascalCase FEATURE_NAME}}.Services;",
+      "",
+      "public class {{pascalCase FEATURE_NAME}}Service(",
+      "    I{{pascalCase FEATURE_NAME}}Repository repository,",
+      "    ILogger<{{pascalCase FEATURE_NAME}}Service> logger) : I{{pascalCase FEATURE_NAME}}Service",
+      "{",
+      "    public async Task<{{pascalCase FEATURE_NAME}}Dto?> GetByIdAsync(int id, CancellationToken cancellationToken = default)",
+      "    {",
+      "        $1",
+      "    }",
+      "}"
+    ],
+    "description": "MORPH .NET Service class template"
+  },
+  "MORPH Template - .NET Repository Class": {
+    "prefix": "morph-repository",
+    "body": [
+      "public class {{pascalCase FEATURE_NAME}}Repository(AppDbContext context) : I{{pascalCase FEATURE_NAME}}Repository",
+      "{",
+      "    private readonly DbSet<{{pascalCase FEATURE_NAME}}> _dbSet = context.Set<{{pascalCase FEATURE_NAME}}>();",
+      "",
+      "    public async Task<{{pascalCase FEATURE_NAME}}?> GetByIdAsync(int id, CancellationToken cancellationToken = default)",
+      "    {",
+      "        $1",
+      "    }",
+      "}"
+    ],
+    "description": "MORPH .NET Repository class template"
+  },
+  "MORPH Template - Blazor Component": {
+    "prefix": "morph-component",
+    "body": [
+      "@page \"/{{kebabCase FEATURE_NAME}}\"",
+      "@inject I{{pascalCase FEATURE_NAME}}Service {{pascalCase FEATURE_NAME}}Service",
+      "@inject ILogger<{{pascalCase FEATURE_NAME}}Page> Logger",
+      "",
+      "<PageTitle>{{pascalCase FEATURE_NAME}}</PageTitle>",
+      "",
+      "<div class=\"container-fluid\">",
+      "    $1",
+      "</div>",
+      "",
+      "@code {",
+      "    $2",
+      "}"
+    ],
+    "description": "MORPH Blazor component template"
+  },
+  "MORPH Template - EF Core Migration": {
+    "prefix": "morph-migration",
+    "body": [
+      "public partial class Add{{pascalCase FEATURE_NAME}} : Migration",
+      "{",
+      "    protected override void Up(MigrationBuilder migrationBuilder)",
+      "    {",
+      "        migrationBuilder.CreateTable(",
+      "            name: \"{{pascalCase FEATURE_NAME}}s\",",
+      "            columns: table => new",
+      "            {",
+      "                Id = table.Column<int>(type: \"int\", nullable: false)",
+      "                    .Annotation(\"SqlServer:Identity\", \"1, 1\"),",
+      "                $1",
+      "            },",
+      "            constraints: table =>",
+      "            {",
+      "                table.PrimaryKey(\"PK_{{pascalCase FEATURE_NAME}}s\", x => x.Id);",
+      "            });",
+      "    }",
+      "",
+      "    protected override void Down(MigrationBuilder migrationBuilder)",
+      "    {",
+      "        migrationBuilder.DropTable(name: \"{{pascalCase FEATURE_NAME}}s\");",
+      "    }",
+      "}"
+    ],
+    "description": "MORPH EF Core migration template"
+  },
+  "MORPH Template - Hangfire Job": {
+    "prefix": "morph-job",
+    "body": [
+      "public class {{pascalCase FEATURE_NAME}}ProcessorJob(",
+      "    I{{pascalCase FEATURE_NAME}}Service service,",
+      "    ILogger<{{pascalCase FEATURE_NAME}}ProcessorJob> logger) : I{{pascalCase FEATURE_NAME}}ProcessorJob",
+      "{",
+      "    [AutomaticRetry(Attempts = 3, DelaysInSeconds = new[] { 60, 300, 900 })]",
+      "    [Queue(\"default\")]",
+      "    [JobDisplayName(\"{{pascalCase FEATURE_NAME}} Processing - ID: {0}\")]",
+      "    public async Task ExecuteAsync(int id, CancellationToken cancellationToken)",
+      "    {",
+      "        $1",
+      "    }",
+      "}"
+    ],
+    "description": "MORPH Hangfire job template"
+  },
+  "MORPH Template - TypeScript Contract": {
+    "prefix": "morph-ts-contract",
+    "body": [
+      "export interface {{pascalCase FEATURE_NAME}} {",
+      "  id: number;",
+      "  $1",
+      "}",
+      "",
+      "export interface Create{{pascalCase FEATURE_NAME}}Request {",
+      "  $2",
+      "}",
+      "",
+      "export interface Update{{pascalCase FEATURE_NAME}}Request {",
+      "  $3",
+      "}"
+    ],
+    "description": "MORPH TypeScript contract template"
+  }
+}