code-ai-installer 4.0.1-a → 4.0.1-c

package/package.json

@@ -1,16 +1,16 @@
 {
   "name": "code-ai-installer",
-  "version": "4.0.1-a",
+  "version": "4.0.1-c",
   "description": "Production-ready CLI to install code-ai agents and skills for multiple AI coding assistants. Bundles the code-ai-mcp MCP server for Claude Code.",
   "license": "MIT",
-  "author": "Denis Harchenko",
+  "author": "Denish1209",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/denish12/codex-ai-agent-and-skills.git"
+    "url": "git+https://github.com/denish12/code-ai-monorepo.git"
   },
-  "homepage": "https://github.com/denish12/codex-ai-agent-and-skills#readme",
+  "homepage": "https://github.com/denish12/code-ai-monorepo#readme",
   "bugs": {
-    "url": "https://github.com/denish12/codex-ai-agent-and-skills/issues"
+    "url": "https://github.com/denish12/code-ai-monorepo/issues"
   },
   "type": "module",
   "files": [

package/domains/analytics/CONTEXT.md

@@ -1,25 +0,0 @@
-# Обзор проекта
-
-| Поле | Значение |
-|------|----------|
-| **Домен** | Business Analytics |
-| **Описание** | Система агентов для бизнес-аналитики и стратегического анализа |
-| **Текущая фаза** | MVP |
-
-## Результаты пайплайна (Full — `/analyze`)
-
-| Сессия | Gate | Статус | Ключевой результат | Дата |
-|--------|------|--------|---------------------|------|
-| 1 | Conductor | ☐ | — | — |
-| 1 | Interviewer | ☐ | — | — |
-| 2 | Аналитики: Researcher | ☐ | — | — |
-| 2 | Аналитики: Data Analyst | ☐ | — | — |
-| 2 | Аналитики: Strategist | ☐ | — | — |
-| 3 | Критики: Researcher | ☐ | — | — |
-| 3 | Критики: Data Analyst | ☐ | — | — |
-| 3 | Критики: Strategist | ☐ | — | — |
-| 4 | Mediator | ☐ | — | — |
-| 4.5 | Mediator (Synthesis) | ☐/N/A | — | — |
-| 5 | Designer | ☐ | — | — |
-| 5 | Layouter | ☐ | — | — |
-| 5 | Release Gate | ☐ | — | — |

package/domains/analytics/locales/en/CONTEXT.md

@@ -1,25 +0,0 @@
-# Project Overview
-
-| Field | Value |
-|-------|-------|
-| **Domain** | Business Analytics |
-| **Description** | Agent system for business analytics and strategic analysis |
-| **Current Phase** | MVP |
-
-## Pipeline Results (Full — `/analyze`)
-
-| Session | Gate | Status | Key Result | Date |
-|---------|------|--------|------------|------|
-| 1 | Conductor | ☐ | — | — |
-| 1 | Interviewer | ☐ | — | — |
-| 2 | Analysts: Researcher | ☐ | — | — |
-| 2 | Analysts: Data Analyst | ☐ | — | — |
-| 2 | Analysts: Strategist | ☐ | — | — |
-| 3 | Critics: Researcher | ☐ | — | — |
-| 3 | Critics: Data Analyst | ☐ | — | — |
-| 3 | Critics: Strategist | ☐ | — | — |
-| 4 | Mediator | ☐ | — | — |
-| 4.5 | Mediator (Synthesis) | ☐/N/A | — | — |
-| 5 | Designer | ☐ | — | — |
-| 5 | Layouter | ☐ | — | — |
-| 5 | Release Gate | ☐ | — | — |

package/domains/content/CONTEXT.md

@@ -1,19 +0,0 @@
-# Обзор проекта
-
-| Поле | Значение |
-|------|----------|
-| **Домен** | Content Production |
-| **Описание** | Система агентов для производства контента |
-| **Текущая фаза** | MVP |
-
-## Результаты пайплайна
-
-| Gate | Статус | Ключевой результат | Дата |
-|------|--------|---------------------|------|
-| Conductor | ☐ | — | — |
-| Strategist | ☐ | — | — |
-| Researcher | ☐ | — | — |
-| Copywriter | ☐ | — | — |
-| Visual Concept | ☐ | — | — |
-| Reviewer | ☐ | — | — |
-| Release Gate | ☐ | — | — |

package/domains/content/locales/en/CONTEXT.md

@@ -1,19 +0,0 @@
-# Project Overview
-
-| Field | Value |
-|------|----------|
-| **Domain** | Content Production |
-| **Description** | System of agents for content production |
-| **Current Phase** | MVP |
-
-## Pipeline Results
-
-| Gate | Status | Key Deliverable | Date |
-|------|--------|---------------------|------|
-| Conductor | ☐ | — | — |
-| Strategist | ☐ | — | — |
-| Researcher | ☐ | — | — |
-| Copywriter | ☐ | — | — |
-| Visual Concept | ☐ | — | — |
-| Reviewer | ☐ | — | — |
-| Release Gate | ☐ | — | — |

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

@@ -1,56 +0,0 @@
----
-description: Auto-restart affected Docker containers after code changes
----
-
-# Auto-Restart Affected Containers
-
-After **any code change** to a file inside one of the application source directories, the corresponding Docker service **must be restarted** automatically without asking the user.
-
-## Source -> Service Mapping
-
-Do not hardcode service or container names from a specific product.
-
-For the current repository:
-
-1. Inspect the active Docker Compose file (`docker-compose.yml`, `docker-compose.yaml`, `compose.yml`, or `compose.yaml`).
-2. Identify which service owns the changed source path by checking:
-   - `build.context`
-   - bind-mounted `volumes`
-   - existing service naming conventions in the repo
-3. Restart the matching Compose service name, not a project-specific container name.
-
-Infrastructure-only changes (`infra/`, compose files, reverse proxy config) do **not** trigger an app-service restart by this workflow.
-Config/env-only changes do **not** trigger an app-service restart by this workflow.
-
-## Steps
-
-1. After editing file(s), determine which app or package directory was affected.
-2. Map that path to the Docker Compose service for the current project.
-3. Run the restart command:
-
-// turbo
-```
-docker compose restart <service_name>
-```
-
-Example: if `apps/frontend/src/components/SomeComponent.jsx` belongs to the `frontend` service:
-```
-docker compose restart frontend
-```
-
-4. If **multiple** services were affected, restart all of them in one command:
-
-// turbo
-```
-docker compose restart <service_one> <service_two>
-```
-
-5. Do **not** ask the user for permission - this is a turbo step.
-6. Wait for the restart to complete before reporting results.
-
-## Important Notes
-
-- The working directory for `docker compose` must be the project root that contains the active Compose file.
-- Use Compose service names, not Docker container names, because container names are project-specific.
-- Shared infrastructure services such as a gateway, proxy, or database usually do **not** need restart for ordinary app-level code changes unless the edited files directly affect them.
-- This workflow is **implicit** - it runs as part of any development task, not as a standalone action.

package/domains/development/CONTEXT.md

@@ -1,62 +0,0 @@
-# 🎯 Обзор проекта
-
-| Поле | Значение |
-|------|----------|
-| **Название** | `<имя проекта>` |
-| **Описание** | `<краткое описание>` |
-| **Текущая фаза** | `<Discovery / MVP / v1 / Production>` |
-| **Дата создания** | `<YYYY-MM-DD>` |
-| **Последнее обновление** | `<YYYY-MM-DD>` |
-
----
-
-## 🔄 Результаты пайплайна
-
-| Gate | Статус | Ключевой результат | Дата |
-|------|--------|---------------------|------|
-| Conductor | ☐ | — | — |
-| PM (PRD) | ☐ | — | — |
-| UX/UI | ☐ | — | — |
-| Architect | ☐ | — | — |
-| DevOps | ☐ | — | — |
-| Dev (TDD) | ☐ | — | — |
-| Reviewer | ☐ | — | — |
-| Tester | ☐ | — | — |
-| Release Gate | ☐ | — | — |
-
----
-
-## 📋 Ключевые решения (ADR)
-
-| ID | Решение | Обоснование | Статус |
-|----|---------|-------------|--------|
-| ADR-001 | `<описание решения>` | `<почему выбрано>` | `Accepted / Superseded / Deprecated` |
-
----
-
-## 📊 Текущее состояние
-
-### ✅ Сделано
-- `<что завершено>`
-
-### ⏳ В процессе
-- `<что сейчас в работе>`
-
-### 🚫 Заблокировано
-- `<что заблокировано и чем>`
-
----
-
-## ❓ Открытые вопросы
-
-| ID | Вопрос | Владелец | Дедлайн | Статус |
-|----|--------|----------|---------|--------|
-| Q-001 | `<вопрос>` | `<кто отвечает>` | `<YYYY-MM-DD>` | `Open / Resolved` |
-
----
-
-## 📝 История сессий
-
-| Сессия | Дата | Краткий итог | Артефакты |
-|--------|------|--------------|-----------|
-| Session 1 | `<YYYY-MM-DD>` | `<что сделано>` | `<ссылки на файлы>` |

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

@@ -1,24 +0,0 @@
----
-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/CONTEXT.md

@@ -1,62 +0,0 @@
-# 🎯 Project Overview
-
-| Field | Value |
-|-------|-------|
-| **Name** | `<project name>` |
-| **Description** | `<brief description>` |
-| **Current Phase** | `<Discovery / MVP / v1 / Production>` |
-| **Created** | `<YYYY-MM-DD>` |
-| **Last Updated** | `<YYYY-MM-DD>` |
-
----
-
-## 🔄 Pipeline Results
-
-| Gate | Status | Key Output | Date |
-|------|--------|------------|------|
-| Conductor | ☐ | — | — |
-| PM (PRD) | ☐ | — | — |
-| UX/UI | ☐ | — | — |
-| Architect | ☐ | — | — |
-| DevOps | ☐ | — | — |
-| Dev (TDD) | ☐ | — | — |
-| Reviewer | ☐ | — | — |
-| Tester | ☐ | — | — |
-| Release Gate | ☐ | — | — |
-
----
-
-## 📋 Key Decisions (ADR)
-
-| ID | Decision | Rationale | Status |
-|----|----------|-----------|--------|
-| ADR-001 | `<decision description>` | `<why chosen>` | `Accepted / Superseded / Deprecated` |
-
----
-
-## 📊 Current State
-
-### ✅ Done
-- `<what is completed>`
-
-### ⏳ In Progress
-- `<what is being worked on>`
-
-### 🚫 Blocked
-- `<what is blocked and by what>`
-
----
-
-## ❓ Open Questions
-
-| ID | Question | Owner | Deadline | Status |
-|----|----------|-------|----------|--------|
-| Q-001 | `<question>` | `<who is responsible>` | `<YYYY-MM-DD>` | `Open / Resolved` |
-
----
-
-## 📝 Session History
-
-| Session | Date | Summary | Artifacts |
-|---------|------|---------|-----------|
-| Session 1 | `<YYYY-MM-DD>` | `<what was done>` | `<file references>` |

package/domains/product/CONTEXT.md

@@ -1,40 +0,0 @@
-# Обзор проекта
-
-| Поле | Значение |
-|------|----------|
-| **Домен** | Product Management (B2B SaaS) |
-| **Описание** | Система агентов для продуктового менеджмента с двумя adversarial-осями |
-| **Текущая фаза** | MVP |
-
-## Результаты пайплайна A — `/ship-right-thing` (Customer-vs-Business)
-
-| Сессия | Gate | Статус | Ключевой результат | Дата |
-|--------|------|--------|---------------------|------|
-| 1 | Conductor | ☐ | — | — |
-| 1 | Discovery | ☐ | — | — |
-| 2 | Customer-Champion: Strategist | ☐ | — | — |
-| 3 | Business-Champion: Strategist | ☐ | — | — |
-| 4 | Mediator (Strategy Synthesis) | ☐ | — | — |
-| 5 | PM (prioritization + PRD) | ☐ | — | — |
-| 5 | UX Designer (wireframes) | ☐ | — | — |
-| 5 | Tech Lead (feasibility) | ☐ | — | — |
-| 5 | Data Analyst (metric plan) | ☐ | — | — |
-| 6 | Designer | ☐ | — | — |
-| 6 | Layouter | ☐ | — | — |
-| 6 | Release Gate | ☐ | — | — |
-
-## Результаты пайплайна B — `/shape-prioritize` (Build-vs-Cut)
-
-| Сессия | Gate | Статус | Ключевой результат | Дата |
-|--------|------|--------|---------------------|------|
-| 1 | Conductor | ☐ | — | — |
-| 1 | Discovery (scope intake) | ☐ | — | — |
-| 2 | Build-Camp: PM + Tech Lead | ☐ | — | — |
-| 3 | Cut-Camp: PM + Tech Lead | ☐ | — | — |
-| 4 | Mediator (Scope Synthesis) | ☐ | — | — |
-| 5 | PM (final PRD) | ☐ | — | — |
-| 5 | UX Designer | ☐ | — | — |
-| 5 | Data Analyst | ☐ | — | — |
-| 6 | Designer | ☐ | — | — |
-| 6 | Layouter | ☐ | — | — |
-| 6 | Release Gate | ☐ | — | — |

package/domains/product/locales/en/CONTEXT.md

@@ -1,40 +0,0 @@
-# Project Overview
-
-| Field | Value |
-|------|----------|
-| **Domain** | Product Management (B2B SaaS) |
-| **Description** | Agent system for product management with two adversarial axes |
-| **Current Phase** | MVP |
-
-## Pipeline A Results — `/ship-right-thing` (Customer-vs-Business)
-
-| Session | Gate | Status | Key Result | Date |
-|--------|------|--------|---------------------|------|
-| 1 | Conductor | ☐ | — | — |
-| 1 | Discovery | ☐ | — | — |
-| 2 | Customer-Champion: Strategist | ☐ | — | — |
-| 3 | Business-Champion: Strategist | ☐ | — | — |
-| 4 | Mediator (Strategy Synthesis) | ☐ | — | — |
-| 5 | PM (prioritization + PRD) | ☐ | — | — |
-| 5 | UX Designer (wireframes) | ☐ | — | — |
-| 5 | Tech Lead (feasibility) | ☐ | — | — |
-| 5 | Data Analyst (metric plan) | ☐ | — | — |
-| 6 | Designer | ☐ | — | — |
-| 6 | Layouter | ☐ | — | — |
-| 6 | Release Gate | ☐ | — | — |
-
-## Pipeline B Results — `/shape-prioritize` (Build-vs-Cut)
-
-| Session | Gate | Status | Key Result | Date |
-|--------|------|--------|---------------------|------|
-| 1 | Conductor | ☐ | — | — |
-| 1 | Discovery (scope intake) | ☐ | — | — |
-| 2 | Build-Camp: PM + Tech Lead | ☐ | — | — |
-| 3 | Cut-Camp: PM + Tech Lead | ☐ | — | — |
-| 4 | Mediator (Scope Synthesis) | ☐ | — | — |
-| 5 | PM (final PRD) | ☐ | — | — |
-| 5 | UX Designer | ☐ | — | — |
-| 5 | Data Analyst | ☐ | — | — |
-| 6 | Designer | ☐ | — | — |
-| 6 | Layouter | ☐ | — | — |
-| 6 | Release Gate | ☐ | — | — |