codeninja 2.0.0

package/tasks/ask-column-type.task.md

@@ -0,0 +1,59 @@
+---
+type: task
+name: ask-column-type
+---
+
+Read `context.current_db.columns` — get the column name just added.
+Let col = last column in the array.
+
+Agent auto-detects suggested type based on column name pattern:
+
+| Pattern              | Suggested Type                                            |
+|----------------------|-----------------------------------------------------------|
+| `*_id`               | BIGINT NOT NULL DEFAULT 0                                 |
+| `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`, `*_total` | BIGINT NOT NULL DEFAULT 0                                 |
+| `*_price`, `*_amount`, `*_fee` | NUMERIC(18,8) NOT NULL DEFAULT 0.00000000    |
+| `*_percentage`, `*_rate` | NUMERIC(6,2) NOT NULL DEFAULT 0.00                   |
+| `*_volume`           | NUMERIC(20,8) NOT NULL DEFAULT 0.00000000                 |
+| `email`              | VARCHAR(132) NOT NULL DEFAULT ''                          |
+| `phone`              | VARCHAR(16) NOT NULL DEFAULT ''                           |
+| `password`           | TEXT NOT NULL DEFAULT ''                                  |
+| `*_image`, `*_icon`, `*_url` | VARCHAR(255) NOT NULL DEFAULT ''                 |
+| `*_name` (person)    | VARCHAR(64) NOT NULL DEFAULT ''                           |
+| `*_name` (entity)    | VARCHAR(256) NOT NULL DEFAULT ''                          |
+| `symbol`             | VARCHAR(32) NOT NULL DEFAULT ''                           |
+| `timezone`           | VARCHAR(64) NOT NULL DEFAULT ''                           |
+| `token`, `uuid`      | TEXT NOT NULL DEFAULT ''                                  |
+| `payload`, `metadata`, `*_result`, `content` | JSON NOT NULL DEFAULT '{}'     |
+| `strategy`           | VARCHAR(256) NOT NULL DEFAULT ''                          |
+| `description`, `*_text`, `*_html` | TEXT NOT NULL DEFAULT ''                  |
+| `version`            | VARCHAR(64) NOT NULL DEFAULT ''                           |
+| `ip`                 | VARCHAR(45) NOT NULL DEFAULT ''  (supports IPv6)          |
+| default              | VARCHAR(255) NOT NULL DEFAULT ''                          |
+
+Display:
+"Suggested type for '[col_name]': [suggested_type]"
+"Press enter to accept or choose a different type."
+
+Present quick options if suggestion might not fit:
+1. Use suggested: [suggested_type]
+2. VARCHAR with custom length
+3. TEXT
+4. INTEGER
+5. BIGINT
+6. BOOLEAN
+7. NUMERIC (custom precision)
+8. TIMESTAMPTZ
+9. JSON
+10. Enter manually
+
+Wait for user selection or enter.
+
+Validate manual entry: must be valid PostgreSQL type syntax.
+
+Store result in: `context.current_db.columns[last].type`
+
+Do not ask any other question in this task.

package/tasks/ask-database-config.task.md

@@ -0,0 +1,66 @@
+---
+type: task
+name: ask-database-config
+---
+
+## Purpose
+Collects all database connection details in a single grouped display.
+Only called in manual init mode. In fast mode, these values are
+auto-populated by generate-fast-defaults.
+
+Read `context.db.type` to determine the correct port default.
+
+## Display
+
+Show this grouped prompt:
+```
+DATABASE CONNECTION
+───────────────────────────────────────────
+Database name   : [cursor — required]
+Database host   : localhost
+Database port   : [5432 / 3306 / 27017 based on db type]
+Database user   : [cursor — required]
+Database password: (leave blank — added to .env manually)
+───────────────────────────────────────────
+Press ENTER on any field to accept the shown default.
+Name and user are required — no default exists for them.
+```
+
+## Field Rules
+
+### Database name
+- Required — no default
+- Validate: lowercase, no spaces, underscores allowed
+- Example: ledgersystem, myapp_db
+- Store in: `context.db.name`
+
+### Database host
+- Default: `localhost`
+- If user presses enter → use "localhost"
+- Store in: `context.db.host`
+
+### Database port
+- Default: determined by `context.db.type`:
+  - postgresql → 5432
+  - mysql → 3306
+  - mongodb → 27017
+- If user presses enter → use the type default
+- Validate: must be a valid port number (1–65535)
+- Store in: `context.db.port`
+
+### Database user
+- Required — no default
+- Store in: `context.db.user`
+
+### Database password
+- Not collected here — intentionally left out
+- The .env file will have `DB_PASSWORD=` blank
+- Developer fills it in manually after generation
+- This is a security practice — passwords are never stored in context
+
+## After Collection
+
+Inform user:
+"Database config saved. Host: [host]:[port], DB: [name], User: [user]"
+
+Do not ask any other question in this task.

package/tasks/ask-database-host.task.md

@@ -0,0 +1,16 @@
+---
+type: task
+name: ask-database-host
+---
+
+Ask the user exactly this question:
+
+"Enter the database host."
+
+Show default: localhost
+
+If user presses enter without input → use "localhost".
+
+Store result in: `context.db.host`
+
+Do not ask any other question in this task.

package/tasks/ask-database-name.task.md

@@ -0,0 +1,18 @@
+---
+type: task
+name: ask-database-name
+---
+
+Ask the user exactly this question:
+
+"Enter the database name."
+
+Example: ledgersystem, myapp_db
+
+Wait for user input.
+
+Validate: lowercase, no spaces, underscores allowed.
+
+Store result in: `context.db.name`
+
+Do not ask any other question in this task.

package/tasks/ask-database-port.task.md

@@ -0,0 +1,23 @@
+---
+type: task
+name: ask-database-port
+---
+
+Read `context.db.type` to determine the suggested default:
+- postgresql → 5432
+- mysql → 3306
+- mongodb → 27017
+
+Ask the user exactly this question:
+
+"Enter the database port."
+
+Show suggested default based on db type.
+
+If user presses enter without input → use the suggested default.
+
+Validate: must be a valid port number (1–65535).
+
+Store result in: `context.db.port`
+
+Do not ask any other question in this task.

package/tasks/ask-database-type.task.md

@@ -0,0 +1,30 @@
+---
+type: task
+name: ask-database-type
+---
+
+Check `context.db.type` first.
+
+If `context.db.type` already exists:
+  Inform user: "Your project is already using [db_type]."
+  Ask: "Do you want to use the same database for this service?"
+  - If yes → store existing value → return
+  - If no → continue asking
+
+Ask the user exactly this question:
+
+"Which database will this service use?"
+
+Present options:
+1. PostgreSQL
+2. MySQL
+3. MongoDB
+
+Wait for user selection.
+
+Store result as:
+- PostgreSQL → `context.db.type = "postgresql"`
+- MySQL → `context.db.type = "mysql"`
+- MongoDB → `context.db.type = "mongodb"`
+
+Do not ask any other question in this task.

package/tasks/ask-database-user.task.md

@@ -0,0 +1,14 @@
+---
+type: task
+name: ask-database-user
+---
+
+Ask the user exactly this question:
+
+"Enter the database username."
+
+Wait for user input.
+
+Store result in: `context.db.user`
+
+Do not ask any other question in this task.

package/tasks/ask-design-description.task.md

@@ -0,0 +1,16 @@
+---
+type: task
+name: ask-design-description
+---
+
+Ask the user exactly this question:
+
+"Describe what this feature or design should do."
+
+Example: "Allow users to register, login, and manage sessions using JWT tokens."
+
+Wait for user input. Accept free text.
+
+Store result in: `context.current_design.description`
+
+Do not ask any other question in this task.

package/tasks/ask-design-target.task.md

@@ -0,0 +1,24 @@
+---
+type: task
+name: ask-design-target
+---
+
+Ask the user exactly this question:
+
+"What would you like to design?"
+
+Present options:
+1. New feature (end-to-end: DB + API + frontend)
+2. New API endpoint only
+3. Database schema change
+4. Full new module (controller + service + model + routes)
+
+Wait for user selection.
+
+Store result in: `context.current_design.type`
+- Option 1 → "feature"
+- Option 2 → "api"
+- Option 3 → "db_change"
+- Option 4 → "module"
+
+Do not ask any other question in this task.

package/tasks/ask-encrypted-transport.task.md

@@ -0,0 +1,25 @@
+---
+type: task
+name: ask-encrypted-transport
+---
+
+Ask the user exactly this question:
+
+"Should request and response bodies be AES encrypted in transit?"
+
+Show guidance:
+"If yes — all API responses will be encrypted using AES-256-CBC before
+sending. The client must decrypt them. API key and IV will still be
+collected and used for password encryption regardless of this choice."
+
+Present options:
+1. Yes — encrypt request and response bodies
+2. No — plain JSON transport (encryption only used for passwords)
+
+Wait for user selection.
+
+Store result in: `context.current_init.encrypted_transport`
+- Option 1 → true
+- Option 2 → false
+
+Do not ask any other question in this task.

package/tasks/ask-encryption-iv.task.md

@@ -0,0 +1,23 @@
+---
+type: task
+name: ask-encryption-iv
+---
+
+Generate a secure suggested value: exactly first 16 alphanumeric characters of `context.current_init.encryption_key`.
+
+Ask the user exactly this question:
+
+"Enter the AES-256-CBC initialization vector (must be exactly 16 characters)."
+
+Show: "Suggested (auto-generated): [generated_value]"
+Show: "Press enter to use the suggested value, or type your own."
+
+If user presses enter without input → use the generated value.
+
+Validate:
+- MUST be exactly 16 characters
+- If not 16 characters → reject and explain: "AES-256-CBC IV requires exactly 16 characters. Please try again."
+
+Store result in: `context.current_init.encryption_iv`
+
+Do not ask any other question in this task.

package/tasks/ask-encryption-key.task.md

@@ -0,0 +1,23 @@
+---
+type: task
+name: ask-encryption-key
+---
+
+Generate a secure suggested value: exactly 32 random alphanumeric characters.
+
+Ask the user exactly this question:
+
+"Enter the AES-256 encryption key (must be exactly 32 characters)."
+
+Show: "Suggested (auto-generated): [generated_value]"
+Show: "Press enter to use the suggested value, or type your own."
+
+If user presses enter without input → use the generated value.
+
+Validate:
+- MUST be exactly 32 characters
+- If not 32 characters → reject and explain: "AES-256 requires exactly 32 characters. Please try again."
+
+Store result in: `context.current_init.encryption_key`
+
+Do not ask any other question in this task.

package/tasks/ask-feature-name.task.md

@@ -0,0 +1,20 @@
+---
+type: task
+name: ask-feature-name
+---
+
+Ask the user exactly this question:
+
+"Enter a name for this feature or design."
+
+Example: user-authentication, product-catalog, invoice-generation
+
+Wait for user input.
+
+Validate:
+- Lowercase, hyphens allowed, no spaces
+- This will become the filename: .codeninja/agent/designs/<name>.design.md
+
+Store result in: `context.current_design.feature_name`
+
+Do not ask any other question in this task.

package/tasks/ask-http-method.task.md

@@ -0,0 +1,21 @@
+---
+type: task
+name: ask-http-method
+---
+
+Ask the user exactly this question:
+
+"Which HTTP method will this endpoint use?"
+
+Present options:
+1. GET
+2. POST
+3. PUT
+4. PATCH
+5. DELETE
+
+Wait for user selection.
+
+Store result in: `context.current_api.method`
+
+Do not ask any other question in this task.

package/tasks/ask-index-columns.task.md

@@ -0,0 +1,46 @@
+---
+type: task
+name: ask-index-columns
+---
+
+Read `context.current_db.table_name` and `context.db.schema.tables[<table>].columns`
+to list available columns.
+
+Display current columns:
+"Columns in '[table_name]':
+  1. id
+  2. user_id
+  3. email
+  4. status
+  5. is_deleted
+  6. created_at
+  ..."
+
+Ask the user exactly this question:
+
+"Which column should this index cover?"
+
+Wait for user selection (select one column number).
+
+Store first column in: `context.current_db.index_columns = [<col>]`
+
+Then ask:
+
+"Is this a single-column index or a compound index (multiple columns)?"
+
+Present options:
+1. Single column — done
+2. Compound — add another column
+
+If compound:
+  Repeat: "Add the next column to this index (or 'done' to finish)."
+  Show remaining columns not yet selected.
+  Append each selection to `context.current_db.index_columns[]`
+  Until user selects 'done' or all columns are selected.
+
+  Note on compound index order:
+  "Tip: Put the most selective column first (e.g. email before is_deleted)."
+
+Store final list in: `context.current_db.index_columns[]`
+
+Do not ask any other question in this task.

package/tasks/ask-index-file-placement.task.md

@@ -0,0 +1,33 @@
+---
+type: task
+name: ask-index-file-placement
+---
+
+Read `context.current_db.table_name` and check if that table's setup file
+already exists in `database/<db_type>/migrations/`.
+
+Auto-suggest based on context:
+- If table was JUST created in this session → suggest option 1 (table's own file)
+- If table already existed before this session → suggest option 2 (shared index file)
+
+Ask the user exactly this question:
+
+"Where should this index be defined?"
+
+Present options:
+1. In the table's own setup file
+   (e.g. 7-setup-tbl-user-bots.sql)
+   → Best for: indexes tightly coupled to this table's structure
+
+2. In the shared index file (111-setup-database-indexes.sql)
+   → Best for: indexes added after initial setup, cross-service use
+
+Show suggestion: "Suggested: [option] — [reason]"
+
+Wait for user selection.
+
+Store result in: `context.current_db.index_file`
+- Option 1 → "table_file"
+- Option 2 → "shared_file"
+
+Do not ask any other question in this task.

package/tasks/ask-index-sort-order.task.md

@@ -0,0 +1,37 @@
+---
+type: task
+name: ask-index-sort-order
+---
+
+Read `context.current_db.index_columns` to check which columns are in the index.
+
+Auto-detect: if any column in index_columns ends in `_at` or is named `time`
+or `event_time` → strongly suggest DESC for that column.
+
+If no timestamp-like columns in index → skip this task entirely and
+set `context.current_db.index_desc_columns = []`.
+
+Ask the user exactly this question:
+
+"Should any column in this index be sorted in descending order (DESC)?"
+
+Show suggestion if applicable:
+"Suggested: '[col_name]' DESC — common for timestamp columns used in
+ORDER BY ... DESC queries."
+
+Present options:
+1. Yes — one or more columns should be DESC
+2. No — all columns ascending (default)
+
+Wait for user selection.
+
+If Yes:
+  For each column in `context.current_db.index_columns`:
+    Ask: "Should '[col]' be ASC or DESC?"
+    Options: 1. ASC (default)  2. DESC
+    Store per-column sort direction.
+
+Store result in: `context.current_db.index_desc_columns[]`
+(list of column names that should be DESC)
+
+Do not ask any other question in this task.

package/tasks/ask-index-type.task.md

@@ -0,0 +1,42 @@
+---
+type: task
+name: ask-index-type
+---
+
+Ask the user exactly this question:
+
+"Is this a standard index or a partial index?"
+
+Present options:
+1. Standard index — covers all rows in the table
+2. Partial index — only indexes rows matching a WHERE condition
+
+Show guidance:
+"Partial indexes are useful when queries always filter by a specific condition.
+Example: WHERE is_deleted = FALSE — if you never query deleted records,
+a partial index on active records only is smaller and faster."
+
+Wait for user selection.
+
+Store result in: `context.current_db.index_type`
+- Option 1 → "standard"
+- Option 2 → "partial"
+
+If "partial":
+  Ask the user exactly this question:
+
+  "Enter the WHERE condition for this partial index."
+
+  Examples:
+    WHERE is_deleted = FALSE
+    WHERE status = 0
+    WHERE botstatus = 'Running'
+
+  Wait for input.
+
+  Validate: must start with WHERE or be a valid SQL condition.
+  (Agent can prepend WHERE if user forgets it.)
+
+  Store result in: `context.current_db.index_where_clause`
+
+Do not ask any other question in this task.

package/tasks/ask-init-mode.task.md

@@ -0,0 +1,28 @@
+---
+type: task
+name: ask-init-mode
+---
+
+Ask the user exactly this question:
+
+"How would you like to set up this service?"
+
+Present options:
+1. Fast setup — I'll auto-generate secure values for keys, ports,
+   and config. You only answer the essentials (9 questions).
+2. Manual setup — Walk me through every value one at a time
+   (22 questions).
+
+Wait for user selection.
+
+Store result in: `context.current_init.init_mode`
+- Option 1 → "fast"
+- Option 2 → "manual"
+
+Show guidance based on selection:
+- If fast → "Great. I'll generate secure defaults for all technical
+  config. You'll see everything in the summary before any files
+  are created — you can change any value there."
+- If manual → "Understood. I'll ask you each value individually."
+
+Do not ask any other question in this task.

package/tasks/ask-linked-service.task.md

@@ -0,0 +1,57 @@
+---
+type: task
+name: ask-linked-service
+---
+
+Read `context.services` and filter for services where `type == "nodejs"`.
+
+## If no NodeJS services exist
+
+Inform the user:
+
+"A ReactJS frontend cannot be initialized without a linked NodeJS backend
+service. No NodeJS services are registered in this project yet.
+
+Please run @initialize-project and select NodeJS first, then come back to
+initialize your ReactJS frontend."
+
+Abort the workflow. Do not proceed.
+
+## If exactly one NodeJS service exists
+
+Inform the user:
+"Your ReactJS app will be linked to: [service_name] (port [port])"
+
+Store automatically:
+- `context.current_init.linked_service = <service_name>`
+- `context.current_init.linked_service_port = <port>`
+- `context.current_init.encryption_key = context.services[service_name].encryption_key`
+- `context.current_init.encryption_iv = context.services[service_name].encryption_iv`
+- `context.current_init.api_key = context.services[service_name].api_key`
+
+Return without asking. Proceed to next step.
+
+## If multiple NodeJS services exist
+
+Ask the user exactly this question:
+
+"Which backend NodeJS service will this ReactJS app connect to?"
+
+List only NodeJS services (skip reactjs and database-only entries):
+  1. [service_name] — port [port] — [description]
+  2. [service_name] — port [port] — [description]
+
+Wait for user selection.
+
+After selection, store:
+- `context.current_init.linked_service = <selected_service_name>`
+- `context.current_init.linked_service_port = <selected_port>`
+- `context.current_init.encryption_key = context.services[selected].encryption_key`
+- `context.current_init.encryption_iv = context.services[selected].encryption_iv`
+- `context.current_init.api_key = context.services[selected].api_key`
+
+Confirm to user:
+"Linked to: [service_name]. Encryption keys and API key will be inherited
+automatically — you will not be asked for them."
+
+Do not ask any other question in this task.

package/tasks/ask-modify-operation.task.md

@@ -0,0 +1,36 @@
+---
+type: task
+name: ask-modify-operation
+---
+
+Read `context.current_db.table_name` to show context.
+
+Ask the user exactly this question:
+
+"What modification do you want to make to '[table_name]'?"
+
+Present options:
+1. Add a new column
+2. Rename a column
+3. Drop a column
+4. Change a column's data type
+5. Add a CHECK constraint to an existing column
+6. Add a new index → (routes to @db:add-index)
+
+Wait for user selection.
+
+Store result in: `context.current_db.modify_operation`
+- Option 1 → "add_column"
+- Option 2 → "rename_column"
+- Option 3 → "drop_column"
+- Option 4 → "change_type"
+- Option 5 → "add_constraint"
+- Option 6 → "add_index"
+
+If option 6 selected:
+  Store: `context.current_db.modify_operation = "add_index"`
+  Inform user: "This will run the @db:add-index workflow."
+  Return to workflow — do not trigger the sub-workflow directly.
+  The calling workflow (db-modify-table) will handle the route.
+
+Do not ask any other question in this task.