codeninja 2.0.0

package/package.json

@@ -0,0 +1,24 @@
+{
+    "name": "codeninja",
+    "version": "2.0.0",
+    "description": "AI agent scaffolding system — NodeJS, ReactJS, and database projects",
+    "private": false,
+    "bin": {
+        "codeninja": "cli.js"
+    },
+    "files": [
+        ".gitattributes",
+        "cli.js",
+        "mcp-server.js",
+        "agent/",
+        "commands/",
+        "tasks/",
+        "README.md"
+    ],
+    "dependencies": {
+        "@modelcontextprotocol/sdk": "^1.0.0"
+    },
+    "engines": {
+        "node": ">=18.0.0"
+    }
+}

package/tasks/README.md

@@ -0,0 +1,283 @@
+# Code Ninja Agent System
+
+AI-powered agentic scaffolding and development assistant for your project.
+
+---
+
+## Folder Structure
+
+```
+.codeninja/agent/
+  global-agent.md               ← Master orchestrator
+  nodejs-agent.md               ← NodeJS backend expert
+  reactjs-agent.md              ← ReactJS frontend expert
+  database-agent.md             ← Database architect (PostgreSQL / MySQL / MongoDB)
+  designs/                      ← @design output files (auto-created)
+
+.codeninja/commands/
+  initialize-project.workflow.md
+  create-api.workflow.md
+  design.workflow.md
+  audit.workflow.md
+  test.workflow.md
+  refactor.workflow.md
+  sync.workflow.md
+  db-create-table.workflow.md
+  db-modify-table.workflow.md
+  db-add-index.workflow.md
+  db-drop-table.workflow.md
+  db-seed.workflow.md
+  db-sync.workflow.md
+
+.codeninja/tasks/
+  ── Project Info ──────────────────────────────
+  ask-project-info-doc.task.md
+  ask-project-scope-of-work.task.md
+  ask-project-figma.task.md
+
+  ── Repository & Init ─────────────────────────
+  detect-repository-state.task.md
+  ask-project-type.task.md
+  ask-service-name.task.md
+  ask-service-port.task.md
+  ask-service-description.task.md
+  ask-package-name.task.md
+  ask-package-author.task.md
+  ask-api-key.task.md
+  ask-encryption-key.task.md
+  ask-encryption-iv.task.md
+  ask-redis-host.task.md
+  ask-redis-port.task.md
+  ask-redis-config.task.md
+  show-init-summary.task.md
+  ask-client-type.task.md
+  ask-encrypted-transport.task.md
+  ask-supported-languages.task.md
+  ask-init-mode.task.md
+  generate-fast-defaults.task.md
+
+  ── Database Config ───────────────────────────
+  ask-database-type.task.md
+  ask-database-name.task.md
+  ask-database-host.task.md
+  ask-database-port.task.md
+  ask-database-user.task.md
+  ask-database-config.task.md
+
+  ── Database Table Operations ─────────────────
+  ask-table-purpose.task.md
+  ask-table-name.task.md
+  ask-table-file-number.task.md
+  ask-table-needs-status.task.md
+  ask-table-needs-soft-delete.task.md
+  ask-table-indexes.task.md
+  ask-table-seed-data.task.md
+  show-db-table-summary.task.md
+
+  ── Column Operations ─────────────────────────
+  ask-column-name.task.md
+  ask-column-type.task.md
+  ask-column-is-enum.task.md
+  ask-column-enum-values.task.md
+  ask-column-position.task.md
+  ask-old-column-name.task.md
+  ask-new-column-name.task.md
+  ask-modify-operation.task.md
+
+  ── Index Operations ──────────────────────────
+  ask-index-columns.task.md
+  ask-index-sort-order.task.md
+  ask-index-type.task.md
+  ask-index-file-placement.task.md
+
+  ── Seed Data ─────────────────────────────────
+  ask-seed-rows-count.task.md
+  ask-seed-row-values.task.md
+
+  ── API & Module Operations ───────────────────
+  ask-target-service.task.md
+  ask-module-name.task.md
+  ask-http-method.task.md
+  ask-route-path.task.md
+  ask-route-description.task.md
+  ask-primary-table.task.md
+  ask-requires-auth.task.md
+  ask-api-version.task.md
+
+  ── Design & Refactor ─────────────────────────
+  ask-design-target.task.md
+  ask-feature-name.task.md
+  ask-design-description.task.md
+  ask-refactor-type.task.md
+  ask-table-name.task.md
+  ask-new-table-name.task.md
+
+  ── Test ──────────────────────────────────────
+  ask-test-type.task.md
+
+  ── Output & Context ──────────────────────────
+  write-context.task.md
+  show-final-summary.task.md
+
+  ── Utilities Generation ──────────────────────────────
+  generate-encryption.task.md
+  generate-response.task.md
+  generate-validator.task.md
+  generate-headerValidator.task.md
+  generate-logging.task.md
+  generate-app.task.md
+  generate-rateLimiter.task.md
+  generate-route-manager.task.md
+  generate-constants.task.md
+  generate-database.task.md
+  generate-template.task.md
+  generate-language-en.task.md
+  generate-ioRedis.task.md
+  generate-notification.task.md
+  generate-common.task.md
+  generate-route.task.md
+  generate-model.task.md
+  generate-enc-dec-html.task.md
+  generate-enc-dec-php.task.md
+  generate-package-json.task.md
+  generate-readme.task.md
+  generate-gitignore.task.md
+  generate-swagger.task.md
+
+── System Tables ─────────────────────────
+  generate-tbl-user-deviceinfo.task.md
+
+.codeninja/context/
+  context.json                  ← Shared memory for all agents (auto-managed)
+```
+
+---
+
+## Available Commands
+
+### Project Initialization
+| Command | Description |
+|---|---|
+| `@initialize-project` | Bootstrap a new NodeJS service, ReactJS app, or database |
+
+### API & Service Development
+| Command | Description |
+|---|---|
+| `@create-api` | Add a new API module to an existing service |
+| `@design` | Plan a feature or schema before writing code |
+| `@audit` | Review a service for security, quality, and consistency |
+| `@test` | Generate or run tests for a module |
+| `@refactor` | Rename or restructure code with full change tracking |
+| `@sync` | Scan the entire repo and rebuild context.json |
+
+### Database Commands
+| Command | Description |
+|---|---|
+| `@db:create-table` | Design and generate a new table following all conventions |
+| `@db:modify-table` | Add/rename/drop a column via ALTER migration file |
+| `@db:add-index` | Add a new index to an existing table |
+| `@db:drop-table` | Generate a DROP migration and clean up context |
+| `@db:seed` | Add or update seed data for a table |
+| `@db:sync` | Scan migration files and rebuild context.db.schema |
+
+---
+
+## How It Works
+
+1. **You run a command** — e.g. `@initialize-project`
+2. **Global agent activates** — reads `.codeninja/context/context.json` for full awareness
+3. **Project info is collected first (once)** — document, SOW, Figma link → builds project summary
+4. **Workflow runs** — routes to the right agent (NodeJS, ReactJS, Database)
+5. **Tasks execute one at a time** — each asks exactly one question
+6. **Single confirmation** — you approve the summary once, then all files are generated
+7. **Context is updated** — every action recorded in `context.json`
+
+---
+
+## Key Design Principles
+
+### One Question Per Task
+Every `ask-*` task collects exactly one value. No multi-field forms.
+
+### Single Confirmation Per Operation
+After collecting all required values, a summary is shown once.
+You confirm once → everything generates. No per-file prompts.
+
+### Context is the Brain
+`.codeninja/context/context.json` is the shared memory for all agents.
+- Every service, route, table, column, and change is stored here
+- All agents read it before making any decision
+- The `change_log` gives a full history of every structural change
+
+### Database First
+During `@initialize-project`, the database folder is always scaffolded
+before any application service code. This ensures NodeJS services are
+generated with accurate DB config and column awareness.
+
+### Project Info Awareness
+When you provide a project document, SOW, or Figma link during initialization,
+the agent extracts entities, features, and tech preferences. Every subsequent
+command uses this context to make smarter suggestions.
+
+---
+
+## Database File Convention
+
+Every table follows this structure:
+```
+database/
+  <db_type>/
+    migrations/
+      1-setup-tbl-<name>.sql    ← One file per table, numbered
+      2-setup-tbl-<name>.sql
+      ...
+      111-setup-database-indexes.sql  ← Shared indexes, always last
+    seeds/
+      <table>_seed.sql          ← Standalone seed files
+    create-schema.sql           ← Auto-generated runner (do not edit)
+    setup-database.sh           ← Linux/Mac setup script
+    setup-database.ps1          ← Windows setup script
+    reset-database.sh           ← Dev-only full reset (dangerous)
+  README.md
+```
+
+### Running the Database
+```bash
+# Linux/Mac — creates DB and runs all migrations
+cd database/<db_type>
+bash setup-database.sh
+
+# Windows
+cd database/<db_type>
+.\setup-database.ps1
+```
+
+---
+
+## Multi-Service Projects
+
+Each service gets its own entry in `context.services`:
+```json
+{
+  "services": {
+    "auth":    { "type": "nodejs",  "port": 1001 },
+    "ledger":  { "type": "nodejs",  "port": 1002 },
+    "frontend":{ "type": "reactjs", "port": 3000 }
+  }
+}
+```
+
+All services share the same `context.db` — they reference the same database
+schema and the same table/column names.
+
+---
+
+## Getting Started
+
+1. Run `@initialize-project`
+2. Answer Phase 0 questions (project doc, SOW, Figma) — once per repo
+3. Choose project type (NodeJS, ReactJS, Database)
+4. Configure database
+5. Name your service and configure it
+6. Confirm once → everything is generated
+7. Run `@db:create-table` to start adding your first table

package/tasks/add-health-route.task.md

@@ -0,0 +1,103 @@
+---
+type: task
+name: add-health-route
+agent: nodejs-agent
+---
+
+# Add Health Check Route
+
+## Purpose
+Adds a `/health` endpoint to the default service module for Docker health checks
+and monitoring systems. This should be added during the route generation in Wave 4.
+
+---
+
+## Implementation
+
+When generating the default module's `route.js` file in `modules/v1/<ServiceName>/route.js`,
+add this health check route:
+
+```javascript
+/**
+ * Health check endpoint for container orchestration and monitoring.
+ *
+ * @param {Object} req - Express request object.
+ * @param {Object} res - Express response object.
+ */
+router.get('/health', (req, res) => {
+  res.status(200).json({
+    status: 'healthy',
+    timestamp: new Date().toISOString(),
+    service: process.env.npm_package_name || 'unknown',
+    uptime: process.uptime()
+  });
+});
+```
+
+---
+
+## Location in File
+
+Place this route FIRST in the route.js file, before any other routes.
+This ensures health checks work even if other routes have issues.
+
+---
+
+## Response Format
+
+```json
+{
+  "status": "healthy",
+  "timestamp": "2024-03-20T10:30:45.123Z",
+  "service": "auth",
+  "uptime": 12345.678
+}
+```
+
+---
+
+## Security Note
+
+- This endpoint is PUBLIC (no authentication required)
+- Does not expose sensitive information
+- Returns only service health status and basic metadata
+- Safe to be called by Docker, Kubernetes, load balancers, etc.
+
+---
+
+## Integration with Dockerfile
+
+The Dockerfile health check uses this endpoint:
+```dockerfile
+HEALTHCHECK --interval=30s --timeout=3s --start-period=40s --retries=3 \
+  CMD node -e "require('http').get('http://localhost:{port}/api/v1/{module}/health', (r) => process.exit(r.statusCode === 200 ? 0 : 1))"
+```
+
+Where:
+- `{port}` is the service port
+- `{module}` is the lowercase module name (e.g., "auth")
+
+---
+
+## Context Registration
+
+Add this route to context during initialization:
+
+```javascript
+context.api_routes.push({
+  service: context.current_init.service_name,
+  method: 'GET',
+  path: `/api/v1/${moduleName.toLowerCase()}/health`,
+  auth: 'none',
+  description: 'Health check endpoint'
+});
+```
+
+---
+
+## Notes
+
+- Always returns 200 status when service is running
+- Can be extended later to check database connectivity, Redis, etc.
+- Used by Docker, Kubernetes, AWS ECS, load balancers
+- Should be the first route registered (top of the file)

package/tasks/ask-api-integration-scope.task.md

@@ -0,0 +1,34 @@
+---
+type: task
+name: ask-api-integration-scope
+---
+
+Read `context.current_action.page_path` — the target page already set.
+
+Ask the user exactly this question:
+
+"What would you like to integrate on this page?"
+
+Present options:
+1. All forms and actions — wire up every form submit and every
+   button action on the page to an API call
+2. A specific form or action — I'll describe which one
+
+Wait for user selection.
+
+Store result in: `context.current_action.api_integration_scope`
+- Option 1 → "all"
+- Option 2 → "specific"
+
+If option 2 (specific):
+  Ask the user exactly this question:
+
+  "Describe the form or action you want to integrate.
+  Example: 'the login form', 'the delete button in the user card',
+  'the search filter submit'"
+
+  Wait for user input.
+  Store result in: `context.current_action.api_integration_target`
+
+Do not ask any other question in this task beyond the scope and
+optional description questions above.

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

@@ -0,0 +1,23 @@
+---
+type: task
+name: ask-api-key
+---
+
+Generate a secure suggested value: random 32-character alphanumeric string.
+
+Ask the user exactly this question:
+
+"Enter the API key for this service (used in x-api-key header)."
+
+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:
+- Minimum 16 characters
+- No spaces
+
+Store result in: `context.current_init.api_key`
+
+Do not ask any other question in this task.

package/tasks/ask-api-version.task.md

@@ -0,0 +1,28 @@
+---
+type: task
+name: ask-api-version
+---
+
+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>].versions` if available.
+
+If only v1 exists (most common case):
+  Inform user: "Using API version: v1"
+  Store automatically: `context.current_api.version = "v1"`
+  Return without asking.
+
+If multiple versions exist OR user is adding a new version:
+  Ask the user exactly this question:
+
+  "Which API version will this endpoint belong to?"
+
+  List existing versions and add option for new version.
+
+  Wait for user selection.
+
+Store result in: `context.current_api.version`
+
+Do not ask any other question in this task.

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

@@ -0,0 +1,24 @@
+---
+type: task
+name: ask-client-type
+---
+
+Ask the user exactly this question:
+
+"Who will be consuming this API?"
+
+Present options:
+1. ReactJS web frontend — uses crypto-js for encryption
+2. Mobile / desktop app — uses cryptlib for encryption
+
+Wait for user selection.
+
+Store result in: `context.current_init.client_type`
+- Option 1 → "reactjs"
+- Option 2 → "app"
+
+This value determines:
+- Which encryption library is used in utilities/encryption.js
+- Whether enc_dec.html or enc_dec.php is generated
+
+Do not ask any other question in this task.

package/tasks/ask-column-enum-values.task.md

@@ -0,0 +1,51 @@
+---
+type: task
+name: ask-column-enum-values
+---
+
+Read the last column in `context.current_db.columns`.
+Let col = that column.
+
+Ask the user exactly this question:
+
+"Enter the allowed values for '[col_name]', separated by commas."
+
+Example input: I, S, L
+Example input: Pending, Running, Completed
+Example input: 0, 1
+
+Wait for user input.
+
+Parse the input into a list of values.
+Trim whitespace from each value.
+
+Ask the user exactly this question:
+
+"Now provide a short label for each value (for the COMMENT)."
+
+Show each value and ask for its label:
+"What does '[value]' mean?"
+
+Example:
+  'I' → Intraday
+  'S' → Short Term
+  'L' → Long Term
+
+Collect one label per value (one at a time).
+
+Build the COMMENT string:
+  Format: '[value1] = [label1], [value2] = [label2], ...'
+  Example: 'I = Intraday, S = Short Term, L = Long Term'
+
+Store results in `context.current_db.columns[last]`:
+  - `check_values`: ["I", "S", "L"]
+  - `check_comment`: "I = Intraday, S = Short Term, L = Long Term"
+  - `default_value`: first value in the list (user can override)
+
+Also ask:
+"What should the DEFAULT value be for this column?"
+Show options: [list of allowed values]
+
+Store: `context.current_db.columns[last].default_value`
+
+Do not ask any other question in this task after collecting all labels and default.

package/tasks/ask-column-is-enum.task.md

@@ -0,0 +1,39 @@
+---
+type: task
+name: ask-column-is-enum
+---
+
+Read the last column in `context.current_db.columns`.
+Let col = that column.
+
+Skip this task automatically if:
+- Column type is BOOLEAN
+- Column type is TIMESTAMPTZ
+- Column type is JSON
+- Column name ends in `_id`
+- Column name ends in `_at`
+
+Otherwise:
+
+Ask the user exactly this question:
+
+"Does column '[col_name]' have a fixed set of allowed values?"
+
+Example: trade_type can only be 'I', 'S', or 'L'
+Example: status can only be 0 or 1
+
+Present options:
+1. Yes — add a CHECK constraint with allowed values
+2. No — any valid value is allowed
+
+Wait for user selection.
+
+If No:
+  Store: `context.current_db.columns[last].is_enum = false`
+  Return.
+
+If Yes:
+  Store: `context.current_db.columns[last].is_enum = true`
+  → Immediately run task: `ask-column-enum-values`
+
+Do not ask any other question in this task.

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

@@ -0,0 +1,39 @@
+---
+type: task
+name: ask-column-name
+---
+
+Read `context.current_db.columns` to show columns collected so far.
+
+If columns already exist, display them:
+"Columns defined so far:
+  [n]. [col_name] — [type]
+  ..."
+
+Agent suggests next column based on `context.current_db.table_purpose`
+and common patterns. For example:
+- User tables → suggest: first_name, last_name, email, phone, password, profile_image
+- Bot tables → suggest: user_id, bot_name, symbol, strategy, status
+- Notification tables → suggest: user_id, content, is_read
+
+Show suggestion if available:
+"Suggested next column: [suggestion] (press enter to use, or type your own)"
+
+Ask the user exactly this question:
+
+"Enter the next column name (or type 'done' to finish adding columns)."
+
+Wait for user input.
+
+Validate:
+- Must be lowercase snake_case
+- No spaces or camelCase
+- Must not already exist in `context.current_db.columns`
+- If 'done' → end column collection loop
+
+If input is camelCase (e.g. 'userId') → auto-convert to snake_case ('user_id')
+and inform the user: "Converted to snake_case: user_id"
+
+Store result in: new entry appended to `context.current_db.columns[]`
+
+Do not ask any other question in this task.

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

@@ -0,0 +1,39 @@
+---
+type: task
+name: ask-column-position
+---
+
+Read `context.current_db.table_name` and `context.db.schema.tables[<table>].columns`
+to list the current columns in order.
+
+Display current column order:
+"Current columns in '[table_name]':
+  1. id
+  2. user_id
+  3. email
+  4. created_at
+  ..."
+
+Read `context.db.type`.
+
+If db_type == "mysql":
+  Show: "MySQL supports AFTER <col> — the column will be physically placed
+  after '[selected_column]' in the table."
+
+If db_type == "postgresql":
+  Show: "Note: In PostgreSQL, ADD COLUMN always appends to the end physically.
+  The position here is for documentation only."
+
+If db_type == "mongodb":
+  Skip this task entirely — MongoDB documents have no fixed column order.
+  Store: `context.current_db.new_column_after = null`
+  Return.
+
+Present: numbered list of current columns
+Add option: "End of table (default)"
+
+Wait for user selection.
+
+Store result in: `context.current_db.new_column_after`
+
+Do not ask any other question in this task.