code-ai-installer 3.0.0 → 4.0.1-a

package/domains/development/locales/en/.agents/skills/wix-self-hosted-embedded-script-reference/agents/skill.yaml

@@ -0,0 +1,25 @@
+version: 1
+name: "wix-self-hosted-embedded-script-reference"
+display_name: "Wix Self-Hosted Embedded Script Reference (Templates)"
+description: "Canonical reference of templates for Wix Self-Hosted Embedded Script — webhookRouter handler, EmbedService class, widget endpoint handlers, embedded script IIFE bootstrap, Caddyfile + trust cert (macOS/Win/Linux), Docker Compose fragment. Growing library of reference templates for ARCH+DEV gates."
+default_prompt: "Use $wix-self-hosted-embedded-script-reference when the task matches the \"Wix Self-Hosted Embedded Script Reference (Templates)\" skill."
+triggers:
+  - "wix-self-hosted-embedded-script-reference"
+  - "wix self hosted embedded script reference"
+  - "Wix Self-Hosted Embedded Script Reference (Templates)"
+  - "Practical runbook for Wix Self-Hosted Embedded Script Reference (Templates) — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors, and DEMO-ready checklist"
+capabilities:
+  - "wix"
+  - "self"
+  - "hosted"
+  - "embedded"
+  - "script"
+tools: []
+invocation:
+  explicit: true
+  implicit: true
+localization:
+  default_locale: "en"
+  available_locales:
+    - "ru"
+    - "en"

package/domains/development/locales/en/.agents/workflows/auto-restart-containers.md

@@ -1,24 +1,24 @@
----
-description: Auto-restart affected Docker containers after code changes
----
-
-# Auto-Restart Affected Containers
-
-After any code change inside one of the application source directories, the corresponding Docker container must be restarted automatically.
-
-## Source → Container Mapping
-
-| Source directory | Docker service name | Container name |
-|-----------------|---------------------|----------------|
-| `apps/api/` | `api` | `smart-cart-api` |
-| `apps/dashboard/` | `dashboard` | `smart-cart-dashboard` |
-| `apps/widget/` | `widget` | `smart-cart-widget` |
-
-Infrastructure files (`infra/`, `docker-compose.yml`) and config/env-only changes do not trigger auto-restart.
-
-## Steps
-1. Determine which `apps/` directory changed.
-2. Map it to the Docker service.
-3. Run `docker compose restart <service_name>` from the project root.
-4. If multiple services changed, restart them together.
+---
+description: Auto-restart affected Docker containers after code changes
+---
+
+# Auto-Restart Affected Containers
+
+After any code change inside one of the application source directories, the corresponding Docker container must be restarted automatically.
+
+## Source → Container Mapping
+
+| Source directory | Docker service name | Container name |
+|-----------------|---------------------|----------------|
+| `apps/api/` | `api` | `smart-cart-api` |
+| `apps/dashboard/` | `dashboard` | `smart-cart-dashboard` |
+| `apps/widget/` | `widget` | `smart-cart-widget` |
+
+Infrastructure files (`infra/`, `docker-compose.yml`) and config/env-only changes do not trigger auto-restart.
+
+## Steps
+1. Determine which `apps/` directory changed.
+2. Map it to the Docker service.
+3. Run `docker compose restart <service_name>` from the project root.
+4. If multiple services changed, restart them together.
 5. Wait for restart completion before reporting results.

package/domains/development/locales/en/.agents/workflows/bugfix.md

@@ -1,90 +1,90 @@
----
-description: Launch the shortened 4-gate pipeline for bug fixes. Use instead of /start-task for bugfix tasks.
----
-
-# /bugfix — Launch Bugfix Pipeline (4 gates)
-
-> 🟢 **Mode:** Bugfix — for fixing bugs in existing functionality.
-> Full pipeline: `/start-task`. Hotfix (trivial): `/hotfix`.
-
-## When to use
-
-- Bug in logic, API errors, broken validation, data issues
-- Affects > 2 files or non-trivial blast radius
-- Does NOT change UI layout, does NOT add new API, does NOT change data schema (otherwise → `/start-task`)
-
-## Step 0: Load rules
-
-Execute `/pipeline-rules` — read the rules BEFORE starting work.
-
-## Step 1: CONDUCTOR — Classification
-
-1. Execute `view_file` on `agents/conductor.md`
-2. Confirm the task = bugfix (per Decision Tree)
-3. Create Mini Checklist:
-```
-[ ] BF-DEV-01   Fix + TDD + Handoff Envelope
-[ ] BF-REV-01   Code review + regression check + Handoff Envelope
-[ ] BF-TEST-01  Verification + regression smoke + GO/NO-GO
-```
-4. `notify_user` → wait for **Approved**
-
-## Step 2: DEV — TDD Fix
-
-1. Execute `view_file` on `agents/senior_full_stack.md`
-2. Follow the protocol (skipping §1 UX review and §6 DEMO):
-   - §0: Context + read skills
-   - §2: Analyze bug + root cause
-   - §3: RED — write a failing test reproducing the bug
-   - §4: GREEN — minimal code to make the test pass
-   - §5: REFACTOR — improve without changing behavior
-   - §7: JSDoc on modified functions
-3. Restart affected services if applicable
-4. Form Handoff Envelope → REV
-5. `notify_user` → wait for **Approved**
-
-## Step 3: REV — Code Review
-
-1. Execute `view_file` on `agents/reviewer.md`
-2. Review focus:
-   - Does the test actually reproduce the bug (RED phase)?
-   - Does the fix create side effects?
-   - Is regression risk assessed?
-   - Is JSDoc in place?
-3. Form Handoff Envelope → TEST
-4. `notify_user` → wait for **Approved**
-
-## Step 4: TEST — Verification
-
-1. Execute `view_file` on `agents/tester.md`
-2. Verify:
-   - Bug is fixed (per reproduction steps)
-   - No regression (smoke on affected modules)
-   - Tests pass (CI green)
-3. Issue verdict: **GO ✅ / NO-GO ❌**
-4. `notify_user` → wait for **Approved**
-
----
-
-## On FAIL at REV or TEST
-
-1. Agent produces FAIL Report + Handoff → DEV
-2. DEV fixes → Handoff → REV → TEST (cycle repeats)
-3. Approved is required at every gate
-
----
-
-## Prompt template
-
-```
-@AGENTS.md /bugfix
-
-Bug: [bug description, 1-2 sentences].
-Reproduction: [steps, if known].
-Files: [affected files, if known].
-
-Rules:
-1. Bugfix Pipeline: CONDUCTOR → DEV → REV → TEST
-2. TDD is mandatory (RED → GREEN → REFACTOR)
-3. Approved at every gate
-```
+---
+description: Launch the shortened 4-gate pipeline for bug fixes. Use instead of /start-task for bugfix tasks.
+---
+
+# /bugfix — Launch Bugfix Pipeline (4 gates)
+
+> 🟢 **Mode:** Bugfix — for fixing bugs in existing functionality.
+> Full pipeline: `/start-task`. Hotfix (trivial): `/hotfix`.
+
+## When to use
+
+- Bug in logic, API errors, broken validation, data issues
+- Affects > 2 files or non-trivial blast radius
+- Does NOT change UI layout, does NOT add new API, does NOT change data schema (otherwise → `/start-task`)
+
+## Step 0: Load rules
+
+Execute `/pipeline-rules` — read the rules BEFORE starting work.
+
+## Step 1: CONDUCTOR — Classification
+
+1. Execute `view_file` on `agents/conductor.md`
+2. Confirm the task = bugfix (per Decision Tree)
+3. Create Mini Checklist:
+```
+[ ] BF-DEV-01   Fix + TDD + Handoff Envelope
+[ ] BF-REV-01   Code review + regression check + Handoff Envelope
+[ ] BF-TEST-01  Verification + regression smoke + GO/NO-GO
+```
+4. `notify_user` → wait for **Approved**
+
+## Step 2: DEV — TDD Fix
+
+1. Execute `view_file` on `agents/senior_full_stack.md`
+2. Follow the protocol (skipping §1 UX review and §6 DEMO):
+   - §0: Context + read skills
+   - §2: Analyze bug + root cause
+   - §3: RED — write a failing test reproducing the bug
+   - §4: GREEN — minimal code to make the test pass
+   - §5: REFACTOR — improve without changing behavior
+   - §7: JSDoc on modified functions
+3. Restart affected services if applicable
+4. Form Handoff Envelope → REV
+5. `notify_user` → wait for **Approved**
+
+## Step 3: REV — Code Review
+
+1. Execute `view_file` on `agents/reviewer.md`
+2. Review focus:
+   - Does the test actually reproduce the bug (RED phase)?
+   - Does the fix create side effects?
+   - Is regression risk assessed?
+   - Is JSDoc in place?
+3. Form Handoff Envelope → TEST
+4. `notify_user` → wait for **Approved**
+
+## Step 4: TEST — Verification
+
+1. Execute `view_file` on `agents/tester.md`
+2. Verify:
+   - Bug is fixed (per reproduction steps)
+   - No regression (smoke on affected modules)
+   - Tests pass (CI green)
+3. Issue verdict: **GO ✅ / NO-GO ❌**
+4. `notify_user` → wait for **Approved**
+
+---
+
+## On FAIL at REV or TEST
+
+1. Agent produces FAIL Report + Handoff → DEV
+2. DEV fixes → Handoff → REV → TEST (cycle repeats)
+3. Approved is required at every gate
+
+---
+
+## Prompt template
+
+```
+@AGENTS.md /bugfix
+
+Bug: [bug description, 1-2 sentences].
+Reproduction: [steps, if known].
+Files: [affected files, if known].
+
+Rules:
+1. Bugfix Pipeline: CONDUCTOR → DEV → REV → TEST
+2. TDD is mandatory (RED → GREEN → REFACTOR)
+3. Approved at every gate
+```

package/domains/development/locales/en/.agents/workflows/hotfix.md

@@ -1,74 +1,74 @@
----
-description: Launch the minimal 2-gate pipeline for trivial fixes (hotfix). Use for trivial fixes with blast radius ≈ 0.
----
-
-# /hotfix — Launch Hotfix Pipeline (2 gates)
-
-> 🟡 **Mode:** Hotfix — for trivial fixes with minimal risk.
-> Full pipeline: `/start-task`. Bugfix (more serious): `/bugfix`.
-
-## When to use
-
-- Typos in text/code
-- CSS fixes (color, padding, font size)
-- Single-line logic fix
-- Copy-paste error
-- Blast radius ≈ 0 (affects 1–2 files, does not change contracts)
-
-## Do NOT use if
-
-- Affects > 2 files → `/bugfix`
-- Changes API contract → `/bugfix` or `/start-task`
-- Changes UI layout / adds screens → `/start-task`
-- Unsure → ask the user
-
-## Step 0: Load rules
-
-Execute `/pipeline-rules` — read the rules BEFORE starting work.
-
-## Step 1: CONDUCTOR — Classification
-
-1. Execute `view_file` on `agents/conductor.md`
-2. Confirm the task = hotfix (per Decision Tree: blast radius ≈ 0, 1–2 files)
-3. Create Mini Checklist:
-```
-[ ] HF-DEV-01   Fix + test + service restart (if applicable)
-[ ] HF-VERIFY   Self-check + GO/NO-GO
-```
-4. `notify_user` → wait for **Approved**
-
-## Step 2: DEV+TEST — Fix and self-verification
-
-1. Execute `view_file` on `agents/senior_full_stack.md`
-2. TDD:
-   - RED: test reproducing the issue (if applicable)
-   - GREEN: minimal fix
-   - REFACTOR: if necessary
-3. JSDoc on modified functions
-4. Restart affected services if applicable
-5. Self-verification:
-   - Does the fix work?
-   - Do tests pass?
-   - No regressions?
-6. Verdict: **GO ✅ / NO-GO ❌**
-7. `notify_user` → wait for **Approved**
-
----
-
-## When in doubt
-
-If during work it becomes clear that the task is more complex than a hotfix:
-> ⚠️ "Task turned out to be more complex than a hotfix. Recommend switching to /bugfix."
-
-Switching — only with user Approved.
-
----
-
-## Prompt template
-
-```
-@AGENTS.md /hotfix
-
-What to fix: [description, 1 sentence].
-File: [specific file].
-```
+---
+description: Launch the minimal 2-gate pipeline for trivial fixes (hotfix). Use for trivial fixes with blast radius ≈ 0.
+---
+
+# /hotfix — Launch Hotfix Pipeline (2 gates)
+
+> 🟡 **Mode:** Hotfix — for trivial fixes with minimal risk.
+> Full pipeline: `/start-task`. Bugfix (more serious): `/bugfix`.
+
+## When to use
+
+- Typos in text/code
+- CSS fixes (color, padding, font size)
+- Single-line logic fix
+- Copy-paste error
+- Blast radius ≈ 0 (affects 1–2 files, does not change contracts)
+
+## Do NOT use if
+
+- Affects > 2 files → `/bugfix`
+- Changes API contract → `/bugfix` or `/start-task`
+- Changes UI layout / adds screens → `/start-task`
+- Unsure → ask the user
+
+## Step 0: Load rules
+
+Execute `/pipeline-rules` — read the rules BEFORE starting work.
+
+## Step 1: CONDUCTOR — Classification
+
+1. Execute `view_file` on `agents/conductor.md`
+2. Confirm the task = hotfix (per Decision Tree: blast radius ≈ 0, 1–2 files)
+3. Create Mini Checklist:
+```
+[ ] HF-DEV-01   Fix + test + service restart (if applicable)
+[ ] HF-VERIFY   Self-check + GO/NO-GO
+```
+4. `notify_user` → wait for **Approved**
+
+## Step 2: DEV+TEST — Fix and self-verification
+
+1. Execute `view_file` on `agents/senior_full_stack.md`
+2. TDD:
+   - RED: test reproducing the issue (if applicable)
+   - GREEN: minimal fix
+   - REFACTOR: if necessary
+3. JSDoc on modified functions
+4. Restart affected services if applicable
+5. Self-verification:
+   - Does the fix work?
+   - Do tests pass?
+   - No regressions?
+6. Verdict: **GO ✅ / NO-GO ❌**
+7. `notify_user` → wait for **Approved**
+
+---
+
+## When in doubt
+
+If during work it becomes clear that the task is more complex than a hotfix:
+> ⚠️ "Task turned out to be more complex than a hotfix. Recommend switching to /bugfix."
+
+Switching — only with user Approved.
+
+---
+
+## Prompt template
+
+```
+@AGENTS.md /hotfix
+
+What to fix: [description, 1 sentence].
+File: [specific file].
+```