code-ai-installer 1.2.0 → 1.3.1

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

@@ -1,12 +1,13 @@
 {
   "name": "a11y_baseline",
   "display_name": "Minimum baseline accessibility for web UI",
-  "description": "Minimum baseline accessibility for web UI: keyboard navigation, focus management, form labels, ARIA for interactive components, error messages.",
+  "description": "Minimum baseline accessibility for web UI — keyboard navigation, focus management, form labels, ARIA for interactive components, error messages.",
   "default_prompt": "Use $a11y_baseline when the task matches the \"Minimum baseline accessibility for web UI\" skill.",
   "triggers": [
     "a11y_baseline",
     "a11y baseline",
-    "Minimum baseline accessibility for web UI"
+    "Minimum baseline accessibility for web UI",
+    "Minimum baseline accessibility for web UI — keyboard navigation, focus management, form labels, ARIA for interactive components, error messages"
   ],
   "capabilities": [
     "a11y",

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

@@ -1,12 +1,13 @@
 {
   "name": "a11y_baseline",
   "display_name": "Minimum baseline accessibility for web UI",
-  "description": "Minimum baseline accessibility for web UI: keyboard navigation, focus management, form labels, ARIA for interactive components, error messages.",
+  "description": "Minimum baseline accessibility for web UI — keyboard navigation, focus management, form labels, ARIA for interactive components, error messages.",
   "default_prompt": "Use $a11y_baseline when the task matches the \"Minimum baseline accessibility for web UI\" skill.",
   "triggers": [
     "a11y_baseline",
     "a11y baseline",
-    "Minimum baseline accessibility for web UI"
+    "Minimum baseline accessibility for web UI",
+    "Minimum baseline accessibility for web UI — keyboard navigation, focus management, form labels, ARIA for interactive components, error messages"
   ],
   "capabilities": [
     "a11y",

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

@@ -1,12 +1,13 @@
 {
   "name": "a11y_baseline",
   "display_name": "Minimum baseline accessibility for web UI",
-  "description": "Minimum baseline accessibility for web UI: keyboard navigation, focus management, form labels, ARIA for interactive components, error messages.",
+  "description": "Minimum baseline accessibility for web UI — keyboard navigation, focus management, form labels, ARIA for interactive components, error messages.",
   "default_prompt": "Use $a11y_baseline when the task matches the \"Minimum baseline accessibility for web UI\" skill.",
   "triggers": [
     "a11y_baseline",
     "a11y baseline",
-    "Minimum baseline accessibility for web UI"
+    "Minimum baseline accessibility for web UI",
+    "Minimum baseline accessibility for web UI — keyboard navigation, focus management, form labels, ARIA for interactive components, error messages"
   ],
   "capabilities": [
     "a11y",

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

@@ -1,6 +1,6 @@
 interface:
   display_name: "Minimum baseline accessibility for web UI"
-  short_description: "Minimum baseline accessibility for web UI: keyboard navigation, focus management, form labels,…"
+  short_description: "Minimum baseline accessibility for web UI — keyboard navigation, focus management, form labels,…"
   default_prompt: "Use $a11y_baseline when the task matches the \"Minimum baseline accessibility for web UI\" skill."
 dependencies:
   tools: []

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

@@ -1,12 +1,13 @@
 {
   "name": "a11y_baseline",
   "display_name": "Minimum baseline accessibility for web UI",
-  "description": "Minimum baseline accessibility for web UI: keyboard navigation, focus management, form labels, ARIA for interactive components, error messages.",
+  "description": "Minimum baseline accessibility for web UI — keyboard navigation, focus management, form labels, ARIA for interactive components, error messages.",
   "default_prompt": "Use $a11y_baseline when the task matches the \"Minimum baseline accessibility for web UI\" skill.",
   "triggers": [
     "a11y_baseline",
     "a11y baseline",
-    "Minimum baseline accessibility for web UI"
+    "Minimum baseline accessibility for web UI",
+    "Minimum baseline accessibility for web UI — keyboard navigation, focus management, form labels, ARIA for interactive components, error messages"
   ],
   "capabilities": [
     "a11y",

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

@@ -1,12 +1,13 @@
 version: 1
 name: "a11y_baseline"
 display_name: "Minimum baseline accessibility for web UI"
-description: "Minimum baseline accessibility for web UI: keyboard navigation, focus management, form labels, ARIA for interactive components, error messages."
+description: "Minimum baseline accessibility for web UI — keyboard navigation, focus management, form labels, ARIA for interactive components, error messages."
 default_prompt: "Use $a11y_baseline when the task matches the \"Minimum baseline accessibility for web UI\" skill."
 triggers:
   - "a11y_baseline"
   - "a11y baseline"
   - "Minimum baseline accessibility for web UI"
+  - "Minimum baseline accessibility for web UI — keyboard navigation, focus management, form labels, ARIA for interactive components, error messages"
 capabilities:
   - "a11y"
   - "baseline"

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

@@ -1,69 +1,369 @@
 ---
 name:adr_log
-description: Record key architectural decisions (ADR) with trade-offs: Pros/Cons/Alternatives/Decision, status and date.
+description: Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, status and date.
 ---
 
 #Skill: ADR Log
 
-## Goal
-Don’t lose track of “why we did this” and simplify review/support.
+Format and examples for Architectural Decision Records.
 
-## When to use
-- For every non-trivial choice: database, auth, cache, module structure, API format, error strategy, queues, search, deployment, integrations, etc.
+**Sections:**
+1. [When create ADR](#1-when)
+2. [Format (mandatory)](#2-format)
+3. [Naming Convention](#3-naming)
+4. [Examples ADR](#4-examples)
+5. [Decision Matrix](#5-decision-matrix)
+6. [Lifecycle](#6-lifecycle)
+7. [Anti-patterns](#7-anti-patterns)
 
-## ADR format (required)
-# ADR-XXX: <Name>
+---
+
+## 1. When create ADR
+
+Create ADR for **each non-trivial choice** — if in 6 months someone asks "why like this?":
+
+| Category | Examples |
+|-----------|---------|
+| **Database** | DBMS choice, embed vs reference, sharding strategy |
+| **Auth** | JWT vs sessions, cookie vs header, OAuth flow |
+| **API Design** | REST vs GraphQL, versioning, error format |
+| **Architecture** | Monolith vs microservices, layering, module boundaries |
+| **Infrastructure** | Docker vs K8s, CDN, reverse proxy, HTTPS strategy |
+| **Integration** | Wix SDK choice, payment provider, email service |
+| **State** | Zustand vs Redux vs Context, server state (React Query) |
+| **Styling** | CSS Modules vs Tailwind vs styled-components |
+| **Testing** | Test runner, coverage thresholds, mock strategy |
+| **Error handling** | Error format, retry policy, circuit breaker |
+
+---
+
+## 2. Format (mandatory)
+
+```markdown
+# ADR-XXX: <Short decision title>
+
+## Status
+Proposed | Accepted | Deprecated | Superseded by ADR-YYY
+
+## Date
+YYYY-MM-DD
 
 ## Context
-<why is this necessary, what are the limitations, what hurts>
+<Why is this needed? What constraints? What hurts?>
+- Current situation
+- Requirements / constraints
+- What happens if it is not solved
 
 ##Decision
-<what you chose and how exactly>
+<What we chose and how exactly we will do it>
 
 ## Consequences
+
 ### Positive
 - ...
+- ...
+
 ###Negative
 - ...
+- ...
+
+### Risks
+- ... (and how we mitigate)
 
 ## Alternatives Considered
-- **A**: ...
-- **B**: ...
 
-##Status
-Proposed / Accepted / Deprecated
+### Option A: <title>
+- ✅ Pros: ...
+- ❌ Cons: ...
+- 💡 Why rejected: ...
 
-##Date
-YYYY-MM-DD
+### Option B: <title>
+- ✅ Pros: ...
+- ❌ Cons: ...
+- 💡 Why rejected: ...
+
+## References
+- PRD section / UX Spec / ticket
+- External docs / articles
+- Related ADRs: ADR-XXX
+```
+
+---
+
+## 3. Naming Convention
+
+| Rule | Example |
+|---------|--------|
+| Number: 3-digit, with leading zeros | ADR-001, ADR-042 |
+| Title: action + object | "Use MongoDB as primary database" |
+| File: `ADR-XXX-kebab-case.md` | `ADR-001-use-mongodb.md` |
+| Directory: `docs/architecture/adr/` | — |
+| Chronological order | New ADR = next number |
+
+---
+
+## 4. Examples ADR
 
-## Requirements (strict)
-- For each ADR there must be explicit Pros/Cons/Alternatives and rationale of choice.
-- If the decision affects security/data/cost, be sure to describe the consequences.
-- ADR should be short and specific: without water, but with key arguments.
+### ADR-001: Use MongoDB as primary database
 
-## Example (short)
-# ADR-001: Selecting the main database
+```markdown
+# ADR-001: Use MongoDB as primary database
+
+## Status
+Accepted
+
+##Date
+2025-06-15
 
 ##Context
-You need to store users/sessions/orders. Transactions and complex queries are needed. Expected growth to 100K users.
+Smart Cart Rescue needs persistent storage for installations, settings,
+and coupons. Requirements:
+- Flexible schema (settings structure varies per template)
+- Low operational overhead (small team)
+- Good Node.js ecosystem support
+- No complex joins needed (data is per-installation)
 
 ##Decision
-We use PostgreSQL as the main database.
+Use MongoDB 7 with Mongoose ODM.
+- Single database, collections: installations, settings, coupons
+- Hosted via Docker (dev) / MongoDB Atlas (production)
 
 ## Consequences
+
 ### Positive
-- ACID transactions
-- Rich queries and indexing
+- Flexible schema fits varying template settings
+- Excellent Mongoose ecosystem (validators, middleware, lean queries)
+- Easy Docker setup for local development
+- Native JSON — minimal serialization overhead
+
 ###Negative
-- Possible need for scaling during growth
-- Operational costs for administration
+- No ACID transactions across collections (need replica set)
+- No joins — must denormalize or do application-level joins
+- Schema discipline required (strict mode + Zod validation)
+
+### Risks
+- Schema drift without validation → mitigated by strict: 'throw'
+- 16MB document limit → mitigated by reference strategy for unbounded arrays
 
 ## Alternatives Considered
-- **MongoDB**: weaker in transactional/complex join scenarios
-- **DynamoDB**: vendor lock-in, more difficult to test locally
+
+### Option A: PostgreSQL
+- ✅ ACID, complex queries, strong typing
+- ❌ Schema migrations more complex for flexible settings
+- ❌ JSON column less ergonomic than native MongoDB documents
+- 💡 Overkill for current use case (no joins, no complex queries)
+
+### Option B: SQLite
+- ✅ Zero infrastructure, file-based
+- ❌ No concurrent writes in Docker
+- ❌ No production scaling path
+- 💡 Too limiting for multi-service architecture
+
+## References
+- PRD: Data requirements section
+- Related: ADR-002 (Mongoose strict mode)
+```
+
+---
+
+### ADR-018: Use Wix ImageViewer for dashboard images
+
+```markdown
+# ADR-018: Use Wix ImageViewer for dashboard images
 
 ##Status
 Accepted
 
 ##Date
-2025-01-15
+2025-12-20
+
+## Context
+Dashboard needs to display template preview images.
+The app runs inside Wix iframe where standard <img> tags may have
+CORS issues with Wix media URLs (wixstatic.com).
+
+## Decision
+Use WDS (Wix Design System) ImageViewer component for all
+dashboard images instead of native <img> tags.
+
+## Consequences
+
+### Positive
+- Handles Wix media URLs natively (no CORS issues)
+- Consistent with Wix design system (visual parity)
+- Built-in loading states and error handling
+
+### Negative
+- Dependency on WDS component library
+- Different API than standard <img> (onLoad, src format)
+
+## Alternatives Considered
+
+### Option A: Native <img> with proxy
+- ✅ Simple, no dependency
+- ❌ CORS errors with wixstatic.com
+- ❌ Need custom proxy endpoint
+- 💡 Unnecessary complexity
+
+## References
+- Bug: Dashboard images not loading (blank src)
+- Wix Design System docs: ImageViewer component
+```
+
+---
+
+### ADR-019: CSS overflow containment for popup templates
+
+```markdown
+# ADR-019: CSS overflow containment for popup
+
+## Status
+Accepted
+
+## Date
+2025-12-20
+
+## Context
+Popup templates render inside Wix embedded script.
+CSS overflow from popup elements leaks outside the container,
+causing scrollbars on the Wix page.
+
+## Decision
+Apply containment strategy:
+1. `overflow: hidden` on popup container
+2. `contain: layout style` on root widget element
+3. `box-sizing: border-box` on all popup children
+
+## Consequences
+
+### Positive
+- No visual leaking outside container
+- No unexpected scrollbars on host page
+- Each template isolated
+
+### Negative
+- Must test each template for clipping issues
+- Shadow effects near edges may be cut off
+
+## Alternatives Considered
+
+### Option A: Shadow DOM
+- ✅ Complete style isolation
+- ❌ Complex to implement for dynamic templates
+- ❌ Limited shadow DOM support for legacy browsers
+- 💡 Overkill for current 3-template scope
+
+## References
+- Bug: Scrollbar appearing on Wix site when popup opens
+- Related: ADR-018 (ImageViewer)
+```
+
+---
+
+## 5. Decision Matrix
+
+For complex decisions with 3+ alternative use weighted matrix:
+
+```markdown
+## Decision Matrix: State Management
+
+### Criteria (weighted)
+| Criteria | Weight | Description |
+|----------|--------|-------------|
+| Simplicity | 3 | Learning curve, boilerplate |
+| Performance | 2 | Re-render efficiency |
+| DevTools | 1 | Debugging experience |
+| Ecosystem | 1 | Community, plugins |
+| Bundle size | 2 | KB added |
+
+### Scoring (1-5, higher = better)
+
+| Option | Simplicity (×3) | Performance (×2) | DevTools (×1) | Ecosystem (×1) | Bundle (×2) | **Total** |
+|--------|:---:|:---:|:---:|:---:|:---:|:---:|
+| **Zustand** | 5 (15) | 4 (8) | 4 (4) | 3 (3) | 5 (10) | **40** |
+| Redux Toolkit | 3 (9) | 4 (8) | 5 (5) | 5 (5) | 3 (6) | **33** |
+| Context + useReducer | 4 (12) | 2 (4) | 3 (3) | 5 (5) | 5 (10) | **34** |
+| Jotai | 4 (12) | 5 (10) | 3 (3) | 2 (2) | 5 (10) | **37** |
+
+### Decision
+Zustand wins (40 points). Best simplicity + performance + bundle size.
+```
+
+---
+
+## 6. Lifecycle
+
+```
+Proposed → Accepted → [Active use]
+                         ↓
+                    Deprecated (if better solution found)
+                         ↓
+                    Superseded by ADR-YYY
+```
+
+| Status | Meaning |
+|--------|---------|
+| **Proposed** | Decision is proposed, waiting for review |
+| **Accepted** | Decision is accepted and applied |
+| **Deprecated** | Decision is deprecated, but the code still uses it |
+| **Superseded** | Superseded by another ADR (specify link) |
+
+### Supersedes/Superseded-by
+
+```markdown
+# ADR-025: Migrate from CSS Modules to Tailwind
+
+## Status
+Accepted (Supersedes ADR-008)
+
+---
+
+# ADR-008: Use CSS Modules for component styling
+
+## Status
+Superseded by ADR-025
+```
+
+---
+
+## 7. Anti-patterns
+
+| ❌ Anti-pattern | ✅ Decision |
+|----------------|-----------|
+| ADR without Alternatives | Always at least 2 alternatives |
+| "We chose X because it's popular" | Concrete pros/cons by project criteria |
+| 500-line ADR | Short and concrete: max 50-80 lines |
+| ADR retroactively (a month later) | Create ADR in the moment the decision is made |
+| No cross-references | Links to the PRD, related ADRs, tickets |
+| No Negative consequences | Every decision has trade-offs |
+| "Alternatives: none" | If there are no alternatives — revisit the scope question |
+
+---
+
+## Deliverables
+
+| Artifact | Format | Where |
+|---------|--------|-----|
+| ADR record | Markdown (format above) | `docs/architecture/adr/ADR-XXX-name.md` |
+| ADR index | Table of contents | `docs/architecture/adr/README.md` |
+
+### ADR Index format
+
+```markdown
+# Architecture Decision Records
+
+| # | Title | Status | Date |
+|---|-------|--------|------|
+| ADR-001 | Use MongoDB as primary database | Accepted | 2025-06-15 |
+| ADR-008 | Use CSS Modules for styling | Superseded by ADR-025 | 2025-07-01 |
+| ADR-018 | Use WDS ImageViewer | Accepted | 2025-12-20 |
+| ADR-019 | CSS overflow containment | Accepted | 2025-12-20 |
+| ADR-025 | Migrate to Tailwind | Accepted | 2026-01-15 |
+```
+
+---
+
+## See also
+- `$architecture_doc` — Architecture Document (ADR decisions referenced inline)
+- `$current_state_analysis` — audit before new ADRs
+- `$system_design_checklist` — checklist design completeness

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

@@ -1,13 +1,13 @@
 {
   "name": "adr_log",
-  "display_name": "ADR-XXX: <Name>",
-  "description": "Record key architectural decisions (ADR) with trade-offs: Pros/Cons/Alternatives/Decision, status and date.",
-  "default_prompt": "Use $adr_log when the task matches the \"ADR-XXX: <Name>\" skill.",
+  "display_name": "ADR-XXX: <Short decision title>",
+  "description": "Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, status and date.",
+  "default_prompt": "Use $adr_log when the task matches the \"ADR-XXX: <Short decision title>\" skill.",
   "triggers": [
     "adr_log",
     "adr log",
-    "ADR-XXX: <Name>",
-    "Record key architectural decisions (ADR) with trade-offs"
+    "ADR-XXX: <Short decision title>",
+    "Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, status and date"
   ],
   "capabilities": [
     "adr",

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

@@ -1,13 +1,13 @@
 {
   "name": "adr_log",
-  "display_name": "ADR-XXX: <Name>",
-  "description": "Record key architectural decisions (ADR) with trade-offs: Pros/Cons/Alternatives/Decision, status and date.",
-  "default_prompt": "Use $adr_log when the task matches the \"ADR-XXX: <Name>\" skill.",
+  "display_name": "ADR-XXX: <Short decision title>",
+  "description": "Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, status and date.",
+  "default_prompt": "Use $adr_log when the task matches the \"ADR-XXX: <Short decision title>\" skill.",
   "triggers": [
     "adr_log",
     "adr log",
-    "ADR-XXX: <Name>",
-    "Record key architectural decisions (ADR) with trade-offs"
+    "ADR-XXX: <Short decision title>",
+    "Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, status and date"
   ],
   "capabilities": [
     "adr",

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

@@ -1,13 +1,13 @@
 {
   "name": "adr_log",
-  "display_name": "ADR-XXX: <Name>",
-  "description": "Record key architectural decisions (ADR) with trade-offs: Pros/Cons/Alternatives/Decision, status and date.",
-  "default_prompt": "Use $adr_log when the task matches the \"ADR-XXX: <Name>\" skill.",
+  "display_name": "ADR-XXX: <Short decision title>",
+  "description": "Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, status and date.",
+  "default_prompt": "Use $adr_log when the task matches the \"ADR-XXX: <Short decision title>\" skill.",
   "triggers": [
     "adr_log",
     "adr log",
-    "ADR-XXX: <Name>",
-    "Record key architectural decisions (ADR) with trade-offs"
+    "ADR-XXX: <Short decision title>",
+    "Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, status and date"
   ],
   "capabilities": [
     "adr",

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

@@ -1,7 +1,7 @@
 interface:
-  display_name: "ADR-XXX: <Name>"
-  short_description: "Record key architectural decisions (ADR) with trade-offs: Pros/Cons/Alternatives/Decision, stat…"
-  default_prompt: "Use $adr_log when the task matches the \"ADR-XXX: <Name>\" skill."
+  display_name: "ADR-XXX: <Short decision title>"
+  short_description: "Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, sta…"
+  default_prompt: "Use $adr_log when the task matches the \"ADR-XXX: <Short decision title>\" skill."
 dependencies:
   tools: []
 policy:

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

@@ -1,13 +1,13 @@
 {
   "name": "adr_log",
-  "display_name": "ADR-XXX: <Name>",
-  "description": "Record key architectural decisions (ADR) with trade-offs: Pros/Cons/Alternatives/Decision, status and date.",
-  "default_prompt": "Use $adr_log when the task matches the \"ADR-XXX: <Name>\" skill.",
+  "display_name": "ADR-XXX: <Short decision title>",
+  "description": "Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, status and date.",
+  "default_prompt": "Use $adr_log when the task matches the \"ADR-XXX: <Short decision title>\" skill.",
   "triggers": [
     "adr_log",
     "adr log",
-    "ADR-XXX: <Name>",
-    "Record key architectural decisions (ADR) with trade-offs"
+    "ADR-XXX: <Short decision title>",
+    "Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, status and date"
   ],
   "capabilities": [
     "adr",

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

@@ -1,13 +1,13 @@
 version: 1
 name: "adr_log"
-display_name: "ADR-XXX: <Name>"
-description: "Record key architectural decisions (ADR) with trade-offs: Pros/Cons/Alternatives/Decision, status and date."
-default_prompt: "Use $adr_log when the task matches the \"ADR-XXX: <Name>\" skill."
+display_name: "ADR-XXX: <Short decision title>"
+description: "Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, status and date."
+default_prompt: "Use $adr_log when the task matches the \"ADR-XXX: <Short decision title>\" skill."
 triggers:
   - "adr_log"
   - "adr log"
-  - "ADR-XXX: <Name>"
-  - "Record key architectural decisions (ADR) with trade-offs"
+  - "ADR-XXX: <Short decision title>"
+  - "Record key architectural decisions (ADR) with trade-offs — Pros/Cons/Alternatives/Decision, status and date"
 capabilities:
   - "adr"
   - "log"