codeninja 3.2.0 → 4.0.1

package/ide/antigravity/.agents/workflows/codeninja-db-create.md

@@ -1,124 +1,137 @@
+This workflow runs when user invokes /codeninja:db:create
+
 ---
-slash_command: /codeninja:db:create
-personas: [global-orchestrator, database-architect]
-skills: [mcp-and-context, database]
-description: Design and generate a new database table with migration file.
+type: workflow
+name: db-create-table
+command: "@db:create-table"
+description: >
+  Design and generate a new database table following all project conventions.
+  Collects table purpose, name, columns one at a time, then generates the
+  numbered SQL file, updates create-schema.sql, and records in context.
 ---
 
-# /codeninja:db:create
+# Workflow: @db:create-table
 
-## Before Running
-1. Call `context_read` — load `context.db` fully
-2. Call `context_check_stale`
-3. Call `migration_next_number` MCP tool — get next sequential migration number
+## Goal
+Generate a complete, convention-compliant SQL table file. Every generated
+file must pass ALL rules defined in database-agent.md.
 
-## Execution — Full Step-by-Step
+## Rules
+- Ask ONE question at a time — never bundle column definitions
+- Always enforce tbl_ prefix and snake_case naming
+- Never create a table file without updating create-schema.sql
+- Always record in context.db.schema after generation
 
-### Phase 1 — Table Identity
+---
 
-**Step 1.** Ask: "What is this table for?" (free text — used by agent for suggestions)
-- Store: `context.current_db.table_purpose`
+## Step-by-Step Execution
+
+### Phase 1 — Table Identity
+1. Run task: `ask-table-purpose`
+   - Stores: `context.current_db.table_purpose`
+   - Used by agent to suggest column names and structure
 
-**Step 2.** Ask: "Table name?" (must start with `tbl_`, snake_case, lowercase)
-- Enforce prefix and casing
-- Store: `context.current_db.table_name`
+2. Run task: `ask-table-name`
+   - Enforce: lowercase, snake_case, must start with `tbl_`
+   - Stores: `context.current_db.table_name`
 
-**Step 3.** Ask: "Migration file number?" (agent reads migrations/ and suggests next)
-- Call `migration_next_number` to get suggestion
-- Store: `context.current_db.file_number`
+3. Run task: `ask-table-file-number`
+   - Agent reads existing files in `database/<db_type>/migrations/`
+   - Suggests next available number
+   - Stores: `context.current_db.file_number`
 
 ---
 
 ### Phase 2 — Standard Columns Decision
+4. Run task: `ask-table-needs-status`
+   - Ask: "Does this table need status and is_deleted columns?"
+   - Agent guidance: suggest YES for user/entity tables, NO for event/log tables
+   - Stores: `context.current_db.needs_status`
 
-**Step 4.** Ask: "Does this table need `status` and `is_deleted` columns?"
-- Suggest YES for user/entity tables, NO for event/log tables
-- Store: `context.current_db.needs_status`
-
-**Step 5.** Ask: "Does this table support soft delete (`is_deleted`)?"
-- Auto-suggest YES if needs_status is YES
-- Store: `context.current_db.needs_soft_delete`
+5. Run task: `ask-table-needs-soft-delete`
+   - Ask: "Does this table support soft delete (is_deleted)?"
+   - Auto-suggest: YES if needs_status is YES
+   - Stores: `context.current_db.needs_soft_delete`
 
 ---
 
 ### Phase 3 — Column Collection (repeat until done)
-
-**Step 6.** Ask: "Enter next column name (or type 'done' to finish):"
-- Show columns collected so far
-- Enforce: snake_case, lowercase
-- Append to: `context.current_db.columns[]`
-
-**Step 7.** Ask: "Column type?" — show type suggestion based on name pattern:
-- `*_id` → BIGINT NOT NULL DEFAULT 0 (also check for FK — ask if foreign key)
-- `is_*` → BOOLEAN NOT NULL DEFAULT FALSE
-- `*_at` → TIMESTAMPTZ NOT NULL DEFAULT CURRENT_TIMESTAMP
-- `status` → INTEGER NOT NULL DEFAULT 0 CHECK (status IN (0,1))
-- `*_count` → BIGINT NOT NULL DEFAULT 0
-- `*_price`, `*_amount` → NUMERIC(18,8) NOT NULL DEFAULT 0.00000000
-- `email` → VARCHAR(132) NOT NULL DEFAULT ''
-- `phone` → VARCHAR(16) NOT NULL DEFAULT ''
-- `password` → TEXT NOT NULL DEFAULT ''
-- `*_image`, `*_url` → VARCHAR(255) NOT NULL DEFAULT ''
-- `payload`, `metadata`, `*_result` → JSON NOT NULL DEFAULT '{}'
-- default → VARCHAR(255) NOT NULL DEFAULT ''
-
-**Step 8.** Ask: "Does this column have a fixed set of allowed values? (enum-like)"
-- If yes → ask for the allowed values and generate a CHECK constraint + COMMENT
-
-**Step 9.** Return to Step 6 until user types 'done'
+6. Run task: `ask-column-name`
+   - Show columns collected so far
+   - Ask: "Enter the next column name (or type 'done' to finish)"
+   - Enforce: snake_case, lowercase
+   - Stores: appends to `context.current_db.columns[]`
+
+7. Run task: `ask-column-type`
+   - Show suggested type based on column name pattern:
+     - `*_id` → BIGINT NOT NULL DEFAULT 0
+     - When a column name ends in `_id`:
+         - Cross-reference context.db.schema.tables for a table whose name
+         matches the prefix (e.g. user_id → tbl_users)
+         - If found → suggest: "This looks like a foreign key to tbl_users.
+         Add FK constraint? (yes/no)"
+         - If yes → add REFERENCES clause to the column definition
+     - `is_*` → BOOLEAN NOT NULL DEFAULT FALSE
+     - `*_at` → TIMESTAMPTZ NOT NULL DEFAULT CURRENT_TIMESTAMP
+     - `status` → INTEGER NOT NULL DEFAULT 0 CHECK (status IN (0,1))
+     - `*_count` → BIGINT NOT NULL DEFAULT 0
+     - `*_price`, `*_amount` → NUMERIC(18,8) NOT NULL DEFAULT 0.00000000
+     - `email` → VARCHAR(132) NOT NULL DEFAULT ''
+     - `phone` → VARCHAR(16) NOT NULL DEFAULT ''
+     - `password` → TEXT NOT NULL DEFAULT ''
+     - `*_image`, `*_url` → VARCHAR(255) NOT NULL DEFAULT ''
+     - `payload`, `metadata`, `*_result` → JSON NOT NULL DEFAULT '{}'
+     - default → VARCHAR(255) NOT NULL DEFAULT ''
+   - Stores: in current column entry
+
+8. Run task: `ask-column-is-enum`
+   - Ask: "Does this column have a fixed set of allowed values? (enum-like)"
+   - If yes → run task: `ask-column-enum-values`
+   - Stores: check constraint and comment text
+
+9. Return to step 6 until user types 'done'
 
 ---
 
 ### Phase 4 — Index Decision
-
-**Step 10.** Agent auto-suggests indexes based on collected columns:
-- Every `*_id` (FK) column → suggest index
-- `status + is_deleted` compound → suggest if both exist
-- `created_at DESC` → suggest for event/log tables
-Ask user to confirm suggested indexes or add custom ones.
+10. Run task: `ask-table-indexes`
+    - Agent auto-suggests indexes based on collected columns:
+      - Every `*_id` (foreign key) column → suggest index
+      - `status + is_deleted` compound → suggest if both exist
+      - `created_at DESC` → suggest for event/log tables
+    - Ask user to confirm suggested indexes or add custom ones
 
 ---
 
 ### Phase 5 — Seed Data
-
-**Step 11.** Ask: "Does this table need initial/seed data?"
-- Guide: suggest YES only for reference/master data tables
-- If yes → collect row values column by column, repeat per row
-- Store: `context.current_db.seed_rows[]`
+11. Run task: `ask-table-seed-data`
+    - Ask: "Does this table need seed/initial data?"
+    - Guidance: suggest YES only for reference/master data tables
+    - If yes → run task: `collect-seed-data`
+    - Stores: `context.current_db.seed_rows[]`
 
 ---
 
 ### Phase 6 — Summary and Generate
-
-**Step 12.** Show complete table definition:
-- Table name, file number, all columns with types, indexes, seed rows
-- Ask: "Generate this table? (yes / no / change a value)"
-- If change → re-run specific step → return to summary
-- If no → abort
-- If yes → proceed
-
-**Step 13.** Delegate to database-agent:
-- Generate: `<repo_root>/database/<db_type>/migrations/<number>-setup-tbl-<n>.sql`
-  - File header comment
-  - `BEGIN;`
-  - Standard system columns: `id BIGSERIAL PRIMARY KEY`
-  - All collected columns in order
-  - `status INTEGER NOT NULL DEFAULT 0 CHECK (status IN (0,1))` if needs_status
-  - `is_deleted BOOLEAN NOT NULL DEFAULT FALSE` if needs_soft_delete
-  - `created_at TIMESTAMPTZ NOT NULL DEFAULT CURRENT_TIMESTAMP`
-  - All CHECK constraints and COMMENTs for enum columns
-  - All per-table CREATE INDEX statements
-  - GRANT SELECT, INSERT, UPDATE, DELETE to `<db_user>`
-  - Seed data INSERT if collected
-  - `COMMIT;`
-- Update: `<repo_root>/database/<db_type>/create-schema.sql` (add `\i` entry in order)
-- If any indexes belong in shared file → update `111-setup-database-indexes.sql`
-
-**Step 14.** Call `context_write`:
-- Append table to `context.db.schema.tables`
-- Append to `context.db.schema.change_log`
-- Clear `context.current_db`
-
-**Step 15.** Call `context_clear_scratchpad` with keys: ["current_db"]
-
-**Step 16.** Show final summary with file path and next steps.
+12. Run task: `show-db-table-summary`
+    - Display complete table definition as it will be generated
+    - Show: table name, file number, all columns with types, indexes, seed data
+    - Ask: "Generate this table? (yes / no / change a value)"
+    - If change → re-run specific task → return to this step
+    - If no → abort, nothing created
+    - If yes → proceed
+
+> **Multi-agent:** Delegate to `database-architect` via Task invocation for parallel execution.
+> Read `.codeninja/tasks/generate-prisma-schema.task.md` and relevant task files before generating each file.
+
+13. Delegate to `database-agent`:
+    - Generate: `<repo_root>/database/<db_type>/migrations/<number>-setup-tbl-<name>.sql`
+    - Update: `<repo_root>/database/<db_type>/create-schema.sql`
+    - If any indexes belong in shared file → update: `111-setup-database-indexes.sql`
+
+14. Run task: `write-context`
+    - Append table to `context.db.schema.tables`
+    - Append to `context.db.schema.change_log`
+    - Clear `context.current_db`
+
+15. Run task: `show-final-summary`

package/ide/antigravity/.agents/workflows/codeninja-db-drop.md

@@ -1,87 +1,109 @@
+This workflow runs when user invokes /codeninja:db:drop
+
 ---
-slash_command: /codeninja:db:drop
-personas: [global-orchestrator, database-architect]
-skills: [mcp-and-context, database]
-description: Generate a DROP TABLE migration. Never deletes the original setup file.
+type: workflow
+name: db-drop-table
+command: "@db:drop-table"
+description: >
+  Generate a DROP TABLE migration file for an existing table. Removes the
+  table from context, updates create-schema.sql, and records the drop in
+  change_log. Never deletes the original setup file — history is preserved.
 ---
 
-# /codeninja:db:drop
-
-## Before Running
-1. Call `context_read` — load `context.db.schema`
-2. Call `context_check_stale`
+# Workflow: @db:drop-table
 
-## Execution — Full Step-by-Step
+## Goal
+Safely generate a DROP TABLE migration. The original setup file is preserved
+for history. The schema runner will execute the drop when run.
 
-### Phase 1 — Target
-
-**Step 1.** Ask: "Which table to drop?" (list from `context.db.schema.tables`)
-- Store: `context.current_db.table_name`
+## Rules
+- NEVER delete the original <number>-setup-tbl-<n>.sql file
+- ALWAYS generate a new numbered drop migration file
+- ALWAYS warn the user about irreversibility
+- Records in change_log with full before-state for rollback reference
 
 ---
 
-### Phase 2 — Impact Analysis
+## Step-by-Step Execution
 
-**Step 2.** Agent scans context:
-- Check `context.api_routes` for routes referencing this table as `primary_table`
-- Check `context.services` for modules using this table
-- Check `context.db.schema.tables` for FK columns pointing to this table
-
-**Step 3.** If references found, display warning:
-```
-⚠ WARNING: This table is referenced by:
-  - [service]/modules/[Module] (primary_table)
-  - tbl_<other_table>.<col> → <this_table> (FK dependency)
+### Phase 1 — Target
+1. Run task: `ask-table-name`
+   - List tables from `context.db.schema.tables`
+   - Stores: `context.current_db.table_name`
 
-Dropping this table will break these references.
-Make sure to update or remove dependent code first.
-```
-Ask: "Do you still want to proceed? (yes / no)"
-If no → abort.
+---
 
-**Step 4.** Final confirmation:
-Ask: "Type the table name to confirm the drop."
-Must match exactly — if wrong → abort.
+### Phase 2 — Impact Analysis
+2. Agent scans `context`:
+   - Check `context.api_routes` for any routes that reference this table as `primary_table`
+   - Check `context.services` for any modules using this table
+   - Check `context.db.schema.tables` for any other tables with FK columns pointing here
+
+3. If references found:
+   - Display warning:
+     ```
+     ⚠ WARNING: This table is referenced by:
+       - [service]/modules/[Module] (primary_table)
+       - tbl_<other_table>.user_id → tbl_users (FK dependency)
+     
+     Dropping this table will break these references.
+     Make sure to update or remove dependent code first.
+     ```
+   - Ask: "Do you still want to proceed? (yes / no)"
+   - If no → abort
+
+4. Final confirmation:
+   - Ask exactly: "Type the table name to confirm the drop."
+   - Must match exactly — if wrong → abort
+   - Stores: confirmation
 
 ---
 
 ### Phase 3 — File Numbering
-
-**Step 5.** Ask: "Migration file number?" (suggest next available)
-- Store: `context.current_db.file_number`
+5. Run task: `ask-table-file-number`
+   - Suggest: next available number
+   - Stores: `context.current_db.file_number`
 
 ---
 
 ### Phase 4 — Generate
 
-**Step 6.** Delegate to database-agent:
-Generate: `<repo_root>/database/<db_type>/migrations/<number>-drop-tbl-<n>.sql`
-
-```sql
--- Drop tbl_<table_name>
--- Migration: <number>-drop-tbl-<n>.sql
--- Generated: <ISO date>
--- WARNING: This migration is irreversible in production.
--- Original table definition: <original_setup_file>
-
-BEGIN;
-
-DROP TABLE IF EXISTS public.<table_name> CASCADE;
-
-COMMIT;
-```
-
-Update `create-schema.sql`:
-- Keep the original `\i <setup_file>` entry
-- Add the drop file entry AFTER it (never remove original)
-
-**Step 7.** Call `context_write`:
-- Snapshot full column list before removing from active tables
-- Append to `context.db.schema.change_log`:
-  `{ type: "table_dropped", table: "<n>", snapshot: { full column list }, file: "<path>" }`
-- Remove table from `context.db.schema.tables`
-- Clear `context.current_db`
-
-**Step 8.** Call `context_clear_scratchpad` with keys: ["current_db"]
-
-**Step 9.** Show final summary.
+> **Multi-agent:** Delegate to `database-architect` via Task invocation for parallel execution.
+> Read `.codeninja/tasks/` before generating the drop migration file.
+
+6. Delegate to `database-agent`:
+   - Generate: `<repo_root>/database/<db_type>/migrations/<number>-drop-tbl-<n>.sql`
+
+   File contents:
+   ```sql
+   -- Drop tbl_<table_name>
+   -- Migration: <number>-drop-tbl-<n>.sql
+   -- Generated: <ISO date>
+   -- WARNING: This migration is irreversible in production.
+   -- Original table definition: <original_setup_file>
+
+   BEGIN;
+
+   DROP TABLE IF EXISTS public.<table_name> CASCADE;
+
+   COMMIT;
+   ```
+
+   - Update: `database/<db_type>/create-schema.sql`
+     - Keep the original `\i <setup_file>` entry
+     - Add the drop file entry AFTER it
+
+7. Run task: `write-context`
+   - Move table from `context.db.schema.tables` → save columns snapshot
+   - Append to `context.db.schema.change_log`:
+     ```json
+     {
+       "type": "table_dropped",
+       "table": "<table_name>",
+       "snapshot": { "<full column list saved here>" },
+       "file": "<drop_file_path>"
+     }
+     ```
+   - Clear `context.current_db`
+
+8. Run task: `show-final-summary`

package/ide/antigravity/.agents/workflows/codeninja-db-index.md

@@ -1,70 +1,102 @@
+This workflow runs when user invokes /codeninja:db:index
+
 ---
-slash_command: /codeninja:db:index
-personas: [global-orchestrator, database-architect]
-skills: [mcp-and-context, database]
-description: Add a new index to an existing table.
+type: workflow
+name: db-add-index
+command: "@db:add-index"
+description: >
+  Add a new index to an existing table. Determines whether the index belongs
+  in the table's own file (new tables) or in 111-setup-database-indexes.sql
+  (shared/cross-service indexes). Updates context and create-schema.sql.
 ---
 
-# /codeninja:db:index
+# Workflow: @db:add-index
+
+## Goal
+Generate a properly named CREATE INDEX statement and place it in the correct
+file. Follow all index naming conventions from database-agent.md.
 
-## Before Running
-1. Call `context_read` — load `context.db.schema`
-2. Call `context_check_stale`
+---
 
-## Execution — Full Step-by-Step
+## Step-by-Step Execution
 
 ### Phase 1 — Target Table
+1. Run task: `ask-table-name`
+   - List tables from `context.db.schema.tables`
+   - Stores: `context.current_db.table_name`
 
-**Step 1.** Ask: "Which table?" (list from `context.db.schema.tables`)
-- Store: `context.current_db.table_name`
+---
 
 ### Phase 2 — Index Columns
+2. Run task: `ask-index-columns`
+   - Ask: "Which column(s) should this index cover?"
+   - List available columns from `context.db.schema.tables[<table>].columns`
+   - Allow selecting one or multiple columns (compound index)
+   - Stores: `context.current_db.index_columns[]`
+
+3. Run task: `ask-index-sort-order`
+   - Ask: "Should any column in this index be sorted descending?"
+   - Common case: `created_at DESC`, `time DESC`
+   - If yes → ask which column(s) should be DESC
+   - Stores: `context.current_db.index_desc_columns[]`
+
+4. Run task: `ask-index-type`
+   - Ask: "Is this a standard index or a partial index?"
+   - Options:
+     1. Standard index (covers all rows)
+     2. Partial index (only indexes rows matching a condition)
+   - If partial → ask: "Enter the WHERE condition."
+     Example: `WHERE is_deleted = FALSE`
+   - Stores: `context.current_db.index_where_clause`
 
-**Step 2.** Ask: "Which column(s) for this index?"
-- List available columns from `context.db.schema.tables[<table>].columns`
-- Allow one or multiple (compound index)
-- Store: `context.current_db.index_columns[]`
-
-**Step 3.** Ask: "Should any column be sorted DESC?" (common: `created_at DESC`, `time DESC`)
-- If yes → ask which column(s)
-- Store: `context.current_db.index_desc_columns[]`
-
-**Step 4.** Ask: "Standard or partial index?"
-- Standard: covers all rows
-- Partial: only rows matching a WHERE condition — if partial, ask for WHERE clause
-- Store: `context.current_db.index_where_clause`
+---
 
 ### Phase 3 — File Placement
+5. Run task: `ask-index-file-placement`
+   - Ask: "Where should this index be defined?"
+   - Options:
+     1. In the table's own setup file (for new/just-created tables)
+     2. In 111-setup-database-indexes.sql (for existing tables, shared use)
+   - Auto-suggest option 2 if table already has a setup file in migrations
+   - Stores: `context.current_db.index_file`
 
-**Step 5.** Ask: "Where should this index be defined?"
-1. In the table's own setup file (for new/just-created tables)
-2. In `111-setup-database-indexes.sql` (for existing tables — auto-suggested)
-- Store: `context.current_db.index_file`
+---
 
 ### Phase 4 — Generate
-
-**Step 6.** Agent auto-generates index name:
-- In table file: `idx_<table_without_tbl_prefix>_<columns_joined>`
-- In shared file: `idx_tbl_<table_without_tbl_prefix>_<columns_joined>`
-- Show: "Index will be named: <name> — OK? (yes / rename)"
-
-**Step 7.** Confirm: "Generate this index? (yes / no)"
-
-**Step 8.** Delegate to database-agent:
-```sql
---
--- Name: <index_name>; Type: INDEX; Schema: public
---
-CREATE INDEX <index_name> ON public.<table_name> (<col> [DESC], ...)
-  [WHERE <where_clause>];
-```
-Append to correct file (table setup file OR `111-setup-database-indexes.sql`).
-
-**Step 9.** Call `context_write`:
-- Append index to `context.db.schema.tables[<table>].indexes`
-- Append to `context.db.schema.change_log`
-- Clear `context.current_db`
-
-**Step 10.** Call `context_clear_scratchpad` with keys: ["current_db"]
-
-**Step 11.** Show final summary.
+6. Agent auto-generates the index name following convention:
+   - In table file: `idx_<table_without_tbl_prefix>_<columns_joined>`
+   - In shared file: `idx_tbl_<table_without_tbl_prefix>_<columns_joined>`
+   - Show name to user: "Index will be named: <n> — OK? (yes / rename)"
+
+7. Confirm: "Generate this index? (yes / no)"
+
+> **Multi-agent:** Delegate to `database-architect` via Task invocation for parallel execution.
+> Read `.codeninja/tasks/` before generating the index.
+
+8. Delegate to `database-agent`:
+   - If table file placement → append to `<repo_root>/database/<db_type>/migrations/<table_file>.sql`
+   - If shared file → append to `<repo_root>/database/<db_type>/migrations/111-setup-database-indexes.sql`
+
+   Generated SQL:
+   ```sql
+   -- Standard
+   CREATE INDEX <index_name> ON public.<table_name> (<col> [DESC], ...);
+
+   -- Partial
+   CREATE INDEX <index_name> ON public.<table_name> (<col> [DESC], ...)
+     WHERE <where_clause>;
+   ```
+
+   With standard header comment:
+   ```sql
+   --
+   -- Name: <index_name>; Type: INDEX; Schema: public
+   --
+   ```
+
+9. Run task: `write-context`
+   - Append index name to `context.db.schema.tables[<table>].indexes`
+   - Append to `context.db.schema.change_log`
+   - Clear `context.current_db`
+
+10. Run task: `show-final-summary`