code-ai-installer 1.3.1 → 1.5.0

package/locales/en/.agents/skills/architecture_compliance_review/agents/gemini.json

@@ -0,0 +1,18 @@
+{
+  "name": "architecture_compliance_review",
+  "display_name": "Architecture Compliance Review",
+  "description": "Check whether code complies with the architecture and ADRs - module boundaries, layers, dependencies, conventions, and red flags.",
+  "default_prompt": "Use $architecture_compliance_review when the task matches the \"Architecture Compliance Review\" skill.",
+  "triggers": [
+    "architecture_compliance_review",
+    "architecture compliance review",
+    "Check whether code complies with the architecture and ADRs - module boundaries, layers, dependencies, conventions, and red flags"
+  ],
+  "capabilities": [
+    "architecture",
+    "compliance",
+    "review"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/locales/en/.agents/skills/architecture_compliance_review/agents/openai.yaml

@@ -0,0 +1,8 @@
+interface:
+  display_name: "Architecture Compliance Review"
+  short_description: "Check whether code complies with the architecture and ADRs - module boundaries, layers, depende…"
+  default_prompt: "Use $architecture_compliance_review when the task matches the \"Architecture Compliance Review\" skill."
+dependencies:
+  tools: []
+policy:
+  allow_implicit_invocation: true

package/locales/en/.agents/skills/architecture_compliance_review/agents/qwen.json

@@ -0,0 +1,18 @@
+{
+  "name": "architecture_compliance_review",
+  "display_name": "Architecture Compliance Review",
+  "description": "Check whether code complies with the architecture and ADRs - module boundaries, layers, dependencies, conventions, and red flags.",
+  "default_prompt": "Use $architecture_compliance_review when the task matches the \"Architecture Compliance Review\" skill.",
+  "triggers": [
+    "architecture_compliance_review",
+    "architecture compliance review",
+    "Check whether code complies with the architecture and ADRs - module boundaries, layers, dependencies, conventions, and red flags"
+  ],
+  "capabilities": [
+    "architecture",
+    "compliance",
+    "review"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/locales/en/.agents/skills/architecture_compliance_review/agents/skill.yaml

@@ -0,0 +1,22 @@
+version: 1
+name: "architecture_compliance_review"
+display_name: "Architecture Compliance Review"
+description: "Check whether code complies with the architecture and ADRs - module boundaries, layers, dependencies, conventions, and red flags."
+default_prompt: "Use $architecture_compliance_review when the task matches the \"Architecture Compliance Review\" skill."
+triggers:
+  - "architecture_compliance_review"
+  - "architecture compliance review"
+  - "Check whether code complies with the architecture and ADRs - module boundaries, layers, dependencies, conventions, and red flags"
+capabilities:
+  - "architecture"
+  - "compliance"
+  - "review"
+tools: []
+invocation:
+  explicit: true
+  implicit: true
+localization:
+  default_locale: "en"
+  available_locales:
+    - "ru"
+    - "en"

package/locales/en/.agents/skills/architecture_doc/SKILL.md

@@ -0,0 +1,204 @@
+---
+name: architecture_doc
+description: Architectural document based on PRD+UX — modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan.
+---
+
+# Skill: Architecture Document
+
+Create an architectural document based on PRD and UX Spec.
+
+**Sections:**
+1. [General rules](#1-general-rules)
+2. [Document Structure](#2-document-structure)
+3. [Component Diagram](#3-component-diagram)
+4. [Data Flow (Sequence)](#4-data-flow)
+5. [Anti-patterns](#5-anti-patterns)
+6. [Output Template](#6-output)
+
+---
+
+## 1. General rules
+
+| Rule | Convention |
+|---------|-----------|
+| **Goal** | Connect "what" (PRD) with "how" (code) |
+| **Audience** | Full Stack, DevOps, Reviewer, PM |
+| **Format** | Markdown with Mermaid diagrams |
+| **Dependencies** | Must reference PRD, UX, ADRs, Contracts |
+| **Scope** | Complete system (frontend, backend, DB, external) |
+| **Update frequency** | Living document; update when architecture changes |
+
+---
+
+## 2. Document Structure
+
+### 2.1 System Overview
+- **Vision:** 1-2 sentence summary of the technical solution.
+- **Constraints:** Hard limits (e.g., "Must run in Wix iframe", "PostgreSQL only", "Max 100ms latency").
+- **Key metrics NFRs:** Scale targets (req/sec, # of users), availability (99.9%).
+
+### 2.2 Component Architecture
+- **Web Client (Frontend):** Framework (React), layout, state management (Zustand/RTK), routing.
+- **API Gateway / Backend:** Framework (Express/Go), auth layer, core modules.
+- **Data Layer:** DBMS, caching, object storage.
+- **External Integrations:** Wix API, Email provider, Payment gateway.
+- *(Include Mermaid Component Diagram here)*
+
+### 2.3 Core Modules
+Describe each logical module (e.g., Auth, Billing, Products):
+- **Responsibility:** What it does.
+- **Dependencies:** What it calls.
+- **Data:** Key entities it owns.
+
+### 2.4 Data Architecture
+- **Schema Overview:** Key collections/tables (link to full Data Model).
+- **Storage Strategy:** Where data lives (MongoDB Atlas, local SQLite for dev).
+- **Caching Strategy:** Redis? In-memory? Browser cache?
+
+### 2.5 Key User Flows (Sequence)
+- Describe 2-3 critical paths (e.g., "User Login & Dashboard Load", "Purchase Flow").
+- *(Include Mermaid Sequence Diagram here)*
+
+### 2.6 Cross-Cutting Concerns
+- **Authentication & Authorization:** JWT vs Session, Role-Based Access Control (RBAC).
+- **Error Handling:** Global error format, retry strategies.
+- **Observability:** Logging (Pino), metrics, tracing (trace_id).
+- **Security:** CSRF, XSS, rate limiting, secrets management.
+
+### 2.7 Deployment & Infrastructure
+- **Environments:** Dev, Staging, Prod.
+- **Hosting:** Vercel (FE) + Render (BE) vs Custom K8s cluster.
+- **CI/CD:** GitHub Actions (lint → test → build → deploy).
+
+### 2.8 Risks & Technical Debt
+- **Known bottlenecks:** "Search uses regex, will be slow at 100k records."
+- **Planned tech debt:** "Skipping Redis cache for MVP."
+- **Mitigation:** "Will migrate to Elasticsearch when hitting 50k users."
+
+---
+
+## 3. Component Diagram
+
+Use Mermaid for visualizing system boundaries:
+
+```mermaid
+graph TD
+    Client[Web Browser (React)]
+    API[Backend API (Node.js)]
+    DB[(Database (MongoDB))]
+    Ext[External API (Wix)]
+    Cache[(Cache (Redis))]
+
+    Client -- HTTPS --> API
+    API -- Mongoose --> DB
+    API -- REST --> Ext
+    API -- ioredis --> Cache
+```
+
+<br>
+
+*Rules for diagrams:*
+- Keep them simple (max 10-15 nodes).
+- Group related components (subgraphs).
+- Label connections with protocols (HTTPS, REST) or tools (Mongoose).
+
+---
+
+## 4. Data Flow (Sequence)
+
+Use Mermaid for critical flows:
+
+```mermaid
+sequenceDiagram
+    participant User
+    participant Client as Frontend (React)
+    participant API as Backend (Express)
+    participant DB as MongoDB
+
+    User->>Client: Clicks "Save Settings"
+    Client->>API: PUT /api/v1/settings (JWT)
+    activate API
+    API->>API: Validate Token & Body (Zod)
+    API->>DB: updateOne(settings)
+    DB-->>API: OK (updated)
+    API-->>Client: 200 OK { data: ... }
+    deactivate API
+    Client-->>User: Show Toast "Saved"
+```
+
+<br>
+
+*Rules for sequence diagrams:*
+- Show happy path + 1 major error path (if critical).
+- clearly show `activate`/`deactivate` blocks.
+- Label arrows with meaningful actions/endpoints.
+
+---
+
+## 5. Anti-patterns
+
+| ❌ Anti-pattern | ✅ Solution |
+|----------------|-----------|
+| **Too detailed** | Document high-level architecture, not every function. |
+| **No diagrams** | Text describes, diagrams visualize. Always use Mermaid. |
+| **Ignoring NFRs** | Explicitly mention performance, security, and scale constraints. |
+| **Orphaned document** | Link to PRD, UX Specs, ADRs, and API Contracts. |
+| **"We'll figure it out later"** | If undetermined, explicitly list as "Open Question" or "Risk". |
+
+---
+
+## 6. Output Template
+
+```markdown
+# Architecture Document: <Project Name>
+
+**Date:** YYYY-MM-DD
+**Version:** v1.0
+**Status:** Draft | Approved
+
+## 1. System Overview
+<Vision and NFR constraints>
+
+## 2. Component Architecture
+<Mermaid graph>
+- Web Client: ...
+- Backend API: ...
+- Database: ...
+
+## 3. Core Modules
+- Module A: ...
+- Module B: ...
+
+## 4. Key User Flows
+<Mermaid sequence diagram for primary flow>
+
+## 5. Data Architecture
+<High-level schema, storage, caching>
+
+## 6. Cross-Cutting Concerns
+- Auth: ...
+- Observability: ...
+- Error Handling: ...
+
+## 7. Deployment & Infrastructure
+<Hosting, CI/CD pipeline overview>
+
+## 8. Risks & Mitigations
+| Risk | Impact | Mitigation |
+|------|--------|------------|
+| ... | ... | ... |
+
+---
+**References:**
+- [PRD](./prd.md)
+- [ADR Index](./adr/README.md)
+- [API Contracts](./api-contracts.md)
+```
+
+---
+
+## See also
+- `$current_state_analysis` — before architecture changes
+- `$adr_log` — detailed architectural decisions
+- `$data_model` — complete DB schema
+- `$deployment_ci_plan` — specific execution plan

package/locales/en/.agents/skills/architecture_doc/agents/claude.json

@@ -0,0 +1,18 @@
+{
+  "name": "architecture_doc",
+  "display_name": "Architecture Document",
+  "description": "Architecture document from PRD and UX - modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan.",
+  "default_prompt": "Use $architecture_doc when the task matches the \"Architecture Document\" skill.",
+  "triggers": [
+    "architecture_doc",
+    "architecture doc",
+    "Architecture Document",
+    "Architecture document from PRD and UX - modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan"
+  ],
+  "capabilities": [
+    "architecture",
+    "doc"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/locales/en/.agents/skills/architecture_doc/agents/copilot.json

@@ -0,0 +1,18 @@
+{
+  "name": "architecture_doc",
+  "display_name": "Architecture Document",
+  "description": "Architecture document from PRD and UX - modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan.",
+  "default_prompt": "Use $architecture_doc when the task matches the \"Architecture Document\" skill.",
+  "triggers": [
+    "architecture_doc",
+    "architecture doc",
+    "Architecture Document",
+    "Architecture document from PRD and UX - modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan"
+  ],
+  "capabilities": [
+    "architecture",
+    "doc"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/locales/en/.agents/skills/architecture_doc/agents/gemini.json

@@ -0,0 +1,18 @@
+{
+  "name": "architecture_doc",
+  "display_name": "Architecture Document",
+  "description": "Architecture document from PRD and UX - modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan.",
+  "default_prompt": "Use $architecture_doc when the task matches the \"Architecture Document\" skill.",
+  "triggers": [
+    "architecture_doc",
+    "architecture doc",
+    "Architecture Document",
+    "Architecture document from PRD and UX - modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan"
+  ],
+  "capabilities": [
+    "architecture",
+    "doc"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/locales/en/.agents/skills/architecture_doc/agents/openai.yaml

@@ -0,0 +1,8 @@
+interface:
+  display_name: "Architecture Document"
+  short_description: "Architecture document from PRD and UX - modules, flows, data, integrations, errors, testability…"
+  default_prompt: "Use $architecture_doc when the task matches the \"Architecture Document\" skill."
+dependencies:
+  tools: []
+policy:
+  allow_implicit_invocation: true

package/locales/en/.agents/skills/architecture_doc/agents/qwen.json

@@ -0,0 +1,18 @@
+{
+  "name": "architecture_doc",
+  "display_name": "Architecture Document",
+  "description": "Architecture document from PRD and UX - modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan.",
+  "default_prompt": "Use $architecture_doc when the task matches the \"Architecture Document\" skill.",
+  "triggers": [
+    "architecture_doc",
+    "architecture doc",
+    "Architecture Document",
+    "Architecture document from PRD and UX - modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan"
+  ],
+  "capabilities": [
+    "architecture",
+    "doc"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/locales/en/.agents/skills/architecture_doc/agents/skill.yaml

@@ -0,0 +1,22 @@
+version: 1
+name: "architecture_doc"
+display_name: "Architecture Document"
+description: "Architecture document from PRD and UX - modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan."
+default_prompt: "Use $architecture_doc when the task matches the \"Architecture Document\" skill."
+triggers:
+  - "architecture_doc"
+  - "architecture doc"
+  - "Architecture Document"
+  - "Architecture document from PRD and UX - modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan"
+capabilities:
+  - "architecture"
+  - "doc"
+tools: []
+invocation:
+  explicit: true
+  implicit: true
+localization:
+  default_locale: "en"
+  available_locales:
+    - "ru"
+    - "en"

package/locales/en/.agents/skills/board/SKILL.md

@@ -0,0 +1,129 @@
+---
+name: board
+description: Project Board Management — creation of tasks with IDs, statuses ☐/⏳/☑/⚠️, updates after each step, visible checklist in every Conductor's message.
+---
+
+# Skill: Board & Task Management
+
+How the Conductor (Main Agent) manages the task board and tracks progress.
+
+**Sections:**
+1. [Core Principles](#1-principles)
+2. [Task Statuses](#2-statuses)
+3. [Board Structure](#3-structure)
+4. [Updating the Board](#4-updating)
+5. [Conductor's Message Format](#5-message-format)
+6. [Anti-patterns](#6-anti-patterns)
+
+---
+
+## 1. Core Principles
+
+- **Visibility:** The board MUST be visible in every message from the Conductor.
+- **Traceability:** Every task has a unique ID (e.g., `T-01`, `BUG-42`).
+- **Granularity:** Tasks should be small enough to complete in 1-2 agent interactions.
+- **Single Source of Truth:** If it's not on the board, it doesn't exist.
+- **Handoff Linking:** When handing off to an agent, reference the Task ID.
+
+---
+
+## 2. Task Statuses
+
+Use exactly these symbols for quick visual parsing:
+
+| Symbol | Status | Meaning |
+|:---:|---|---|
+| `☐` | **TODO** | Task identified, not started yet. |
+| `⏳` | **IN PROGRESS** | Agent is currently working on it. |
+| `☑` | **DONE** | Validated and completed (DoD met). |
+| `⚠️` | **BLOCKED** | Needs user input, clarification, or depends on another blocked task. |
+| `❌` | **CANCELED** | Won't do, out of scope, or obsolete. |
+
+---
+
+## 3. Board Structure
+
+The board is a markdown checklist grouped by Epic or Phase.
+
+### Typical Layout
+
+```markdown
+## 📋 Project Board
+
+### Phase 1: Planning & Design (Gate 1 & 2)
+- ☑ [T-01] Gather Requirements (PM)
+- ☑ [T-02] Draft PRD (PM)
+- ⏳ [T-03] Create UX Spec (UX Designer) - *Waiting for review*
+- ☐ [T-04] Architecture Document (Architect)
+- ☐ [T-05] API Contracts (Architect)
+
+### Phase 2: Implementation (Gate 3)
+- ☐ [T-06] DB Schema Setup (Senior Full Stack)
+- ☐ [T-07] Build Login Flow (Senior Full Stack)
+...
+```
+
+---
+
+## 4. Updating the Board
+
+### When to update
+
+1. **New Request:** Parse user request into `T-xx` items. Add them as `☐`.
+2. **Before Handoff:** Change target task to `⏳`.
+3. **After Handoff (Success):** Change task to `☑`.
+4. **After Handoff (Failure/Bug):** Change to `⚠️` or spawn a new `[BUG-xx]` item.
+5. **Phase Complete:** Collapse completed phases or summarize them if the board gets too long.
+
+### Spawning subtasks
+
+If a task `T-06 (Build Login Flow)` turns out to be complex, break it down:
+
+```markdown
+- ⏳ [T-06] Build Login Flow
+  - ☑ [T-06.1] Setup JWT middleware
+  - ⏳ [T-06.2] Create `/login` endpoint
+  - ☐ [T-06.3] Frontend Login form
+```
+
+---
+
+## 5. Conductor's Message Format
+
+Every response from the Conductor to the User MUST follow this structure:
+
+```markdown
+# 🎭 Conductor
+
+**Status Update:** <1-2 sentences summarizing what just happened>
+
+<Answer to user / Recommendations / Next Steps>
+
+---
+## 📋 Current Board
+- ☑ [T-01] Initial setup
+- ⏳ [T-02] Implementing Feature X (Full Stack doing this now)
+- ☐ [T-03] Testing
+- ⚠️ [T-04] Clarify API rate limits (need User input)
+
+**Next action:** Handoff T-02 to Senior Full Stack. Do you approve?
+```
+
+---
+
+## 6. Anti-patterns
+
+| ❌ Anti-pattern | ✅ Solution |
+|----------------|-----------|
+| **Forgetting the board** | Conductor replies with just text. The user loses context. ALWAYS include the board. |
+| **Tasks without IDs** | "Fix login bug". Hard to reference. Use `[BUG-01] Fix login bug`. |
+| **Vague statuses** | Using "Pending" or mixed symbols. Stick to `☐, ⏳, ☑, ⚠️, ❌`. |
+| **Silent updates** | Changing a task from `⏳` to `☑` without explaining *how* it was validated. |
+| **Mega-tasks** | `☐ [T-01] Build the entire app`. Break it down. |
+
+---
+
+## See also
+- `$handoff` — How to pass a task to another agent.
+- `$gates` — How phases map to pipeline gates.
+- `$pm_backlog` — How the PM originally creates the list of tasks.

package/locales/en/.agents/skills/board/agents/claude.json

@@ -0,0 +1,16 @@
+{
+  "name": "board",
+  "display_name": "Project Board",
+  "description": "Manage the Project Board - create task IDs, maintain statuses, update progress after each step, and keep a visible checklist in every conductor message.",
+  "default_prompt": "Use $board when the task matches the \"Project Board\" skill.",
+  "triggers": [
+    "board",
+    "Project Board",
+    "Manage the Project Board - create task IDs, maintain statuses, update progress after each step, and keep a visible checklist in every conductor message"
+  ],
+  "capabilities": [
+    "board"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/locales/en/.agents/skills/board/agents/copilot.json

@@ -0,0 +1,16 @@
+{
+  "name": "board",
+  "display_name": "Project Board",
+  "description": "Manage the Project Board - create task IDs, maintain statuses, update progress after each step, and keep a visible checklist in every conductor message.",
+  "default_prompt": "Use $board when the task matches the \"Project Board\" skill.",
+  "triggers": [
+    "board",
+    "Project Board",
+    "Manage the Project Board - create task IDs, maintain statuses, update progress after each step, and keep a visible checklist in every conductor message"
+  ],
+  "capabilities": [
+    "board"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/locales/en/.agents/skills/board/agents/gemini.json

@@ -0,0 +1,16 @@
+{
+  "name": "board",
+  "display_name": "Project Board",
+  "description": "Manage the Project Board - create task IDs, maintain statuses, update progress after each step, and keep a visible checklist in every conductor message.",
+  "default_prompt": "Use $board when the task matches the \"Project Board\" skill.",
+  "triggers": [
+    "board",
+    "Project Board",
+    "Manage the Project Board - create task IDs, maintain statuses, update progress after each step, and keep a visible checklist in every conductor message"
+  ],
+  "capabilities": [
+    "board"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/locales/en/.agents/skills/board/agents/openai.yaml

@@ -0,0 +1,8 @@
+interface:
+  display_name: "Project Board"
+  short_description: "Manage the Project Board - create task IDs, maintain statuses, update progress after each step,…"
+  default_prompt: "Use $board when the task matches the \"Project Board\" skill."
+dependencies:
+  tools: []
+policy:
+  allow_implicit_invocation: true

package/locales/en/.agents/skills/board/agents/qwen.json

@@ -0,0 +1,16 @@
+{
+  "name": "board",
+  "display_name": "Project Board",
+  "description": "Manage the Project Board - create task IDs, maintain statuses, update progress after each step, and keep a visible checklist in every conductor message.",
+  "default_prompt": "Use $board when the task matches the \"Project Board\" skill.",
+  "triggers": [
+    "board",
+    "Project Board",
+    "Manage the Project Board - create task IDs, maintain statuses, update progress after each step, and keep a visible checklist in every conductor message"
+  ],
+  "capabilities": [
+    "board"
+  ],
+  "tools": [],
+  "implicit_invocation": true
+}

package/locales/en/.agents/skills/board/agents/skill.yaml

@@ -0,0 +1,20 @@
+version: 1
+name: "board"
+display_name: "Project Board"
+description: "Manage the Project Board - create task IDs, maintain statuses, update progress after each step, and keep a visible checklist in every conductor message."
+default_prompt: "Use $board when the task matches the \"Project Board\" skill."
+triggers:
+  - "board"
+  - "Project Board"
+  - "Manage the Project Board - create task IDs, maintain statuses, update progress after each step, and keep a visible checklist in every conductor message"
+capabilities:
+  - "board"
+tools: []
+invocation:
+  explicit: true
+  implicit: true
+localization:
+  default_locale: "en"
+  available_locales:
+    - "ru"
+    - "en"