code-ai-installer 1.2.0 → 1.3.1

package/locales/en/.agents/current_state_analysis/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
-  display_name: "Analysis of the current repository architecture"
-  short_description: "Analysis of the current repository architecture: conventions, patterns, technical debt, scaling…"
-  default_prompt: "Use $current_state_analysis when the task matches the \"Analysis of the current repository architecture\" skill."
+  display_name: "Current State Analysis: <project-name>"
+  short_description: "Analysis of the current repository architecture ? conventions, patterns, tech debt, scaling bot…"
+  default_prompt: "Use $current_state_analysis when the task matches the \"Current State Analysis: <project-name>\" skill."
 dependencies:
   tools: []
 policy:

package/locales/en/.agents/current_state_analysis/agents/qwen.json

@@ -1,12 +1,13 @@
 {
   "name": "current_state_analysis",
-  "display_name": "Analysis of the current repository architecture",
-  "description": "Analysis of the current repository architecture: conventions, patterns, technical debt, scaling bottlenecks, security risks and consistency.",
-  "default_prompt": "Use $current_state_analysis when the task matches the \"Analysis of the current repository architecture\" skill.",
+  "display_name": "Current State Analysis: <project-name>",
+  "description": "Analysis of the current repository architecture ? conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency.",
+  "default_prompt": "Use $current_state_analysis when the task matches the \"Current State Analysis: <project-name>\" skill.",
   "triggers": [
     "current_state_analysis",
     "current state analysis",
-    "Analysis of the current repository architecture"
+    "Current State Analysis: <project-name>",
+    "Analysis of the current repository architecture ? conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency"
   ],
   "capabilities": [
     "current",

package/locales/en/.agents/current_state_analysis/agents/skill.yaml

@@ -1,12 +1,13 @@
 version: 1
 name: "current_state_analysis"
-display_name: "Analysis of the current repository architecture"
-description: "Analysis of the current repository architecture: conventions, patterns, technical debt, scaling bottlenecks, security risks and consistency."
-default_prompt: "Use $current_state_analysis when the task matches the \"Analysis of the current repository architecture\" skill."
+display_name: "Current State Analysis: <project-name>"
+description: "Analysis of the current repository architecture ? conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency."
+default_prompt: "Use $current_state_analysis when the task matches the \"Current State Analysis: <project-name>\" skill."
 triggers:
   - "current_state_analysis"
   - "current state analysis"
-  - "Analysis of the current repository architecture"
+  - "Current State Analysis: <project-name>"
+  - "Analysis of the current repository architecture ? conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency"
 capabilities:
   - "current"
   - "state"

package/locales/en/.agents/data_model/SKILL.md

@@ -1,40 +1,285 @@
 ---
 name: data_model
-description: Data model and storage strategy: normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency - with trade-offs and binding to UX flows.
+description: Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency — with trade-offs and tied to UX flows.
 ---
 
 # Skill: Data Model
 
-## Goal
-Support product scenarios and prepare the base for growth.
+Model data: from entity definitions to query optimization.
+
+**Sections:**
+1. [Inputs](#1-inputs)
+2. [Entity Definition Template](#2-entity-template)
+3. [ER Diagram](#3-er-diagram)
+4. [Data Patterns](#4-data-patterns)
+5. [Index Strategy](#5-indexes)
+6. [Query Pattern Mapping](#6-query-mapping)
+7. [Transactions](#7-transactions)
+8. [Migrations](#8-migrations)
+9. [Example: full model](#9-example)
+10. [Output Template](#10-output)
+
+---
+
+## 1. Inputs
+
+| Input | From | Why |
+|------|--------|-------|
+| PRD | PM gate | Acceptance criteria → entities, constraints |
+| UX Spec | UX gate | Screens/flows → query patterns |
+| API Contracts | Architect | Request/Response → fields, types |
+| NFR | System Design | Volume, latency, retention |
+
+---
+
+## 2. Entity Definition Template
 
-## Exit
-## 1) Entities
 For each entity:
-- fields (type/required)
-- restrictions (unique/not null/range)
-- communications
-- indexes for UX queries
-
-## 2) Data patterns (conscious choice)
-- Default normalization
-- Denormalization for read perf (if really needed)
-- Cache layers (Redis) - if there are hot reads
-- Eventual consistency - if there are distributed parts
-- Event sourcing - only if you need a strict audit/replay
-
-For each selected pattern: Pros/Cons/Alternatives (ADR if necessary).
-
-## 3) Migrations strategy
-- versioning
-- reversibility (if necessary)
-- Seeds/fixtures
-
-## 4) Transaction boundaries
-- where transactions are needed
-- competition and integrity (constraints/locking)
-
-## 5) Query patterns
-- typical requests for screens
-- risks of N+1 / heavy joins
-- optimizations: indexes, prefetch, denormalization (if necessary)
+
+```markdown
+### Entity: Coupon
+
+**Collection:** `coupons`
+**Lifecycle:** Created by site owner, read by embedded script, deleted manually
+
+| Field | Type | Required | Default | Constraints | Description |
+|-------|------|----------|---------|-------------|-------------|
+| _id | ObjectId | auto | auto | unique | Primary key |
+| appInstanceId | string | ✅ | — | indexed | Installation reference |
+| code | string | ✅ | — | 3-20 chars, uppercase, alphanumeric | Coupon code |
+| discount | number | ✅ | — | 1-100 | Discount value |
+| type | string | ✅ | "percent" | enum: percent, fixed | Discount type |
+| active | boolean | ⬜ | true | — | Is coupon active |
+| usageCount | number | ⬜ | 0 | min: 0 | Times used |
+| createdAt | Date | auto | now | — | Timestamp |
+| updatedAt | Date | auto | now | — | Timestamp |
+
+**Unique constraints:** (appInstanceId, code)
+**Indexes:** See Index Strategy
+**Relationships:** belongs to Installation (via appInstanceId)
+**Storage pattern:** Reference (separate collection)
+**Rationale:** Coupons have independent lifecycle, unbounded per installation
+```
+
+---
+
+## 3. ER Diagram
+
+```mermaid
+erDiagram
+    INSTALLATION ||--|| SETTINGS : "has one"
+    INSTALLATION ||--o{ COUPON : "has many"
+
+    INSTALLATION {
+        ObjectId _id PK
+        string appInstanceId UK
+        string instanceId
+        string siteUrl
+        string status
+        Date installedAt
+    }
+
+    SETTINGS {
+        ObjectId _id PK
+        string appInstanceId UK "FK → Installation"
+        object overlay
+        object cta
+        object tab
+        object timer
+        string designStyle
+        string templateId
+        object templateSettings
+    }
+
+    COUPON {
+        ObjectId _id PK
+        string appInstanceId "FK → Installation"
+        string code
+        number discount
+        string type
+        boolean active
+        number usageCount
+        Date createdAt
+    }
+```
+
+---
+
+## 4. Data Patterns
+
+### Embed vs Reference Decision
+
+| Criterion | Embed ✅ | Reference ✅ |
+|---------|---------|-------------|
+| Are read together | Yes | No |
+| Independent lifecycle | No | Yes |
+| Bounded size | Yes (< 50 items) | Unbounded |
+| Atomic updates child | Needed | Not critical |
+
+### Decision table (for project)
+
+| Parent | Child | Pattern | Rationale |
+|--------|-------|---------|-----------|
+| Installation | Settings | **Embed** (or 1:1 ref) | Always are read together, 1 settings per install |
+| Installation | Coupons | **Reference** | Independent CRUD, unbounded, own pagination |
+| Settings | overlay/cta/tab | **Embed** | Bounded subdocuments, always read together |
+
+> Each choice embed/reference = a potential ADR. If it is not obvious — create `$adr_log`.
+
+### Caching (if applicable)
+
+| Data | Cache? | Strategy | TTL | Invalidation |
+|------|--------|----------|-----|-------------|
+| Widget config | ✅ | HTTP Cache-Control | 60s | PUT settings → purge |
+| Coupon list | ⬜ | No cache (small, dashboard only) | — | — |
+| Settings (dashboard) | ⬜ | No cache (always fresh) | — | — |
+
+---
+
+## 5. Index Strategy
+
+### Index → Query Pattern Mapping
+
+| Index | Fields | Type | Serves Query |
+|-------|--------|------|-------------|
+| `installations_appInstanceId` | `{ appInstanceId: 1 }` | unique | Lookup by appInstanceId |
+| `settings_appInstanceId` | `{ appInstanceId: 1 }` | unique | Lookup settings by install |
+| `coupons_app_code` | `{ appInstanceId: 1, code: 1 }` | unique | Duplicate check on create |
+| `coupons_app_active_date` | `{ appInstanceId: 1, active: 1, createdAt: -1 }` | compound | List active coupons sorted by date |
+| `coupons_app_date` | `{ appInstanceId: 1, createdAt: -1 }` | compound | List all coupons sorted |
+
+### Index rules
+
+| Rule | Description |
+|---------|---------|
+| **ESR** | Equality → Sort → Range (order fields in compound) |
+| **Max 5-7** | Each index = write overhead |
+| **Verify** | `explain('executionStats')` → IXSCAN, not COLLSCAN |
+| **Partial** | If index needed not for all docs: `partialFilterExpression` |
+
+---
+
+## 6. Query Pattern Mapping
+
+Mapping UX screen → query:
+
+| UX Screen | Action | Query | Index Used |
+|-----------|--------|-------|------------|
+| Dashboard: Coupons list | Load page | `find({ appInstanceId }).sort({ createdAt: -1 }).limit(20)` | `coupons_app_date` |
+| Dashboard: Coupons list | Filter active | `find({ appInstanceId, active: true }).sort({ createdAt: -1 })` | `coupons_app_active_date` |
+| Dashboard: Coupons list | Search by code | `find({ appInstanceId, code: { $regex } })` | `coupons_app_code` (prefix) |
+| Dashboard: Settings | Load | `findOne({ appInstanceId })` | `settings_appInstanceId` |
+| Dashboard: Settings | Save | `updateOne({ appInstanceId }, { $set: ... })` | `settings_appInstanceId` |
+| Embedded Script | Load config | `findOne({ appInstanceId })` + `findOne({ appInstanceId, active: true }).sort({ createdAt: -1 })` | `settings_appInstanceId` + `coupons_app_active_date` |
+| Webhook: install | Create | `updateOne({ appInstanceId }, { ... }, { upsert: true })` | `installations_appInstanceId` |
+
+### Performance notes
+
+| Query | Expected latency | Volume | Notes |
+|-------|-----------------|--------|-------|
+| Widget config | < 10ms | Every page view | Add cache header |
+| Coupons list | < 20ms | Dashboard only | Paginated |
+| Settings load | < 5ms | Dashboard only | Single doc |
+
+---
+
+## 7. Transactions
+
+### When needed
+
+| Scenario | Transaction? | Rationale |
+|----------|:---:|-----------|
+| Create coupon | ⬜ No | Single collection write |
+| Update settings | ⬜ No | Single document update |
+| Apply coupon (if order system) | ✅ Yes | Multi-doc: update order + increment usage |
+| Install webhook (upsert install + settings) | ⬜ No | Idempotent upserts, eventual consistency OK |
+
+### Rule
+
+> MongoDB any modeling, where transactions needed **rarely**. If transaction needed often — revisit schema (can is worth embed).
+
+---
+
+## 8. Migrations
+
+### Strategy
+
+| When | How |
+|-------|-----|
+| New field (optional) | Add in schema + `$setOnInsert` default |
+| New field (required) | Migration script: `updateMany` + backfill |
+| Rename field | Migration script + update code + period with both fields |
+| Remove field | Migration script: `$unset` + remove from schema |
+| Change type | Two steps: add new field → migrate data → remove old |
+
+### Tool
+
+```bash
+npx migrate-mongo create add-templateId-to-settings
+npx migrate-mongo up
+npx migrate-mongo down   # rollback
+npx migrate-mongo status
+```
+
+---
+
+## 9. Example: full model
+
+```markdown
+# Data Model: Smart Cart Rescue
+
+## Entities
+1. Installation — Wix app installation record
+2. Settings — Widget configuration (1:1 with Installation)
+3. Coupon — Discount coupons (1:N with Installation)
+
+## Storage
+- MongoDB 7 (single instance, Docker)
+- Mongoose ODM (strict: 'throw')
+- Timestamps on all collections
+
+## Key decisions
+- Settings embedded approach considered, but separate collection for independent API
+- Coupons always referenced (unbounded, independent CRUD)
+- See ADR-001 (MongoDB), ADR-003 (embed vs reference)
+```
+
+---
+
+## 10. Output Template
+
+```markdown
+# Data Model: <project-name>
+
+**Date:** YYYY-MM-DD
+**Database:** MongoDB 7 + Mongoose
+
+## ER Diagram
+<mermaid diagram>
+
+## Entities
+<for each entity: section 2 template>
+
+## Data Patterns
+<embed vs ref decisions with rationale>
+
+## Indexes
+<section 5 table>
+
+## Query Mapping
+<section 6 table>
+
+## Transactions
+<section 7 table>
+
+## Migration Strategy
+<section 8>
+```
+
+---
+
+## See also
+- `$api_contracts` — API endpoints (schemas match entity fields)
+- `$mongodb_mongoose_best_practices` — implementation patterns
+- `$architecture_doc` — Architecture Document (data model section)
+- `$adr_log` — ADR for embed/reference/DB decisions

package/locales/en/.agents/data_model/agents/claude.json

@@ -1,12 +1,12 @@
 {
   "name": "data_model",
   "display_name": "Data Model",
-  "description": "Data model and storage strategy: normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency - with trade-offs and binding to UX flows.",
+  "description": "Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency — with trade-offs and tied to UX flows.",
   "default_prompt": "Use $data_model when the task matches the \"Data Model\" skill.",
   "triggers": [
     "data_model",
     "data model",
-    "Data model and storage strategy"
+    "Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency — with trade-offs and tied to UX flows"
   ],
   "capabilities": [
     "data",

package/locales/en/.agents/data_model/agents/copilot.json

@@ -1,12 +1,12 @@
 {
   "name": "data_model",
   "display_name": "Data Model",
-  "description": "Data model and storage strategy: normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency - with trade-offs and binding to UX flows.",
+  "description": "Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency — with trade-offs and tied to UX flows.",
   "default_prompt": "Use $data_model when the task matches the \"Data Model\" skill.",
   "triggers": [
     "data_model",
     "data model",
-    "Data model and storage strategy"
+    "Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency — with trade-offs and tied to UX flows"
   ],
   "capabilities": [
     "data",

package/locales/en/.agents/data_model/agents/gemini.json

@@ -1,12 +1,12 @@
 {
   "name": "data_model",
   "display_name": "Data Model",
-  "description": "Data model and storage strategy: normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency - with trade-offs and binding to UX flows.",
+  "description": "Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency — with trade-offs and tied to UX flows.",
   "default_prompt": "Use $data_model when the task matches the \"Data Model\" skill.",
   "triggers": [
     "data_model",
     "data model",
-    "Data model and storage strategy"
+    "Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency — with trade-offs and tied to UX flows"
   ],
   "capabilities": [
     "data",

package/locales/en/.agents/data_model/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Data Model"
-  short_description: "Data model and storage strategy: normalization/denormalization, indexes, transactions, cache, (…"
+  short_description: "Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (o…"
   default_prompt: "Use $data_model when the task matches the \"Data Model\" skill."
 dependencies:
   tools: []

package/locales/en/.agents/data_model/agents/qwen.json

@@ -1,12 +1,12 @@
 {
   "name": "data_model",
   "display_name": "Data Model",
-  "description": "Data model and storage strategy: normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency - with trade-offs and binding to UX flows.",
+  "description": "Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency — with trade-offs and tied to UX flows.",
   "default_prompt": "Use $data_model when the task matches the \"Data Model\" skill.",
   "triggers": [
     "data_model",
     "data model",
-    "Data model and storage strategy"
+    "Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency — with trade-offs and tied to UX flows"
   ],
   "capabilities": [
     "data",

package/locales/en/.agents/data_model/agents/skill.yaml

@@ -1,12 +1,12 @@
 version: 1
 name: "data_model"
 display_name: "Data Model"
-description: "Data model and storage strategy: normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency - with trade-offs and binding to UX flows."
+description: "Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency — with trade-offs and tied to UX flows."
 default_prompt: "Use $data_model when the task matches the \"Data Model\" skill."
 triggers:
   - "data_model"
   - "data model"
-  - "Data model and storage strategy"
+  - "Model data and strategy store — normalization/denormalization, indexes, transactions, cache, (optional) event sourcing/eventual consistency — with trade-offs and tied to UX flows"
 capabilities:
   - "data"
   - "model"