@polymorphism-tech/morph-spec 4.16.0 → 4.18.0

package/framework/skills/level-0-meta/morph-frontend-review/SKILL.md

@@ -10,7 +10,7 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion,
   mcp__playwright__browser_navigate, mcp__playwright__browser_resize,
   mcp__playwright__browser_take_screenshot, mcp__playwright__browser_snapshot,
   mcp__playwright__browser_evaluate, mcp__playwright__browser_console_messages
-cliVersion: "4.8.19"
+cliVersion: "4.18.0"
 stacks:
   - nextjs
 ---

package/framework/skills/level-0-meta/morph-init/SKILL.md

@@ -101,28 +101,28 @@ Gather evidence to build a stack map. Run these in parallel:
 
 | Tool | Pattern | Signal |
 |------|---------|--------|
-| `Glob` | `**/package.json` | Detect next, supabase, clerk, stripe in deps |
+| `Glob` | `**/package.json` | Detect next, neon, @neondatabase/auth, stripe in deps |
 | `Glob` | `**/*.csproj` | .NET projects at any depth |
 | `Glob` | `**/next.config.{js,ts,mjs}` | Next.js in any subdirectory |
 | `Glob` | `**/components.json` | shadcn/ui |
 | `Glob` | `**/docker-compose*.yml` | Container services |
-| `Glob` | `database/migrations/**` | Supabase local dev |
-| `Glob` | `supabase/**` | Supabase project config |
+| `Glob` | `database/migrations/**` | Database migrations |
+| `Grep` | `DATABASE_URL\|NEON_\|neonctl` | Neon database config |
 
 | `Glob` | `**/Abstractions/IHandler.cs` | VSA pattern (KanaiyaKatarmal) |
 | `Glob` | `**/Pipelines/ValidationDecorator.cs` | VSA pipeline |
 | `Glob` | `**/Features/**/*Feature` | VSA feature folder suffix |
 | `Read` | `.env.example` | Env vars reveal integrations |
 | `Read` | `README.md` | Existing project description |
-| `Grep` | `@supabase/supabase-js` | Supabase dep in any package.json |
-| `Grep` | `clerk\|auth0\|nextauth` | Auth provider |
+| `Grep` | `@neondatabase/serverless` | Neon dep in any package.json |
+| `Grep` | `@neondatabase/auth\|auth0\|nextauth` | Auth provider |
 | `Grep` | `stripe\|asaas` | Payment provider |
 
 Read each found `package.json` for dependency names. Build an **evidence map**:
 
 ```
 stack:             [nextjs, dotnet, ...]
-integrations:      [supabase, docker, clerk, ...]
+integrations:      [neon, docker, neon-auth, ...]
 uiLibrary:         shadcn | null
 monorepo:          true | false
 frontendPath:      src/frontend (if monorepo)
@@ -147,7 +147,7 @@ Ask at most 3 questions, only those that apply:
 |---|----------|-----------|---------|
 | 1 | *"In one sentence: what is the main purpose of **[ProjectName]**?"* | Always | README.md Overview |
 | 2 | *"Confirmed: frontend at `{frontendPath}`, backend at `{backendPath}`. Correct?"* | Monorepo detected | Validate paths before persisting |
-| 3 | *"Supabase Cloud (managed) or self-hosted?"* | Supabase detected | Local dev configuration |
+| 3 | *"Neon (cloud PostgreSQL) or self-hosted Postgres?"* | Neon detected | Database configuration |
 
 Do **not** ask about technology already confirmed by file evidence.
 
@@ -326,7 +326,7 @@ Read `.morph/config/config.json` and merge into `project`:
     "stack": "[stacks joined with +, e.g. nextjs+dotnet]",
     "architecture": "[monorepo | single-stack | detected pattern]",
     "uiLibrary": "[detected or null]",
-    "integrations": ["supabase", "docker", "clerk"],
+    "integrations": ["neon", "docker", "neon-auth"],
     "frontendPath": "[path if monorepo, else omit]",
     "backendPath": "[path if monorepo, else omit]"
   }
@@ -385,9 +385,9 @@ Output confirms: `✓ setup-infra (reinstall): complete.`
 
 For each detected integration with an available MCP:
 
-**Supabase detected:**
-> *"Supabase CLI detected. Local Docker instance will be used for all database operations (`npx supabase start`)."*
-> No MCP configuration needed — CLI is the primary and only tool for Supabase interaction.
+**Neon detected:**
+> *"Neon database detected. Use `neonctl` for branch management and `psql` for direct database operations."*
+> No MCP configuration needed — CLI is the primary tool for Neon interaction.
 
 **GitHub:**
 > *"Configure GitHub MCP? Requires Docker + a `GITHUB_PERSONAL_ACCESS_TOKEN`."*
@@ -421,7 +421,7 @@ Only offer Docker, Azure if explicitly detected in `.env.example`.
 
 > **Format rules for MCP configs:**
 >
-> **Remote MCPs** (Supabase, Vercel) — no credentials, OAuth-based:
+> **Remote MCPs** (Vercel) — no credentials, OAuth-based:
 > ```json
 > "mcp-name": { "type": "http", "url": "https://mcp.example.com" }
 > ```

package/framework/skills/level-0-meta/morph-post-implementation/SKILL.md

@@ -104,11 +104,11 @@ Read validation output, fix reported issues, and re-run until it passes.
 
 ---
 
-### Step 4b — Verify RLS Policies (Supabase projects)
+### Step 4b — Verify RLS Policies (Neon/PostgreSQL projects)
 
-> **Supabase CLI:** If the project uses Supabase, verify RLS policies on the local Docker instance:
+> **Neon CLI (`neonctl`):** If the project uses Neon/PostgreSQL, verify RLS policies on the database:
 >
-> 1. Get DB URL: `npx supabase status` → extract `DB URL`
+> 1. Get DB URL: `neonctl connection-string`
 > 2. Query: `psql <DB_URL> -c "SELECT tablename, policyname, cmd, qual FROM pg_policies WHERE schemaname = 'public'"`
 > 3. For each table modified in this feature, verify:
 >    - [ ] RLS is enabled (`ALTER TABLE ... ENABLE ROW LEVEL SECURITY`)
@@ -116,13 +116,13 @@ Read validation output, fix reported issues, and re-run until it passes.
 >    - [ ] INSERT/UPDATE/DELETE policies match feature requirements
 > 4. If any table is missing RLS → **flag as CRITICAL** (blocks PR)
 >
-> If local Supabase is not running, check for RLS policy files in the `supabase/migrations/` directory and verify they cover modified tables. If no Supabase in the stack, skip this step.
+> If Neon database is not accessible, check for RLS policy files in the `migrations/` directory and verify they cover modified tables. If no Neon/PostgreSQL in the stack, skip this step.
 
 ---
 
 ## Step 5 — Smoke Test (Playwright MCP)
 
-> **Docker CLI:** Before smoke testing, verify local services are running: `docker ps --format "table {{.Names}}\t{{.Status}}"` — all expected containers should show "Up". If Supabase containers are down, run `npx supabase start` before proceeding.
+> **Docker CLI:** Before smoke testing, verify local services are running: `docker ps --format "table {{.Names}}\t{{.Status}}"` — all expected containers should show "Up".
 
 > **MCP:** Smoke testing via **Playwright MCP** is the primary method. If Playwright MCP is not available, fall back to `curl`/`WebFetch` for endpoint verification (limited — cannot test JS-rendered pages or interactions).
 

package/framework/skills/level-0-meta/morph-tool-usage-guide/SKILL.md

@@ -137,10 +137,10 @@ Criterion: if reading file B does not depend on the CONTENT of file A, read both
 |-------|-------------|---------------------|
 | Proposal | GitHub (optional) | No |
 | UI/UX | Playwright, Context7 | No |
-| Design | Supabase, Context7, GitHub | Yes (architect + schema in parallel) |
+| Design | Neon CLI, Context7, GitHub | Yes (architect + schema in parallel) |
 | Plan | Context7, GitHub | No |
 | Tasks | Context7, GitHub | Yes (when spec has 20+ reqs or 3+ domains) |
-| Implement | Supabase, Context7, Playwright, GitHub | Yes (when tasks.total ≥ 6 and 2+ domains) |
+| Implement | Neon CLI, Context7, Playwright, GitHub | Yes (when tasks.total ≥ 6 and 2+ domains) |
 
 ---
 
@@ -164,7 +164,7 @@ Criterion: if reading file B does not depend on the CONTENT of file A, read both
 
 | MCP | When to Use | Fallback |
 |-----|-------------|----------|
-| **Supabase** | Schema analysis, migrations, RLS | Grep + Read code files |
+| **Neon CLI (`neonctl`) + `psql`** | Schema analysis, migrations, RLS | Grep + Read code files |
 | **GitHub** | Issues, PRs, repo metadata, code search | Bash `gh` CLI |
 | **Context7** | Library documentation lookups | WebSearch + WebFetch |
 | **Playwright** | Browser automation, screenshots, page inspection, smoke tests | WebFetch (read-only), Manual testing |
@@ -215,9 +215,9 @@ For the canonical list of MCPs, their tools, phase relevance, and fallbacks, see
 | Proposal | Context7 | WebSearch |
 | Setup | GitHub | `gh` CLI |
 | UI/UX | Playwright, Context7 | WebFetch, Read CSS |
-| Design | Supabase, Context7, GitHub | Grep + Read code |
+| Design | Neon CLI, Context7, GitHub | Grep + Read code |
 | Tasks | Context7, GitHub | WebSearch, `gh` CLI |
-| Implement | Supabase, Context7, Playwright, GitHub | CLI tools |
+| Implement | Neon CLI, Context7, Playwright, GitHub | CLI tools |
 
 ### Detected Plugins & MCPs
 

package/framework/skills/level-0-meta/morph-tool-usage-guide/references/tools-per-phase.md

@@ -68,7 +68,7 @@
 | **Get dispatch config** | **Bash** `morph-spec dispatch-agents {feature} design` | Which agents to spawn + their task prompts |
 | **Dispatch architecture analyst** (parallel) | **Task** subagent with prompt from dispatch config | Analyze architecture complexity independently |
 | **Dispatch tech leads** (parallel) | **Task** subagents (dotnet-senior, nextjs-expert, etc.) | Validate architecture independently |
-| Get database schema | **Bash** `npx supabase db dump --local` or `psql <DB_URL>` | **PREFERRED** — real local schema |
+| Get database schema | **Bash** `pg_dump $(neonctl connection-string)` or `psql <DB_URL>` | **PREFERRED** — real schema |
 | Get table relationships | **Bash** `psql <DB_URL>` FK queries | Real FK/constraint data |
 | Get RLS policies | **Bash** `psql <DB_URL>` pg_policies query | Security analysis |
 | **Fallback:** Find query files | **Grep** `\.from\(` or `\.select\(` in `*.ts,*.tsx,*.js,*.cs` | When no DB MCP available |
@@ -83,14 +83,14 @@
 | Create schema-analysis.md | **Write** to output directory | Document findings |
 | Update state | **Bash** `morph-spec state mark-output {feature} schemaAnalysis && morph-spec state mark-output {feature} spec && morph-spec state mark-output {feature} contracts && morph-spec state mark-output {feature} decisions` | CLI command |
 
-**Tools used:** Supabase CLI / psql (schema analysis — local Docker), Context7 (library research), GitHub (code search).
+**Tools used:** Neon CLI (`neonctl`) / psql (schema analysis), Context7 (library research), GitHub (code search).
 
 **Parallel dispatch opportunity:** Architecture complexity analysis and schema analysis (phase-codebase-analysis) are **independent** — run them as parallel Task subagents to cut design phase time.
 
 **Anti-patterns:**
 - ❌ Guessing field names without checking schema (use MCP or Grep first!)
 - ❌ Task agent to read a single spec file (use Read directly)
-- ❌ WebSearch for database schema (use Supabase CLI/psql or code analysis)
+- ❌ WebSearch for database schema (use Neon CLI/psql or code analysis)
 - ❌ Manually writing contracts-level{N}.cs from scratch (use template render)
 - ❌ Running domain analysis and schema analysis sequentially (they're independent — run in parallel)
 
@@ -138,12 +138,12 @@
 | Create new files | **Write** new source files | New entities, services, pages |
 | Modify existing files | **Edit** existing source files | Add features to existing code |
 | Look up API during coding | **Context7 MCP** `query_docs()` | Accurate library usage |
-| Run database migrations | **Bash** `npx supabase migration up --local` | DDL via psql |
-| **Fallback:** Run migrations | **Bash** `npx supabase migration ...` or `dotnet ef ...` | CLI tools |
+| Run database migrations | **Bash** `dotnet ef database update` | DDL via psql |
+| **Fallback:** Run migrations | **Bash** `dotnet ef ...` or `psql` | CLI tools |
 | Build project | **Bash** `dotnet build` or `npm run build` | Verify compilation |
 | Run tests | **Bash** `dotnet test` or `npm test` | Verify implementation |
 | Checkpoint validation | **Bash** `morph-spec checkpoint ...` | Every 3 tasks |
-| Create RLS policies | **Bash** write SQL migration + `npx supabase migration up --local` | Security policies |
+| Create RLS policies | **Bash** write SQL migration + `dotnet ef database update` | Security policies |
 | Manage containers | **Bash** `docker ps`, `docker logs`, `docker compose` | Container health + debugging |
 | Create infrastructure | **Bash** `az bicep ...` or Bicep files via Write | IaC |
 | Create PR | **GitHub MCP** `create_pull_request()` or **Bash** `gh pr create` | Ship code |
@@ -153,7 +153,7 @@
 | Screenshot para recap.md | **Playwright MCP** `browser_take_screenshot()` | Manual screenshot |
 | Mark recap output | **Bash** `morph-spec state mark-output {feature} recap` | CLI command |
 
-**Tools used:** Supabase CLI (migrations, RLS — local Docker), Context7 (API lookup), GitHub (PRs), Playwright (smoke test, verification).
+**Tools used:** Neon CLI (`neonctl`) / EF Core CLI (migrations), Context7 (API lookup), GitHub (PRs), Playwright (smoke test, verification).
 
 **Parallel dispatch threshold:**
 - `tasks.total ≥ 6` AND feature spans 2+ domains (e.g. `dotnet-senior` + `nextjs-expert`) → dispatch parallel implementers

package/framework/skills/level-1-workflows/morph-phase-codebase-analysis/SKILL.md

@@ -3,7 +3,7 @@ name: morph-phase-codebase-analysis
 description: MORPH-SPEC Design sub-phase that analyzes existing codebase and database schema, producing schema-analysis.md with real column names, types, relationships, and field mismatches. Use at the start of Design phase before generating contracts.cs to prevent incorrect field names or types.
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.16.0"
+cliVersion: "4.18.0"
 ---
 
 # MORPH Codebase Analysis - Design Sub-phase
@@ -26,7 +26,7 @@ Automates existing code analysis to generate `schema-analysis.md` with real data
 
 | Action | Tool | Alternative |
 |------|------------|-------------|
-| List database tables | **Bash** `npx supabase db dump --local` or `psql <DB_URL>` | **Grep** `.from(` in code |
+| List database tables | **Bash** `pg_dump $(neonctl connection-string)` or `psql <DB_URL>` | **Grep** `.from(` in code |
 | Get table schema | **Bash** `psql <DB_URL> -c "SELECT ... FROM information_schema.columns"` | **Read** type definitions |
 | Get FK relationships | **Bash** `psql <DB_URL> -c "SELECT ... FROM information_schema.table_constraints"` | **Grep** JOIN/FK patterns |
 | Get RLS policies | **Bash** `psql <DB_URL> -c "SELECT ... FROM pg_policies"` | **Read** policy files |
@@ -36,7 +36,7 @@ Automates existing code analysis to generate `schema-analysis.md` with real data
 | Complex multi-file analysis | **Task** (subagent Explore) | Read individual |
 | Generate schema-analysis.md | **Write** using template | **Bash** template render |
 
-**Tools for this phase:** Supabase CLI / psql (schema — **PRIORITY**, local Docker), Generic database CLIs.
+**Tools for this phase:** Neon CLI (`neonctl`) / psql (schema — **PRIORITY**), Generic database CLIs.
 
 ---
 
@@ -48,37 +48,37 @@ Automates existing code analysis to generate `schema-analysis.md` with real data
 Verify first with a test call before attempting to use it.
 
 ```
-0. **Docker health check:** Run `docker info --format '{{.ServerVersion}}'` to verify Docker is running.
-   → IF Docker is not running → warn user: "Docker Desktop not running — Supabase local requires Docker."
-   → Ask user via AskUserQuestion: start Docker or fall back to Method B.
+0. **Database connectivity check:** Run `neonctl connection-string` to verify Neon CLI is configured.
+   → IF Neon CLI is not configured → warn user: "Neon CLI not configured — run `neonctl auth`."
+   → Ask user via AskUserQuestion: configure Neon or fall back to Method B.
 
-1. IF Supabase project detected (supabase/ dir exists OR config.json stack includes supabase):
-   → Run `npx supabase status` to verify local Docker is running
+1. IF Neon/PostgreSQL database detected (DATABASE_URL env var exists OR config.json stack includes database):
+   → Run `neonctl connection-string` to get the DB URL
    → IF running (exit 0): extract DB URL from output → Use Method A (direct CLI/psql)
    → IF not running (exit non-zero):
-      → Log: "Supabase local not running — run `npx supabase start`"
-      → Ask user via AskUserQuestion: start it or fall back to Method B
+      → Log: "Neon database not accessible — run `neonctl auth`"
+      → Ask user via AskUserQuestion: configure it or fall back to Method B
 
-2. IF no Supabase detected:
+2. IF no Neon/PostgreSQL database detected:
    → Use Method B (static code analysis)
 ```
 
-**Signs of unavailable local Supabase:**
-- `npx supabase status` exits with non-zero code
-- Docker not running or Supabase containers stopped
-- Project uses database other than Supabase (CloudSQL, RDS, Azure SQL, etc.)
+**Signs of unavailable Neon database:**
+- `neonctl connection-string` exits with non-zero code
+- Neon CLI not authenticated or project not configured
+- Project uses database other than Neon (CloudSQL, RDS, Azure SQL, etc.)
 
-### Step 2A: CLI Method (Preferred — Local Docker)
+### Step 2A: CLI Method (Preferred — Neon CLI)
 
-**Tools:** Bash (Supabase CLI + psql)
+**Tools:** Bash (Neon CLI + psql)
 
 ```bash
-# 0. Get local DB URL (port may vary per instance)
-npx supabase status
-# → Extract "DB URL" line, e.g.: postgresql://postgres:postgres@127.0.0.1:54322/postgres
+# 0. Get DB URL
+neonctl connection-string
+# → Returns connection string, e.g.: postgresql://user:pass@ep-xxx.us-east-2.aws.neon.tech/neondb
 
 # 1. List all tables
-npx supabase db dump --local --schema public 2>/dev/null | grep "CREATE TABLE"
+pg_dump $(neonctl connection-string) --schema public 2>/dev/null | grep "CREATE TABLE"
 
 # 2. For each feature-relevant table:
 
@@ -107,7 +107,7 @@ psql $DB_URL -c "SELECT policyname, cmd, qual FROM pg_policies WHERE tablename =
 **Phase B1: Find Queries**
 
 ```
-Grep: "\.from\(|\.select\(|SELECT |supabase\.|context\.|dbContext\.|DbSet<"
+Grep: "\.from\(|\.select\(|SELECT |context\.|dbContext\.|DbSet<"
 Type: ts,tsx,js,jsx,cs
 Output: files_with_matches
 ```
@@ -138,12 +138,12 @@ Glob: "**/Models/**/*.cs"
 
 Use Task subagent **ONLY** when:
 - Project has 20+ query files
-- Multiple data access patterns (Supabase + EF Core + raw SQL)
+- Multiple data access patterns (Neon + EF Core + raw SQL)
 - Precise cross-context analysis across many files
 
 Do not use Task subagent when:
 - Project has < 10 query files (direct Read is faster)
-- Data access pattern is uniform (only Supabase OR only EF Core)
+- Data access pattern is uniform (only Neon OR only EF Core)
 
 ### Step 2B-Format: Standardized Format for Static Analysis
 

package/framework/skills/level-1-workflows/morph-phase-design/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: morph-phase-design
-description: MORPH-SPEC Phase 2 (Design). Schema-first interactive design: reads EF models/Supabase/DB, validates findings with user, then generates VSA Blueprint based on config.architecture.style, producing spec.md, contracts.cs, schema-analysis.md, and decisions.md through a unified quality + clarification loop (score 0-100). Use after proposal phase to create technical specifications grounded in the real database schema.
+description: MORPH-SPEC Phase 2 (Design). Schema-first interactive design: reads EF models/Neon PostgreSQL/DB, validates findings with user, then generates VSA Blueprint based on config.architecture.style, producing spec.md, contracts.cs, schema-analysis.md, and decisions.md through a unified quality + clarification loop (score 0-100). Use after proposal phase to create technical specifications grounded in the real database schema.
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Agent
-cliVersion: "4.16.0"
+cliVersion: "4.18.0"
 ---
 
 # MORPH Design — Phase 2
@@ -28,7 +28,7 @@ Schema-first interactive design: read the real schema, validate with user, gener
 |--------|------|-------------|
 | Read proposal + UI specs | **Read** output files | — |
 | **Detect architecture** | **Read** `.morph/config/config.json` → check `architecture.style` | **Bash** `grep` |
-| **Schema: Supabase** | **Bash** `npx supabase status` → `npx supabase db dump --local` / `psql <DB_URL>` | **Grep** `.from(` in code |
+| **Schema: Neon PostgreSQL** | **Bash** `neonctl connection-string` → `pg_dump $(neonctl connection-string)` / `psql <DB_URL>` | **Grep** `.from(` in code |
 | **Schema: EF Core** | **Glob** `**/Entities/**/*.cs` + **Glob** `**/*Context.cs` → **Read** | **Grep** `DbSet<` |
 | **Schema: Next.js/TS** | **Glob** `src/**/types/**/*.ts` + **Grep** `interface\|type.*=` | — |
 | Schema: RLS policies | **Bash** `psql <DB_URL> -c "SELECT ... FROM pg_policies"` | **Read** policy files |
@@ -53,8 +53,8 @@ Schema-first interactive design: read the real schema, validate with user, gener
 ## Pre-flight — Tool Availability
 
 Check session context lines for tool readiness:
-- `docker ✓` + `supabase ✓` → Supabase CLI method for schema analysis
-- `docker ✗` or `supabase ✗` → Static code analysis fallback (Grep/Read)
+- `neonctl ✓` → Neon CLI method for schema analysis
+- `neonctl ✗` → Static code analysis fallback (Grep/Read)
 - `context7 ✓` → Use for library docs when writing spec.md
 - `context7 ✗` → WebSearch + WebFetch fallback
 
@@ -116,16 +116,16 @@ If scope ≥ 20 tasks or refactor touches ≥ 5 domain files → **EnterPlanMode
 
 Execute in parallel according to the stack detected in `config.json`:
 
-**Supabase (local Docker via CLI):**
+**Neon PostgreSQL (via Neon CLI):**
 
-> **Supabase CLI:** Run `npx supabase status` to get the local DB URL (port may vary across instances).
-> Then use `npx supabase db dump --local` for full schema export, or `psql <DB_URL>` for targeted queries.
-> Always query the **local Docker instance** — never production. Cross-reference existing schema with the proposal to avoid duplicating tables or missing foreign keys to existing data.
-> If local Supabase is not running, rely on EF Core/TypeScript entity scanning as described below.
+> **Neon CLI (`neonctl`):** Run `neonctl connection-string` to get the DB URL.
+> Then use `pg_dump $(neonctl connection-string)` for full schema export, or `psql <DB_URL>` for targeted queries.
+> Cross-reference existing schema with the proposal to avoid duplicating tables or missing foreign keys to existing data.
+> If Neon database is not accessible, rely on EF Core/TypeScript entity scanning as described below.
 
 ```
-Bash: npx supabase status → extract DB URL
-    + npx supabase db dump --local | grep -A20 "CREATE TABLE relevant_table"
+Bash: neonctl connection-string → extract DB URL
+    + pg_dump $(neonctl connection-string) | grep -A20 "CREATE TABLE relevant_table"
     + psql <DB_URL> -c "SELECT column_name, data_type, is_nullable FROM information_schema.columns WHERE table_name = 'X'"
     + psql <DB_URL> -c "SELECT tablename, policyname, cmd, qual FROM pg_policies WHERE schemaname = 'public'"
 ```

package/framework/skills/level-1-workflows/morph-phase-implement/SKILL.md

@@ -5,7 +5,7 @@ argument-hint: "[feature-name]"
 context: fork
 agent: general-purpose
 user-invocable: false
-cliVersion: "4.16.0"
+cliVersion: "4.18.0"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Agent
 ---
 
@@ -81,9 +81,9 @@ Before starting tasks, verify that CLIs and MCPs needed for this phase are avail
 
 | CLI | Required for | If missing |
 |-----|-------------|------------|
-| `docker` | Container services (Supabase, Redis) | Start Docker Desktop |
-| `supabase` | Migrations, schema, RLS | `npm install -g supabase` |
-| `psql` | Direct DB queries | Included with Supabase CLI or install PostgreSQL client |
+| `docker` | Container services (Redis, etc.) | Start Docker Desktop |
+| `neonctl` | Neon database management, migrations | `npm install -g neonctl` |
+| `psql` | Direct DB queries | Install PostgreSQL client |
 | `az` | Azure resource management | `winget install Microsoft.AzureCLI` |
 | `gh` | GitHub PRs, issues | `winget install GitHub.cli` |
 
@@ -103,7 +103,7 @@ For each MCP showing `✗ (recommended)`:
 | **GitHub** | `gh` CLI |
 | **Vercel** | `vercel` CLI |
 
-> **Design:** This check is fail-open — consistent with morph-spec philosophy. Missing tools are warnings, not blockers (except `docker` for Supabase projects).
+> **Design:** This check is fail-open — consistent with morph-spec philosophy. Missing tools are warnings, not blockers (except `docker` for container-dependent projects).
 
 ---
 
@@ -160,7 +160,7 @@ See `.morph/framework/templates/` for the full template index (abstractions, ext
 | Create new files | **Write** source files | — |
 | Modify existing files | **Edit** source files | — |
 | Look up library API | **Context7 MCP** `query_docs()` | **WebSearch** + **WebFetch** |
-| Run migrations | **Bash** `npx supabase migration up --local` | `psql <DB_URL>` for verification |
+| Run migrations | **Bash** `dotnet ef database update` | `psql <DB_URL>` for verification |
 | Build project | **Bash** `dotnet build` or `npm run build` | — |
 | Run tests | **Bash** `dotnet test` or `npm test` | — |
 | Checkpoint validation | **Bash** `morph-spec validate-feature ...` | — |
@@ -172,9 +172,9 @@ See `.morph/framework/templates/` for the full template index (abstractions, ext
 | Create PR | **Bash** `gh pr create ...` | **GitHub MCP** `create_pull_request()` |
 | Update state | **Bash** `morph-spec state set ...` | — |
 
-**Phase tools:** Docker CLI (container health, logs), Supabase CLI (migrations, RLS — local Docker), Context7 (API lookup), Playwright (smoke test), GitHub (PRs), Vercel (deploy, logs, env vars).
+**Phase tools:** Docker CLI (container health, logs), Neon CLI (`neonctl`) (database management), EF Core CLI (migrations), Context7 (API lookup), Playwright (smoke test), GitHub (PRs), Vercel (deploy, logs, env vars).
 
-> **Supabase CLI:** When creating or running database migrations, use `npx supabase migration new <name>` to create, then `npx supabase migration up --local` to apply against the local Docker instance. Verify with `npx supabase db dump --local --schema public` or `psql` against local instance (get DB URL from `npx supabase status`).
+> **Database Migrations:** When creating or running database migrations, use `dotnet ef migrations add <name>` to create, then `dotnet ef database update` to apply. Verify with `pg_dump $(neonctl connection-string) --schema public` or `psql` against the Neon database (get DB URL from `neonctl connection-string`).
 
 **Anti-patterns:**
 - Task agent for editing a single file (use Edit directly)
@@ -189,7 +189,7 @@ See `.morph/framework/templates/` for the full template index (abstractions, ext
 - **(VSA)** Using `Guid.NewGuid()` — use `Guid.CreateVersion7()`
 - Trying to fix a bug without invoking `systematic-debugging` first
 
-> **Docker CLI:** If a build or test fails with connection errors to local services (Supabase, Redis, etc.), check container health first: `docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"`. For debugging: `docker logs <container> --tail 50` to see recent logs. To restart a stuck container: `docker restart <container>`.
+> **Docker CLI:** If a build or test fails with connection errors to local services (Redis, etc.), check container health first: `docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"`. For debugging: `docker logs <container> --tail 50` to see recent logs. To restart a stuck container: `docker restart <container>`.
 
 ---
 

package/framework/skills/level-1-workflows/morph-phase-plan/SKILL.md

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 3 (Plan). Generates a detailed implementation plan
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.16.0"
+cliVersion: "4.18.0"
 ---
 
 # MORPH Plan — Phase 3

package/framework/skills/level-1-workflows/morph-phase-tasks/SKILL.md

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 4 (Tasks). Breaks approved spec into bottom-up ord
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.16.0"
+cliVersion: "4.18.0"
 ---
 
 # MORPH Tasks — Phase 4