code-ai-installer 1.5.0 → 1.5.2

package/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/locales/en/.agents/workflows/pipeline-rules.md

@@ -1,24 +1,163 @@
----
-description: Absolute development pipeline rules. MUST NOT BE BROKEN.
 ---
+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
 
-# Pipeline Rules
+### 🟢 Bugfix Pipeline (4 gates) — `/bugfix`
+CONDUCTOR → DEV → REV → TEST
 
-The pipeline must not be skipped.
+### 🟡 Hotfix Pipeline (2 gates) — `/hotfix`
+CONDUCTOR → DEV+TEST
 
-## Pipeline
-TEST → PM → UX → ARCH → DEV → REV → OPS → 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
+```
 
-## Mandatory actions at every gate
-1. Read `agents/<role>.md`
-2. Follow that role protocol and its skills
+> 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 result to the user
-5. Wait for explicit `Approved` before moving forward
-
-## Forbidden
-- Fast-tracking gates
-- Writing code before the required gates are complete
-- Skipping mandatory protocol sections
-- Treating generic confirmation as permission to skip gates
-- Claiming a protocol was read when it was not
+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/locales/en/.agents/workflows/start-task.md

@@ -1,27 +1,130 @@
----
-description: Task launch template through the 8-agent pipeline. Use at the beginning of EVERY session.
 ---
+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
 
-# /start-task
+## Step 5: Code — ONLY after DEV gate + Approved
 
-## Steps
-1. Load `/pipeline-rules`
-2. Read `AGENTS.md`
-3. Read `agents/conductor.md`
-4. Start the pipeline gate by gate
-5. Do not apply code before DEV gate + explicit Approved
-6. If a gate fails, run a full Fix Cycle through DEV → REV → OPS → TEST
+- 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)
 
-## First prompt template
 ```
 @AGENTS.md /pipeline-rules
 
-Task: [what to do].
-Files: [known files].
+Task: [what to do, 1-2 sentences].
+Files: [specific files, if known].
 
 Rules:
-1. Start with Conductor
-2. Every gate: read protocol → complete all sections → full response → Approved
-3. Do not apply code before DEV gate + my Approved
+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/locales/en/AGENTS.md

@@ -84,6 +84,7 @@ Use skills (folders with `SKILL.md`). Full list:
 - $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)

package/locales/en/agents/senior_full_stack.md

@@ -180,11 +180,13 @@ The report for the conductor contains:
 - $mongodb_mongoose_best_practices
 - $n8n_pinecone_qdrant_supabase
 - $wix_self_hosted_embedded_script
+- $tailwind_beast_practices
 - (conditional) $wix_iframe_sdk
 - (conditional) $react_15_3_wix_iframe
 
+
 ---
-- $tailwind_beast_practices
+
 
 ## Agent response format (strict)
 

package/locales/en/prompt-examples.md

@@ -0,0 +1,152 @@
+# Prompt Examples for Pipeline Launch
+
+> Copy the relevant prompt, replace placeholders with your data, paste into chat.
+
+---
+
+## 🔵 Full Pipeline (`/start-task`) — new feature / refactoring
+
+### New Feature
+```
+@AGENTS.md Task:
+Implement [feature description].
+Full pipeline!
+
+SESSION RULES:
+1. Each gate: view_file agents/<role>.md → view_file on EVERY SKILL.md from the protocol skills → deliverable → notify_user → wait for "Approved"
+2. Skipping a gate or skill = BLOCKER
+3. Do not proceed without Approved
+```
+
+### Refactoring
+```
+@AGENTS.md Task:
+Refactor [description: what exactly we're refactoring and why].
+Full pipeline!
+
+SESSION RULES:
+1. Each gate: view_file agents/<role>.md → view_file on EVERY SKILL.md from the protocol skills → deliverable → notify_user → wait for "Approved"
+2. Skipping a gate or skill = BLOCKER
+3. Do not proceed without Approved
+```
+
+---
+
+## 🟢 Bugfix (`/bugfix`) — bug fix (4 gates)
+
+### Standard Bug
+```
+@AGENTS.md Task:
+Fix bug: [bug description, reproduction steps, expected vs actual behavior].
+Bugfix pipeline!
+
+SESSION RULES:
+1. Each gate: view_file agents/<role>.md → view_file on EVERY SKILL.md from the protocol skills → deliverable → notify_user → wait for "Approved"
+2. Skipping a gate or skill = BLOCKER
+3. Do not proceed without Approved
+```
+
+### Bug with File References
+```
+@AGENTS.md Task:
+@[path/to/file1] @[path/to/file2]
+Bug: [description]. Root cause likely in the referenced files.
+Bugfix pipeline!
+
+SESSION RULES:
+1. Each gate: view_file agents/<role>.md → view_file on EVERY SKILL.md → deliverable → notify_user → wait for "Approved"
+2. Skipping a gate = BLOCKER
+```
+
+---
+
+## 🟡 Hotfix (`/hotfix`) — minor fix (2 gates)
+
+### Typo / CSS / Single Line
+```
+@AGENTS.md Task:
+Hotfix: [fix description, e.g.: "fix typo in heading" or "change button color from #333 to #555"].
+Hotfix pipeline!
+
+SESSION RULES:
+1. Each gate: view_file agents/<role>.md → view_file on EVERY SKILL.md → deliverable → notify_user → wait for "Approved"
+2. Skipping a gate = BLOCKER
+```
+
+---
+
+## 🎨 Design Only (Google Stitch)
+
+### UI Screen Generation
+```
+@AGENTS.md Task:
+Create UI screens for [description: which screens, which application].
+Use Google Stitch via $google_stitch_skill.
+
+SESSION RULES:
+1. view_file agents/ux_ui_designer.md → view_file $google_stitch_skill → deliverable → notify_user → wait for "Approved"
+```
+
+---
+
+## 📄 Documentation Only
+
+### Document Adaptation / Creation
+```
+@AGENTS.md Task:
+[Documentation task description, e.g.: "adapt files X, Y, Z for global use"].
+Bugfix pipeline! (or Full pipeline — depending on complexity)
+
+SESSION RULES:
+1. Each gate: view_file agents/<role>.md → view_file on EVERY SKILL.md → deliverable → notify_user → wait for "Approved"
+2. Skipping a gate = BLOCKER
+```
+
+---
+
+## ⚡ Gate Transitions (User Responses)
+
+### Approve and Move to Next Gate
+```
+Approved. Next gate: agents/<role>.md. Skills: view_file required. Full format.
+```
+
+### Approve with Trigger (Wix / Shopify)
+```
+Approved. TEST gate. Wix.
+```
+
+### Reject / Return for Rework
+```
+NO-GO. Fix: [list of issues]. Return to [gate] gate.
+```
+
+---
+
+## 🔧 Utility Prompts
+
+### Check Status
+```
+Show the current Master Checklist and status of all gates.
+```
+
+### Run a Specific Agent
+```
+Run agents/<role>.md. Context: [brief description]. Skills: view_file required.
+```
+
+### Update Version
+```
+Update the version in package.json to X.Y.Z
+```
+
+---
+
+## 📝 Tips for Writing Prompts
+
+1. **Always start with `@AGENTS.md`** — this loads the agent system
+2. **Reference files with `@[path]`** — the agent immediately sees the context
+3. **Name the pipeline mode** — "Full pipeline!", "Bugfix pipeline!", "Hotfix pipeline!"
+4. **Add SESSION RULES** — this guarantees protocol compliance
+5. **Write "Approved" explicitly** — without this word the agent will not proceed to the next gate
+6. **Be specific** — the more precise the description, the better the result

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "code-ai-installer",
-  "version": "1.5.0",
+  "version": "1.5.2",
   "description": "Production-ready CLI to install code-ai agents and skills for multiple AI coding assistants.",
   "license": "MIT",
   "author": "Denis Harchenko",
@@ -49,18 +49,18 @@
   ],
   "dependencies": {
     "chalk": "^5.3.0",
-    "commander": "^12.1.0",
-    "fs-extra": "^11.2.0",
+    "commander": "^14.0.3",
+    "fs-extra": "^11.3.4",
     "prompts": "^2.4.2",
-    "yaml": "^2.8.2",
-    "zod": "^3.23.8"
+    "yaml": "^2.8.3",
+    "zod": "^4.3.6"
   },
   "devDependencies": {
     "@types/fs-extra": "^11.0.4",
-    "@types/node": "^22.10.2",
+    "@types/node": "^25.5.0",
     "@types/prompts": "^2.4.9",
     "tsx": "^4.19.2",
-    "typescript": "^5.7.2",
-    "vitest": "^2.1.8"
+    "typescript": "^6.0.2",
+    "vitest": "^4.1.1"
   }
 }