codeninja 2.0.0

package/tasks/ask-modularize-scope.task.md

@@ -0,0 +1,31 @@
+---
+type: task
+name: ask-modularize-scope
+---
+
+Ask the user exactly this question:
+
+"What would you like to modularize?"
+
+Present options:
+1. All pages — scan every page in src/pages/ and modularize all of them
+2. A specific page — I'll ask you which one
+
+Wait for user selection.
+
+Store result in: `context.current_action.modularize_scope`
+- Option 1 → "all"
+- Option 2 → "specific"
+
+If option 1 (all):
+  Inform user:
+  "Understood. I'll scan every page and extract shared layout components
+  (header, footer, sidebar, navbar, etc.) once, then apply them across
+  all pages. Pages that already use components will be left unchanged."
+  Return. Do not ask anything else.
+
+If option 2 (specific):
+  Run task: `ask-page-path`
+  (This stores the target page into context.current_action.page_path)
+
+Do not ask any other question in this task beyond the scope question.

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

@@ -0,0 +1,30 @@
+---
+type: task
+name: ask-module-name
+---
+
+Read service name from context — check in this order:
+  1. `context.current_api.service_name`
+  2. `context.current_action.service_name`
+Use whichever is populated.
+Read `context.services[<resolved_service_name>].modules` if available.
+
+If modules exist, show them:
+"Existing modules in this service: [list]"
+
+Ask the user exactly this question:
+
+"Enter the module name."
+
+Example: Products, Orders, Invoice, Users
+
+Wait for user input.
+
+Validate:
+- PascalCase recommended (e.g. Products not products)
+- Must NOT already exist in the service's modules list
+- If duplicate → inform user and ask again
+
+Store result in: `context.current_action.module_name`
+
+Do not ask any other question in this task.

package/tasks/ask-new-column-name.task.md

@@ -0,0 +1,21 @@
+---
+type: task
+name: ask-new-column-name
+---
+
+Read `context.current_refactor.old_column_name` to show the current name.
+
+Ask the user exactly this question:
+
+"Enter the new name for column '[old_column_name]'."
+
+Wait for user input.
+
+Validate:
+- snake_case only
+- No spaces
+- Must not already exist in the same table's columns in context
+
+Store result in: `context.current_refactor.new_column_name`
+
+Do not ask any other question in this task.

package/tasks/ask-new-table-name.task.md

@@ -0,0 +1,22 @@
+---
+type: task
+name: ask-new-table-name
+---
+
+Read `context.current_refactor.table_name` to show the current name.
+
+Ask the user exactly this question:
+
+"Enter the new name for table '[current_table_name]'."
+
+Wait for user input.
+
+Validate:
+- Must be lowercase snake_case
+- Must start with tbl_
+- Must not already exist in `context.db.schema.tables`
+- No spaces
+
+Store result in: `context.current_refactor.new_table_name`
+
+Do not ask any other question in this task.

package/tasks/ask-old-column-name.task.md

@@ -0,0 +1,22 @@
+---
+type: task
+name: ask-old-column-name
+---
+
+Read table name from context — check in this order:
+  1. `context.current_refactor.table_name` (if called from @refactor)
+  2. `context.current_db.table_name` (if called from @db:modify-table)
+Use whichever is populated.
+Read `context.db.schema.tables[<table_name>].columns` to list available columns.
+
+Ask the user exactly this question:
+
+"Which column do you want to rename?"
+
+List all columns for the selected table from context.
+
+Wait for user selection.
+
+Store result in: `context.current_refactor.old_column_name`
+
+Do not ask any other question in this task.

package/tasks/ask-package-author.task.md

@@ -0,0 +1,16 @@
+---
+type: task
+name: ask-package-author
+---
+
+Ask the user exactly this question:
+
+"Enter the author name for package.json."
+
+Example: John Doe
+
+Wait for user input.
+
+Store result in: `context.current_init.author`
+
+Do not ask any other question in this task.

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

@@ -0,0 +1,23 @@
+---
+type: task
+name: ask-package-name
+---
+
+Read `context.current_init.service_name` and use it as the suggested default.
+
+Ask the user exactly this question:
+
+"Enter the npm package name for this service."
+
+Show suggested default: [service_name]
+
+If user presses enter without input → use the service_name as-is.
+
+Validate:
+- Lowercase
+- No spaces
+- Valid npm package name format
+
+Store result in: `context.current_init.package_name`
+
+Do not ask any other question in this task.

package/tasks/ask-page-path.task.md

@@ -0,0 +1,40 @@
+---
+type: task
+name: ask-page-path
+---
+
+Read `context.current_action.service_name`.
+Read `context.services[<service_name>]`.
+
+Scan the service's `src/pages/` directory to build a list of available pages.
+For each subdirectory in `src/pages/` that contains an `index.jsx` or
+`index.js` file → add it to the list as a valid page target.
+
+Also scan `src/views/` if it exists — include those as well.
+
+If pages are found, display them:
+"Available pages in [service_name]:"
+  1. [PageName] — src/pages/[PageName]/index.jsx
+  2. [PageName] — src/pages/[PageName]/index.jsx
+  ...
+
+Ask the user exactly this question:
+
+"Which page would you like to target?
+Enter the page name from the list above, or type a custom path
+relative to src/ (e.g. pages/Login/index.jsx)"
+
+Wait for user input.
+
+Validate:
+- If a name from the list was entered → resolve to the full path
+- If a custom path was entered → verify the file exists on disk
+- If the file cannot be found → inform user and ask again
+
+Store result in:
+- `context.current_action.page_name` — the page/component display name
+  (e.g. "Login", "Dashboard")
+- `context.current_action.page_path` — the full relative path from service
+  root (e.g. "src/pages/Login/index.jsx")
+
+Do not ask any other question in this task.

package/tasks/ask-primary-table.task.md

@@ -0,0 +1,30 @@
+---
+type: task
+name: ask-primary-table
+---
+
+Read `context.db.schema.tables` to get list of available tables.
+
+If no tables exist in context:
+  Inform user: "No tables found in context. Run @sync or @initialize-project first to register your schema."
+  Ask: "Enter the table name manually."
+  Store result and continue.
+
+If tables exist:
+  Ask the user exactly this question:
+
+  "Which database table will this endpoint primarily interact with?"
+
+  List all tables from context.db.schema.tables with their column count.
+  Example:
+    1. users (7 columns)
+    2. products (12 columns)
+    3. orders (9 columns)
+
+  Add option: "None (this endpoint does not use a DB table)"
+
+  Wait for user selection.
+
+Store result in: `context.current_api.primary_table`
+
+Do not ask any other question in this task.

package/tasks/ask-project-figma.task.md

@@ -0,0 +1,71 @@
+---
+type: task
+name: ask-project-figma
+---
+
+Check `context.project_info.has_figma` — if already set, skip this task entirely.
+
+Ask the user exactly this question:
+
+"Do you have a Figma design file or any UI design link for this project?"
+
+Present options:
+1. Yes — I have a Figma or design link
+2. No — skip this
+
+Wait for user selection.
+
+If No:
+  Store: `context.project_info.has_figma = false`
+  Return. Do not ask anything else.
+
+If Yes:
+  Store: `context.project_info.has_figma = true`
+
+  Ask the user exactly this question:
+
+  "Enter the Figma link or design URL."
+
+  Wait for input.
+
+  Validate:
+    - Should be a URL (starts with https://)
+    - Figma links typically contain figma.com — inform user if it doesn't look like a Figma link,
+      but still accept it (could be InVision, Zeplin, Adobe XD, etc.)
+
+  Store: `context.project_info.figma_url = <url>`
+
+  Ask the user exactly this question:
+
+  "Is this Figma link publicly accessible or does it require a login?"
+
+  Present options:
+  1. Publicly accessible — anyone with the link can view
+  2. Requires login — I'll describe the screens manually
+
+  Wait for user selection.
+
+  If publicly accessible:
+    Store: `context.project_info.figma_accessible = true`
+    Agent notes: "Figma link stored. Will reference for screen names, component
+    naming, and UI structure when generating ReactJS components or API contracts."
+
+  If requires login:
+    Store: `context.project_info.figma_accessible = false`
+
+    Ask the user exactly this question:
+
+    "Briefly describe the main screens or pages in your design."
+
+    Example: "Login, Register, Dashboard, Profile, Product List, Product Detail, Cart, Checkout"
+
+    Wait for input.
+    Store: `context.project_info.figma_screens = <input>`
+
+  After collecting:
+    Extract and store in `context.project_info.from_figma`:
+      - screens: [] (list of screen/page names identified)
+      - components_hinted: [] (any reusable components visible or described)
+      - color_theme: "" (if determinable from description)
+
+Do not ask any other question in this task.

package/tasks/ask-project-info-doc.task.md

@@ -0,0 +1,57 @@
+---
+type: task
+name: ask-project-info-doc
+---
+
+Check `context.project_info.has_doc` — if already set, skip this task entirely.
+
+Ask the user exactly this question:
+
+"Do you have a project information document or requirement document?
+(This helps the agent understand your project deeply for better suggestions)"
+
+Present options:
+1. Yes — I have a document
+2. No — skip this
+
+Wait for user selection.
+
+If No:
+  Store: `context.project_info.has_doc = false`
+  Return. Do not ask anything else.
+
+If Yes:
+  Store: `context.project_info.has_doc = true`
+
+  Ask the user exactly this question:
+
+  "How would you like to provide your project document?"
+
+  Present options:
+  1. Paste a URL or hosted link
+  2. Paste the content directly in chat
+
+  Wait for user selection.
+
+  If URL:
+    Ask: "Enter the document URL."
+    Wait for input.
+    Store: `context.project_info.doc_url = <url>`
+    Store: `context.project_info.doc_source = "url"`
+
+  If paste:
+    Ask: "Paste your project document content below."
+    Wait for input.
+    Store: `context.project_info.doc_content = <content>`
+    Store: `context.project_info.doc_source = "paste"`
+
+  After collecting content:
+    Extract and store in `context.project_info.from_doc`:
+      - project_name: (if mentioned)
+      - domain: (e.g. fintech, ecommerce, healthcare)
+      - purpose: (one sentence summary of what the product does)
+      - features: [] (list of features/modules mentioned)
+      - entities: [] (data entities mentioned: users, products, orders, etc.)
+      - tech_preferences: [] (any tech mentioned: nodejs, react, postgres, etc.)
+
+Do not ask any other question in this task.

package/tasks/ask-project-scope-of-work.task.md

@@ -0,0 +1,57 @@
+---
+type: task
+name: ask-project-scope-of-work
+---
+
+Check `context.project_info.has_sow` — if already set, skip this task entirely.
+
+Ask the user exactly this question:
+
+"Do you have a Scope of Work (SOW) or project specification document?"
+
+Present options:
+1. Yes — I have a SOW
+2. No — skip this
+
+Wait for user selection.
+
+If No:
+  Store: `context.project_info.has_sow = false`
+  Return. Do not ask anything else.
+
+If Yes:
+  Store: `context.project_info.has_sow = true`
+
+  Ask the user exactly this question:
+
+  "How would you like to provide your Scope of Work?"
+
+  Present options:
+  1. Paste a URL or hosted link
+  2. Paste the content directly in chat
+
+  Wait for user selection.
+
+  If URL:
+    Ask: "Enter the Scope of Work URL."
+    Wait for input.
+    Store: `context.project_info.sow_url = <url>`
+    Store: `context.project_info.sow_source = "url"`
+
+  If paste:
+    Ask: "Paste your Scope of Work content below."
+    Wait for input.
+    Store: `context.project_info.sow_content = <content>`
+    Store: `context.project_info.sow_source = "paste"`
+
+  After collecting content:
+    Extract and store in `context.project_info.from_sow`:
+      - phases: [] (project phases or milestones if listed)
+      - deliverables: [] (specific deliverables mentioned)
+      - apis_expected: [] (any APIs or endpoints mentioned)
+      - tables_expected: [] (any data structures or entities mentioned)
+      - integrations: [] (third-party services: payment gateways, SMS, email, etc.)
+      - constraints: [] (performance, security, compliance requirements mentioned)
+      - timeline: "" (any timeline info mentioned)
+
+Do not ask any other question in this task.

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

@@ -0,0 +1,24 @@
+---
+type: task
+name: ask-project-type
+---
+
+Ask the user exactly this question:
+
+"What type of project would you like to initialize?"
+
+Present options:
+1. NodeJS API service
+2. ReactJS frontend
+3. Database only (schema + migrations, no application code)
+
+Wait for user selection.
+
+Validate: must be one of the three options.
+
+Store result as:
+- `nodejs` → `context.current_init.project_type = "nodejs"`
+- `reactjs` → `context.current_init.project_type = "reactjs"`
+- `database-only` → `context.current_init.project_type = "database-only"`
+
+Do not ask any other question in this task.

package/tasks/ask-react-target-service.task.md

@@ -0,0 +1,32 @@
+---
+type: task
+name: ask-react-target-service
+---
+
+Read `context.services` and filter for services where `type == "reactjs"`.
+
+If no ReactJS services exist:
+  Inform user:
+  "No ReactJS services have been initialized yet. Run @initialize-project
+  and select ReactJS first, then run this command again."
+  Abort task.
+
+If exactly one ReactJS service exists:
+  Inform user: "Using ReactJS service: [service_name] (port [port])"
+  Store automatically: `context.current_action.service_name = <only_service>`
+  Return without asking.
+
+If multiple ReactJS services exist:
+  Ask the user exactly this question:
+
+  "Which ReactJS service would you like to work on?"
+
+  List only ReactJS services:
+    1. [service_name] — port [port] — [description]
+    2. [service_name] — port [port] — [description]
+
+  Wait for user selection.
+
+Store result in: `context.current_action.service_name`
+
+Do not ask any other question in this task.

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

@@ -0,0 +1,42 @@
+---
+type: task
+name: ask-redis-config
+---
+
+## Purpose
+Collects Redis 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.
+
+## Display
+
+Show this grouped prompt:
+```
+REDIS CONNECTION
+───────────────────────────────────────────
+Redis host   : localhost
+Redis port   : 6379
+───────────────────────────────────────────
+Press ENTER on either field to accept the shown default.
+Most local setups use localhost:6379.
+```
+
+## Field Rules
+
+### Redis host
+- Default: `localhost`
+- If user presses enter → use "localhost"
+- Store in: `context.current_init.redis_host`
+
+### Redis port
+- Default: `6379`
+- If user presses enter → use 6379
+- Validate: must be a valid port number (1–65535)
+- Store in: `context.current_init.redis_port`
+
+## After Collection
+
+Inform user:
+"Redis config saved. [redis_host]:[redis_port]"
+
+Do not ask any other question in this task.

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

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

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

@@ -0,0 +1,18 @@
+---
+type: task
+name: ask-redis-port
+---
+
+Ask the user exactly this question:
+
+"Enter the Redis port for this service."
+
+Show default: 6379
+
+If user presses enter without input → use 6379.
+
+Validate: must be a valid port number (1–65535).
+
+Store result in: `context.current_init.redis_port`
+
+Do not ask any other question in this task.

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

@@ -0,0 +1,26 @@
+---
+type: task
+name: ask-refactor-type
+---
+
+Ask the user exactly this question:
+
+"What would you like to refactor?"
+
+Present options:
+1. Rename a database column
+2. Rename a database table
+3. Rename a service
+4. Rename a module
+5. Restructure files within a service
+
+Wait for user selection.
+
+Store result in: `context.current_refactor.type`
+- Option 1 → "rename_column"
+- Option 2 → "rename_table"
+- Option 3 → "rename_service"
+- Option 4 → "rename_module"
+- Option 5 → "restructure"
+
+Do not ask any other question in this task.

package/tasks/ask-requires-auth.task.md

@@ -0,0 +1,22 @@
+---
+type: task
+name: ask-requires-auth
+---
+
+Ask the user exactly this question:
+
+"Does this endpoint require authentication?"
+
+Present options:
+1. Yes — apply API key + JWT middleware
+2. API key only — apply headerValidator middleware only
+3. No — public endpoint, no auth middleware
+
+Wait for user selection.
+
+Store result in: `context.current_api.requires_auth`
+- Option 1 → "full"
+- Option 2 → "api_key_only"
+- Option 3 → "none"
+
+Do not ask any other question in this task.

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

@@ -0,0 +1,38 @@
+---
+type: task
+name: ask-response-mode
+---
+
+Ask the user exactly this question:
+
+"What response code format should API responses use?"
+
+Show guidance:
+"This controls what the 'code' field in every API response contains.
+
+  Standard HTTP mode — the 'code' field echoes the HTTP status code.
+    Example success:  { code: 200, message: '...', data: {...} }
+    Example failure:  { code: 401, message: '...' }
+
+  Company mode (0/1) — the 'code' field uses internal status values.
+    1  = success
+    0  = failure / business logic error
+   -1  = authentication error
+    Example success:  { code: 1, message: '...', data: {...} }
+    Example failure:  { code: 0, message: '...' }
+
+Both modes always send the correct HTTP status code on the wire (200,
+401, 500 etc). This setting only controls what goes inside the response
+body's 'code' field."
+
+Present options:
+1. Standard HTTP codes — code field mirrors the HTTP status (200, 401, 500…)
+2. Company codes — code field uses 1 / 0 / -1 internal values
+
+Wait for user selection.
+
+Store result in: `context.current_init.response_mode`
+- Option 1 → "http"
+- Option 2 → "company"
+
+Do not ask any other question in this task.

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

@@ -0,0 +1,20 @@
+---
+type: task
+name: ask-route-description
+---
+
+Ask the user exactly this question:
+
+"Enter a short description for this endpoint."
+
+Example: "Fetch all products with pagination"
+
+Wait for user input.
+
+Store result in: `context.current_api.description`
+
+This description will be used in:
+- swagger_doc.json summary field
+- Controller file JSDoc comment
+
+Do not ask any other question in this task.