code-ai-installer 1.5.6 → 2.0.1

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

@@ -0,0 +1,25 @@
+version: 1
+name: "wix-self-hosted-embedded-script"
+display_name: "Wix Self-Hosted Embedded Script"
+description: "Practical runbook for Wix Self-Hosted Embedded Script — HTTPS locally, install webhook, embed script, resolve appInstanceId, DB-driven widget config, common errors, and DEMO-ready checklist."
+default_prompt: "Use $wix-self-hosted-embedded-script when the task matches the \"Wix Self-Hosted Embedded Script\" skill."
+triggers:
+  - "wix-self-hosted-embedded-script"
+  - "wix self hosted embedded script"
+  - "Wix Self-Hosted Embedded Script"
+  - "Practical runbook for Wix Self-Hosted Embedded Script — 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

@@ -0,0 +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.
+5. Wait for restart completion before reporting results.

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

@@ -0,0 +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
+```

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

@@ -0,0 +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].
+```

package/domains/development/locales/en/.agents/workflows/pipeline-rules.md

@@ -0,0 +1,163 @@
+---
+description: Absolute development pipeline rules. MUST NOT be violated.
+---
+
+# 🔴 ABSOLUTE RULE: Pipeline must not be skipped
+
+**This rule has no exceptions. Violation = blocker.**
+
+## Pipeline — 3 Modes
+
+### 🔵 Full Pipeline (8 gates) — `/start-task`
+CONDUCTOR → PM → UX → ARCH → DEV → REV → OPS → TEST → RG
+
+### 🟢 Bugfix Pipeline (4 gates) — `/bugfix`
+CONDUCTOR → DEV → REV → TEST
+
+### 🟡 Hotfix Pipeline (2 gates) — `/hotfix`
+CONDUCTOR → DEV+TEST
+
+### Decision Tree (mode selection)
+```
+User task
+  │
+  ├─ New feature / refactoring / new API / new screen?
+  │    └─ 🔵 Full Pipeline
+  │
+  ├─ Bug in existing functionality?
+  │    ├─ Affects > 2 files or changes API contract?
+  │    │    └─ 🟢 Bugfix (4 gates)
+  │    ├─ Affects 1–2 files, blast radius ≈ 0?
+  │    │    └─ 🟡 Hotfix (2 gates)
+  │    └─ Unsure → ask the user
+  │
+  └─ User explicitly specified mode (/bugfix, /hotfix)?
+       └─ Use the specified mode
+```
+
+> Conductor **does not receive new skills** — uses existing `$board`, `$handoff`, `$gates`.
+
+## Mandatory actions on EVERY gate (all modes)
+
+1. `view_file` on `agents/<role>.md` — read the agent protocol
+2. Follow **its** instructions, use **its** skills
+3. Produce deliverable + Handoff Envelope
+4. Present the result to the user via `notify_user`
+5. **Wait for explicit "Approved" from the user** before moving to the next gate
+
+---
+
+## 🛑 STOP RULES (before any code action)
+
+### Rule 1: Agent protocol — step by step, no collapsing
+Each paragraph (§) in the agent file = **a separate step**.
+- Agent MUST pass ALL paragraphs in the order specified in the file
+- Collapsing multiple §§ into a single response is forbidden
+- If agent skips a §, it MUST state the reason: "§X skipped: [reason]"
+
+### Rule 2: Code is applied ONLY after full protocol pass
+- ❌ Must not: write code first → then write the report
+- ✅ Must: pass all §§ of the protocol → present plan → Approved → apply code
+
+### Rule 3: Full response format — no shortcuts
+- Use **"Agent Response Format (strict)"** from the agent file
+- Every section of the format is MANDATORY — skipping = violation
+- If a section is not applicable, explicitly write: "N/A — [reason]"
+
+### Rule 4: Fix Cycle — full pass through agents
+On FAIL at any gate:
+1. Current agent (e.g. Tester) produces FAIL Report + HANDOFF Envelope → DEV
+2. DEV reads `agents/senior_full_stack.md` and passes FULL protocol (§0–§7)
+3. DEV HANDOFF → REV → OPS → TEST (each gate with view_file + protocol + Approved)
+4. No "quick fixes" without passing through agents
+
+### Rule 5: Self-check before notify_user
+Before each `notify_user` the agent MUST internally verify:
+- [ ] Did I read the agent file (`view_file` on `agents/<role>.md`)?
+- [ ] Did I pass ALL paragraphs of the protocol?
+- [ ] Am I using the FULL response format?
+- [ ] Is there a HANDOFF Envelope with ALL mandatory fields?
+- [ ] Did I NOT apply code before receiving Approved?
+
+---
+
+## Prohibited
+
+- ❌ "Fast-tracking" gates (skipping multiple gates at once)
+- ❌ Interpreting "Confirmed" as permission to skip gates
+- ❌ Starting the pipeline without explicit user permission
+- ❌ Moving to the next gate without "Approved" from the user
+- ❌ Writing code (DEV gate) before passing prior gates
+- ❌ Applying code before completing the full agent protocol
+- ❌ Shortening the response format (every section is mandatory)
+- ❌ Ignoring protocol paragraphs, considering the task "trivial"
+- ❌ Lying about reading the protocol (if no `view_file` — it was not read)
+
+---
+
+## 🔒 MECHANICAL BLOCKS
+
+> These rules were introduced after an incident where the agent ignored the pipeline,
+> auto-approved the ARCH gate, ignored an open user question,
+> wrote code without TDD, and delivered a broken preview.
+
+### Block 1: ShouldAutoProceed = false ALWAYS
+```
+notify_user → ShouldAutoProceed: false
+```
+No exceptions. On EVERY notify_user. Even on "trivial" gates.
+Even if the agent is "confident". The user ALWAYS decides.
+
+### Block 2: Pre-flight check before ANY write_to_file / replace_file_content
+Before every code-writing tool call the agent MUST:
+1. Quote the LAST user message containing the word "Approved"
+2. If there is no quote — CODE MUST NOT BE WRITTEN
+3. System-generated messages are NOT considered "Approved"
+4. Auto-proceeded artifacts are NOT considered "Approved"
+
+### Block 3: Answering a question — quoting is mandatory
+If the agent asked the user a question:
+1. The agent's next response MUST start with: `> Your answer: [exact quote]`
+2. If there is no quote — no answer was given — STOP, repeat the question
+3. Guessing the answer for the user is forbidden
+4. Accepting a system-generated message as an answer is forbidden
+
+### Block 4: Strict TDD (DEV gate)
+1. RED: write FAILING tests FIRST
+2. GREEN: minimal code to make tests pass
+3. REFACTOR: improve code without changing behavior
+4. Writing code before tests = violation = blocker
+
+### Block 5: Skills — mandatory reading via view_file
+Each agent (`agents/<role>.md`) references skills in `.agents/skills/`.
+1. Agent MUST execute `view_file` on `SKILL.md` of EVERY skill referenced in the agent protocol
+2. If there was no `view_file` — the skill is NOT considered applied
+3. Patterns, anti-patterns, code examples, best practices from skills — mandatory for application
+4. In the deliverable the agent MUST state: `Skills applied: [list]` with `view_file` confirmation
+5. Formal checkmarks without actual reading = violation = blocker
+
+---
+
+## Mandatory artifacts
+
+### task.md (Antigravity brain — automatic)
+- **Created by:** Conductor at Gate 0
+- **Updated by:** EVERY agent after completing their gate
+- **Contains:** Master Checklist + Handoff Envelopes Status + Fix Cycle tracking
+- **Rule:** If task.md is not updated after a gate — the gate is not considered complete
+
+### implementation_plan.md
+- **Created by:** Architect at Gate 3 (ARCH) — or Conductor, if the task does not require ARCH
+- **Saved to:** `docs/reports/architect/plan-<task-name>.md` (in the project)
+- **Contains:** Proposed Changes + files + Verification Plan
+- **Rule:** DEV must read the plan before starting implementation. Reviewer references it during code review.
+
+### walkthrough.md (Antigravity brain — automatic)
+- **Created by:** Tester at Gate 7 (TEST) — or Release Gate
+- **Contains:** what was done, what was verified, validation results
+- **Rule:** update on each Fix Cycle and before Release Gate
+
+### docs/architecture.md + docs/ADR-log.md (in the project)
+- **Updated by:** Architect on any architectural decision
+- **Referenced by:** Reviewer and Architect on each gate
+- **Rule:** New ADRs are added to ADR-log.md. Architecture.md is updated when the stack, patterns, or constraints change

package/domains/development/locales/en/.agents/workflows/start-task.md

@@ -0,0 +1,130 @@
+---
+description: Template for launching a task through the 8-agent pipeline. Use at the start of EVERY session.
+---
+
+# /start-task — Launch a task through the pipeline
+
+## Step 0: Select pipeline mode
+
+Determine the task type and choose the workflow:
+- 🔵 **New feature / refactoring** → continue with `/start-task` (this file)
+- 🟢 **Bugfix** (> 2 files, non-trivial) → switch to `/bugfix`
+- 🟡 **Hotfix** (1–2 files, blast radius ≈ 0) → switch to `/hotfix`
+
+> If you selected `/bugfix` or `/hotfix` — stop reading this file and follow the chosen workflow.
+
+## Step 1: Load pipeline rules
+
+Execute `/pipeline-rules` — read and acknowledge ALL rules BEFORE starting work.
+
+## Step 2: Initialize agents
+Execute `view_file` on `AGENTS.md` — confirm the list of agents and skills.
+
+## Step 3: Launch the Conductor
+Execute `view_file` on `agents/conductor.md` — read the protocol and create the Master Checklist in `task.md`.
+
+## Step 4: Pass each gate STRICTLY by protocol
+
+On EVERY gate, mandatory steps:
+1. `view_file` on `agents/<role>.md` — read the agent protocol
+2. Pass EACH section of the protocol in order (no "collapsing")
+3. Use the **full** "Agent Response Format (strict)" from the agent file
+4. If a section is not applicable — explicitly write: "N/A — [reason]"
+5. Produce deliverable + Handoff Envelope with ALL mandatory fields
+6. Present the result via `notify_user`
+7. **Wait for explicit "Approved"** before moving to the next gate
+
+## Step 5: Code — ONLY after DEV gate + Approved
+
+- First, the DEV agent passes ALL sections of the protocol (§0–§7)
+- Then proposes the change plan
+- User approves
+- ONLY THEN the agent applies code
+
+## Step 6: Fix Cycle (on FAIL)
+
+If the tester or reviewer finds a bug:
+1. Current agent produces FAIL Report + HANDOFF Envelope → DEV
+2. User approves FAIL HANDOFF
+3. DEV reads `agents/senior_full_stack.md` and passes the FULL protocol
+4. DEV HANDOFF → REV → OPS → TEST (each gate with full protocol)
+5. No "quick fixes" without passing through agents
+
+---
+
+## First prompt template (copy and fill)
+
+```
+@AGENTS.md /pipeline-rules
+
+Task: [what to do, 1-2 sentences].
+Files: [specific files, if known].
+
+Rules:
+1. Start with the Conductor (agents/conductor.md)
+2. Each gate: view_file → ALL protocol sections → full format → Approved
+3. Do not apply code until DEV gate + my Approved
+4. Fix Cycle = full pass through agents
+```
+
+---
+
+## Session recommendations
+
+- **One session = 3-4 gates maximum** (context is preserved)
+- **Approved is given on EACH gate**, not per session
+- **Session 1:** Conductor → Approved → PM → Approved → UX → Approved
+- **Session 2:** ARCH → Approved → DEV → Approved → REV → Approved
+- **Session 3:** OPS → Approved → TEST → Approved → RG → Approved
+- Each new session — start with `/start-task`
+
+## Mandatory questions from agents
+
+Each agent that has a Clarification/Questions section in their protocol MUST:
+1. Ask questions to the user BEFORE performing work
+2. Minimum questions (from agent protocol): PM — 5+, ARCH — 5-10, DEV — as needed, Tester — 5+
+3. If the task seems "obvious" — still ask at minimum 2-3 clarifying questions
+4. Wait for user answers BEFORE continuing
+5. The only exception: the user explicitly wrote "no questions"
+
+## When "cutting corners" — one phrase
+
+If the model shortcuts, say:
+> "Stop. Section [X] of protocol agents/<role>.md. Re-read and execute."
+
+---
+
+## Feedback protocol (mandatory)
+
+The model MUST provide feedback to the user at every stage:
+
+### 1. Warning when tempted to shortcut
+If the task looks "trivial", the model MUST write:
+```
+⚠️ Task looks trivial. My instinct is to do it quickly.
+But following the protocol, I'm going through the full cycle. Sections: [list].
+```
+
+### 2. User prompt assessment
+At the start of each task the model assesses the prompt:
+```
+📊 Prompt assessment:
+- Clarity: [high/medium/low]
+- What helped: [what was useful]
+- What's missing: [what to add for effectiveness]
+```
+
+### 3. Tips in Handoff Envelope
+In each Handoff add a section:
+```
+💡 Feedback: [tip for the user, if any]
+```
+
+### 4. Retrospective at session end
+Before finishing work:
+```
+🔄 Retrospective:
+- Gates passed: X
+- Protocol violations: X
+- What to improve in the next session: [recommendation]
+```

package/domains/development/locales/en/AGENTS.md

@@ -0,0 +1,136 @@
+<!-- code-ai: target=gpt-codex; asset=orchestrator; normalized_hints=none -->
+<!-- codex: reasoning=medium; note="auto-adapted default" -->
+# AGENTS.md - Web Development Orchestra
+
+## Source of truth by roles
+Roles are described in:
+- agents/conductor.md
+- agents/product_manager.md
+- agents/ux_ui_designer.md
+- agents/architect.md
+- agents/devops.md
+- agents/senior_full_stack.md
+- agents/reviewer.md
+- agents/tester.md
+
+Follow these roles during work. If needed, open the corresponding role file and apply it.
+
+---
+
+## Skills (explicitly call)
+Use skills (folders with `SKILL.md`). Full list:
+
+### Core / Orchestration
+- $board
+- $handoff
+- $memory
+- $gates
+- $release-gate
+- $release-gate-checklist-template
+
+### Product Management
+- $pm-interview
+- $pm-prd
+- $pm-backlog
+
+### UX/UI / Design
+- $ux-discovery
+- $ux-spec
+- $ui-inventory
+- $a11y-baseline
+- $design-intake
+- $design-parity-review
+- $design-systems
+- $ui-a11y-smoke-review
+- $google-stitch-skill
+
+### Architecture
+- $current-state-analysis
+- $system-design-checklist
+- $architecture-doc
+- $architecture-compliance-review
+- $design-patterns-reference
+- $adr-log
+- $api-contracts
+- $data-model
+- $threat-model-baseline
+- $observability-plan
+- $deployment-ci-plan
+- $docker-kubernetes-architecture
+- $k8s-manifests-conventions
+- $n8n-pinecone-qdrant-supabase
+- $wix-self-hosted-embedded-script
+- $wix-iframe-sdk
+- $react-15-3-wix-iframe (conditional, only for Wix iFrame / React 15.3)
+
+### Development (Senior Full Stack)
+- $tdd-workflow
+- $testing-strategy-js
+- $tests-quality-review
+- $es2025-beast-practices
+- $typescript-beast-practices
+- $react-beast-practices
+- $tanstack-beast-practices
+- $state-zustand-beast-practices
+- $state-rtk-beast-practices
+- $styling-css-stack
+- $tooling-bun-biome
+- $node-express-beast-practices
+- $go-beast-practices
+- $security-baseline-dev
+- $observability-logging
+- $dev-reference-snippets
+- $mongodb-mongoose-best-practices
+- $n8n-pinecone-qdrant-supabase
+- $wix-self-hosted-embedded-script
+- $wix-iframe-sdk
+- $tailwind-beast-practices
+- $react-15-3-wix-iframe (conditional, only for Wix iFrame / React 15.3)
+
+### Review (Best Practices + Security)
+- $code-review-checklist
+- $api-contract-compliance-review
+- $security-review
+- $security-review-baseline
+- $cloud-infrastructure-security
+- $dependency-supply-chain-review
+- $observability-review
+- $performance-review-baseline
+- $review-reference-snippets
+
+### Testing (QA)
+- $qa-test-plan
+- $qa-manual-run
+- $qa-api-contract-tests
+- $qa-browser-testing
+- $qa-security-smoke-tests
+- $qa-ui-a11y-smoke
+- $qa-e2e-playwright
+
+---
+
+## Gates (Pipeline)
+PM(PRD) -> UX(UX Spec) -> ARCH(Architecture/ADR/Contracts) -> DEV(TDD) -> REV(Security/Best) -> OPS(Infrastructure/CI-CD) -> TEST(Test plan/report) -> RG(Release Gate)
+
+---
+
+## Mandatory function documentation rule
+- For all functions in the codebase, use a JSDoc block in this format:
+
+```js
+/**
+ * Calculates the sum of two numbers.
+ * @param {number} a - First number.
+ * @param {number} b - Second number.
+ * @returns {number} Sum of a and b.
+ */
+function add(a, b) {
+    return a + b;
+}
+```
+
+- This requirement is mandatory for DEV and REV stages.
+
+## Mandatory TDD rule
+- Apply the TDD cycle to all development tasks: RED -> GREEN -> REFACTOR.
+- This requirement is mandatory for DEV and REV stages (same as JSDoc).