codeninja 2.0.0

package/commands/db-seed.workflow.md

@@ -0,0 +1,99 @@
+---
+type: workflow
+name: db-seed
+command: "@db:seed"
+description: >
+  Add or update seed data for a table. For reference/master data tables,
+  seed goes inside the table setup file. For all others, a standalone seed
+  file is generated in the seeds/ folder.
+---
+
+# Workflow: @db:seed
+
+## Goal
+Generate properly formatted INSERT seed data for a table. Determine whether
+seed belongs in the table file or a standalone seed file.
+
+## Rules
+- Passwords in seed data must be pre-encrypted — agent must ask for encrypted value
+- Never generate plaintext passwords in any file
+- Multi-row INSERT format always (single INSERT with multiple value tuples)
+- Seed file naming: `<repo_root>/database/<db_type>/seeds/<table_name>_seed.sql`
+
+---
+
+## Step-by-Step Execution
+
+### Phase 1 — Target
+1. Run task: `ask-table-name`
+   - List tables from `context.db.schema.tables`
+   - Stores: `context.current_db.table_name`
+
+---
+
+### Phase 2 — Seed File Type
+2. Agent checks if table is a reference/master table:
+   - Reference tables (seed goes IN setup file): tbl_country, tbl_app_content,
+     tbl_strategy_modules, tbl_admin, any lookup table
+   - All others: standalone seed file in seeds/
+
+   Ask: "Where should this seed data go?"
+   Options:
+   1. Append to the table's setup file (for reference/master data)
+   2. Create a standalone seed file in seeds/ (for dev/test data)
+
+   Stores: `context.current_db.seed_target`
+
+---
+
+### Phase 3 — Data Collection
+3. Show column list for the table from context.
+   
+4. Run task: `ask-seed-rows-count`
+   - Ask: "How many rows do you want to seed?"
+   - Stores: `context.current_db.seed_count`
+
+5. For each row (repeat seed_count times):
+   Run task: `ask-seed-row-values`
+   - For each column (excluding `id` and `created_at` — auto-generated):
+     - Ask the value one column at a time
+     - If column is `password` → warn: "Enter the encrypted/hashed value only. Never store plaintext."
+     - If column has CHECK constraint → show allowed values
+     - If column has DEFAULT → offer to use default (user can press enter to skip)
+   - Stores: appends to `context.current_db.seed_rows[]`
+
+---
+
+### Phase 4 — Generate
+6. Show full INSERT preview to user
+   - Ask: "Generate this seed data? (yes / no)"
+
+7. Delegate to `database-agent`:
+
+   If appending to setup file:
+   - Read existing setup file
+   - Append after the GRANT line:
+   ```sql
+   INSERT INTO public.<table_name> (<col1>, <col2>, ...) VALUES
+   (<val1a>, <val2a>, ...),
+   (<val1b>, <val2b>, ...);
+   ```
+
+   If standalone seed file:
+   - Generate: `database/<db_type>/seeds/<table_name>_seed.sql`
+   ```sql
+   -- Seed data for <table_name>
+   -- Environment: development
+   -- Generated: <ISO date>
+
+   INSERT INTO public.<table_name> (<col1>, <col2>, ...) VALUES
+   (<val1a>, <val2a>, ...),
+   (<val1b>, <val2b>, ...);
+   ```
+
+8. Run task: `write-context`
+   - Append to `context.db.schema.change_log`:
+     `{ "type": "seed_added", "table": "<n>", "rows": <count> }`
+   - Clear `context.current_db`
+
+9. Run task: `show-final-summary`

package/commands/db-sync.workflow.md

@@ -0,0 +1,100 @@
+---
+type: workflow
+name: db-sync
+command: "@db:sync"
+description: >
+  Scan all migration files in the database folder and rebuild context.db.schema
+  from actual file contents. Safe to run at any time. Never destructive —
+  only adds or updates, never removes existing context entries.
+---
+
+# Workflow: @db:sync
+
+## Goal
+Make context.db.schema an accurate reflection of what is actually on disk.
+Parse every migration file in order and reconstruct the full schema state.
+
+---
+
+## Step-by-Step Execution
+
+### Phase 1 — Locate Files
+1. Read `context.db.type` to find the correct folder:
+   `<repo_root>/database/<db_type>/migrations/`
+   The database folder is always at repository root, never inside
+   a service folder.
+2. List all `.sql` files in that folder
+3. Sort them in numeric order by filename prefix (1, 2, 3... 111)
+4. Separate into categories:
+   - setup files: `*-setup-tbl-*.sql`
+   - alter files: `*-alter-tbl-*.sql`
+   - drop files: `*-drop-tbl-*.sql`
+   - index file: `111-setup-database-indexes.sql`
+
+---
+
+### Phase 2 — Parse Each File
+For each setup file (in order):
+- Extract table name from CREATE TABLE statement
+- Extract all column names and types
+- Extract CHECK constraints (enum values)
+- Extract COMMENT ON COLUMN lines (enum descriptions)
+- Extract per-file CREATE INDEX lines
+- Note if table has `status`, `is_deleted`, `created_at`
+
+For each alter file (in order after its setup file):
+- Parse ADD COLUMN → add to that table's columns
+- Parse RENAME COLUMN → update column name, record in change_log
+- Parse DROP COLUMN → remove from columns
+- Parse ADD CONSTRAINT → update column's constraint info
+
+For each drop file:
+- Mark that table as dropped in the scan result
+
+For the index file:
+- Parse all CREATE INDEX statements
+- Associate each index with its table
+
+---
+
+### Phase 3 — Rebuild Context
+For each discovered table (not dropped):
+- Compare with existing `context.db.schema.tables[<table>]`
+- Add any tables not already in context
+- Add any columns not already tracked
+- Add any indexes not already tracked
+- For renames found in ALTER files → append to change_log if not already there
+
+For dropped tables:
+- If still in `context.db.schema.tables` → move to change_log snapshot
+- Remove from active tables list
+
+---
+
+### Phase 4 — Rebuild create-schema.sql
+- Re-read all file names in correct numeric order
+- Rewrite `create-schema.sql` to match actual files on disk
+- Report any \i entries that are in create-schema.sql but missing from disk (stale)
+- Report any files on disk not in create-schema.sql (missing)
+
+---
+
+### Phase 5 — Write and Report
+1. Run task: `write-context` with all schema deltas
+2. Display sync report:
+```
+@db:sync complete
+─────────────────────────────────────────
+Migration files scanned : [n]
+Tables discovered       : [n] ([x] new)
+Columns synced          : [n] ([x] new)
+Indexes synced          : [n] ([x] new)
+Renames detected        : [n]
+Dropped tables          : [n]
+create-schema.sql       : updated
+Context gaps filled     : [n]
+─────────────────────────────────────────
+```
+3. If any conflicts found (e.g. column exists in context with different type than file):
+   - List each conflict
+   - Ask user which to keep (file or context) — one at a time

package/commands/design.workflow.md

@@ -0,0 +1,66 @@
+---
+type: workflow
+name: design
+description: >
+  Plan a feature, API contract, or database change before writing any code.
+  Produces a design document and optionally updates context with the planned
+  schema or routes for other agents to reference.
+---
+
+# Workflow: @design
+
+## Goal
+Think before coding. Produce a structured design plan that becomes the
+contract for `@create-api`, `@initialize-project`, or manual implementation.
+
+## Rules
+- No files are generated unless user explicitly confirms
+- Design output is stored in `.codeninja/agent/designs/<feature_name>.design.md`
+- Approved designs update context with planned routes and schema
+
+---
+
+## Step-by-Step Execution
+
+### Phase 1 — Scope
+1. Run task: `ask-design-target`
+   - Options: new feature, new API endpoint, database change, full module
+   - Stores: `context.current_design.type`
+
+2. Run task: `ask-feature-name`
+   - Stores: `context.current_design.feature_name`
+
+3. Run task: `ask-design-description`
+   - Free text: what should this feature do?
+   - Stores: `context.current_design.description`
+
+---
+
+### Phase 2 — Database Design (if applicable)
+4. If design involves data storage:
+   - Delegate to `database-agent`
+   - Design table structure, column types, indexes, relationships
+   - Present schema proposal to user for feedback
+   - Allow user to request changes (one change at a time)
+
+---
+
+### Phase 3 — API Design (if applicable)
+5. If design involves API endpoints:
+   - Delegate to `nodejs-agent`
+   - Propose: method, path, request body, response shape, auth requirement
+   - Present to user for feedback
+
+---
+
+### Phase 4 — Output
+6. Generate `.codeninja/agent/designs/<feature_name>.design.md` containing:
+   - Feature summary
+   - DB schema proposal (tables, columns)
+   - API contracts (method, path, request, response)
+   - Open questions / decisions needed
+
+7. Ask: "Save this design and mark planned routes/schema in context? (yes/no)"
+8. If yes → run task: `write-context` with operation = "design"
+   Then call: context_clear_scratchpad with keys: ["current_design"]
+9. Run task: `show-final-summary`