code-ai-installer 1.3.0 → 1.4.0

package/locales/en/.agents/styling_css_stack/agents/copilot.json

@@ -1,19 +0,0 @@
-{
-  "name": "styling_css_stack",
-  "display_name": "Styling (CSS Stack) Beast Practices",
-  "description": "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors). DO/DON'T examples. Activate with writing or review CSS/Less/Sass, with refactoring styles, or with questions «how correctly style X».",
-  "default_prompt": "Use $styling_css_stack when the task matches the \"Styling (CSS Stack) Beast Practices\" skill.",
-  "triggers": [
-    "styling_css_stack",
-    "styling css stack",
-    "Styling (CSS Stack) Beast Practices",
-    "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors)"
-  ],
-  "capabilities": [
-    "styling",
-    "css",
-    "stack"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/styling_css_stack/agents/gemini.json

@@ -1,19 +0,0 @@
-{
-  "name": "styling_css_stack",
-  "display_name": "Styling (CSS Stack) Beast Practices",
-  "description": "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors). DO/DON'T examples. Activate with writing or review CSS/Less/Sass, with refactoring styles, or with questions «how correctly style X».",
-  "default_prompt": "Use $styling_css_stack when the task matches the \"Styling (CSS Stack) Beast Practices\" skill.",
-  "triggers": [
-    "styling_css_stack",
-    "styling css stack",
-    "Styling (CSS Stack) Beast Practices",
-    "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors)"
-  ],
-  "capabilities": [
-    "styling",
-    "css",
-    "stack"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/styling_css_stack/agents/openai.yaml

@@ -1,8 +0,0 @@
-interface:
-  display_name: "Styling (CSS Stack) Beast Practices"
-  short_description: "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, tran…"
-  default_prompt: "Use $styling_css_stack when the task matches the \"Styling (CSS Stack) Beast Practices\" skill."
-dependencies:
-  tools: []
-policy:
-  allow_implicit_invocation: true

package/locales/en/.agents/styling_css_stack/agents/qwen.json

@@ -1,19 +0,0 @@
-{
-  "name": "styling_css_stack",
-  "display_name": "Styling (CSS Stack) Beast Practices",
-  "description": "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors). DO/DON'T examples. Activate with writing or review CSS/Less/Sass, with refactoring styles, or with questions «how correctly style X».",
-  "default_prompt": "Use $styling_css_stack when the task matches the \"Styling (CSS Stack) Beast Practices\" skill.",
-  "triggers": [
-    "styling_css_stack",
-    "styling css stack",
-    "Styling (CSS Stack) Beast Practices",
-    "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors)"
-  ],
-  "capabilities": [
-    "styling",
-    "css",
-    "stack"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/styling_css_stack/agents/skill.yaml

@@ -1,23 +0,0 @@
-version: 1
-name: "styling_css_stack"
-display_name: "Styling (CSS Stack) Beast Practices"
-description: "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors). DO/DON'T examples. Activate with writing or review CSS/Less/Sass, with refactoring styles, or with questions «how correctly style X»."
-default_prompt: "Use $styling_css_stack when the task matches the \"Styling (CSS Stack) Beast Practices\" skill."
-triggers:
-  - "styling_css_stack"
-  - "styling css stack"
-  - "Styling (CSS Stack) Beast Practices"
-  - "CSS practices — custom properties (design tokens), naming (BEM / CSS Modules), responsive, transitions, z-index scale, dark mode, a11y (focus-visible, prefers-reduced-motion, forced-colors)"
-capabilities:
-  - "styling"
-  - "css"
-  - "stack"
-tools: []
-invocation:
-  explicit: true
-  implicit: true
-localization:
-  default_locale: "en"
-  available_locales:
-    - "ru"
-    - "en"

package/locales/en/.agents/system_design_checklist/SKILL.md

@@ -1,207 +0,0 @@
----
-name: system_design_checklist
-description: Checklist system design — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), so that nothing not forget.
----
-
-# Skill: System Design Checklist
-
-Self-checking of the completeness of the architecture before transfer to development.
-
-**Sections:**
-1. [Functional Requirements](#1-functional-requirements)
-2. [Non-Functional Requirements](#2-nfr)
-3. [Technical Design](#3-technical-design)
-4. [Data Layer](#4-data-layer)
-5. [Security](#5-security)
-6. [Operations](#6-operations)
-7. [Red Flags](#7-red-flags)
-8. [Output Template](#8-output)
-
----
-
-## 1. Functional Requirements
-
-| # | Check | Guidance | Status |
-|---|-------|---------|--------|
-| 1.1 | User stories documented | Format: "As a [user], I want [action], so that [value]". Minimum for MVP scope | ☐ |
-| 1.2 | UI/UX flows mapped | Each screen → actions → outcomes. Including loading/error/empty states | ☐ |
-| 1.3 | API contracts defined | Endpoints, methods, request/response schemas, status codes. Format: OpenAPI or markdown table | ☐ |
-| 1.4 | Data models defined | Entities, relationships, constraints. Format: ER diagram (mermaid) or schema definitions | ☐ |
-| 1.5 | Edge cases covered | What if: empty data, concurrent updates, partial failures, expired tokens | ☐ |
-
-### Example PASS
-
-```
-1.3 API contracts: ✅ PASS
-  POST /api/v1/coupons — CreateCouponRequest → CouponResponse (201)
-  GET /api/v1/coupons/:id — → CouponResponse (200) | ErrorResponse (404)
-  Schemas defined in docs/api-contracts.md
-```
-
-### Example MISSING
-
-```
-1.5 Edge cases: ❌ MISSING
-  Behavior is not defined for:
-  - Concurrent update settings (optimistic locking?)
-  - Expired coupon on storefront (show expired or hide?)
-  → Recommendation: add acceptance criteria in PRD
-  → Task: ARCH-05
-```
-
----
-
-## 2. Non-Functional Requirements
-
-| # | Check | Guidance | Status |
-|---|-------|---------|--------|
-| 2.1 | Performance targets | p95 latency ≤ X ms, throughput ≥ Y rps. For each critical endpoint | ☐ |
-| 2.2 | Scalability | Expected load (users, requests, data volume). Growth plan (x10, x100) | ☐ |
-| 2.3 | Availability | Uptime target (99.9%?). Allowed downtime. Graceful degradation strategy | ☐ |
-| 2.4 | Security | Auth/authz model, data classification, compliance requirements (GDPR, PCI) | ☐ |
-| 2.5 | Observability | Logging, metrics, alerting, tracing requirements | ☐ |
-
-### Guidance: Performance targets
-
-```markdown
-## Performance Targets
-
-| Endpoint | p50 | p95 | p99 | Max concurrent |
-|----------|-----|-----|-----|----------------|
-| GET /api/v1/widget/:id | 50ms | 100ms | 200ms | 100 |
-| POST /api/v1/settings | 100ms | 200ms | 500ms | 20 |
-| Dashboard page load | 1s | 2s | 3s | 50 |
-
-Measurement: response time from gateway, without network latency.
-```
-
----
-
-## 3. Technical Design
-
-| # | Check | Guidance | Status |
-|---|-------|---------|--------|
-| 3.1 | Architecture diagram | Text (mermaid/ASCII). Shows: components, flows data, boundaries | ☐ |
-| 3.2 | Component responsibilities | For each: what does, what Not does, public API, dependencies | ☐ |
-| 3.3 | Data flow | Request path: client → gateway → API → service → repo → DB → response | ☐ |
-| 3.4 | Integration points | External systems (Wix API, payment, email). Retry/timeout/circuit breaker strategy | ☐ |
-| 3.5 | Error handling | Unified format errors. Mapping: domain errors → HTTP codes → UI messages | ☐ |
-| 3.6 | Testing strategy | Unit/integration/e2e boundaries. Coverage targets. What to mock | ☐ |
-
-### Example: Architecture diagram (mermaid)
-
-```mermaid
-graph LR
-    A[Browser] -->|HTTPS| B[Caddy Gateway :5173]
-    B -->|/dashboard| C[React SPA :3001]
-    B -->|/api| D[Express API :3000]
-    B -->|/widget| E[Static Files]
-    D --> F[(MongoDB :27017)]
-    D -->|OAuth| G[Wix API]
-    E -->|fetch config| D
-```
-
-### Example: Error handling table
-
-| Domain Error | HTTP Code | UI Message | Log Level |
-|-------------|-----------|-----------|-----------|
-| ValidationError | 400 | "Check your input" + field details | warn |
-| NotFoundError | 404 | "Not found" | info |
-| DuplicateError | 409 | "Already exists" | warn |
-| AuthError | 401 | "Please log in" | warn |
-| InternalError | 500 | "Something went wrong" | error |
-
----
-
-## 4. Data Layer
-
-| # | Check | Guidance | Status |
-|---|-------|---------|--------|
-| 4.1 | Schema definitions | Mongoose schemas with validators, defaults, timestamps | ☐ |
-| 4.2 | Embed vs Reference | Intentional choice, documented in ADR | ☐ |
-| 4.3 | Indexes | Compound indexes under key query patterns. Verified via explain() | ☐ |
-| 4.4 | Pagination | Cursor for large collections, skip for small | ☐ |
-| 4.5 | Migrations | migrate-mongo or analogue. Backfill strategy for schema changes | ☐ |
-
----
-
-## 5. Security
-
-| # | Check | Guidance | Status |
-|---|-------|---------|--------|
-| 5.1 | Input validation | Zod schemas on each endpoint. Whitelist approach | ☐ |
-| 5.2 | Auth/Authz | JWT/session strategy. Authorization before data access | ☐ |
-| 5.3 | Secrets management | Env vars only. .env.example without values. gitignore | ☐ |
-| 5.4 | Secure headers | Helmet, CORS whitelist, CSP | ☐ |
-| 5.5 | Dependency audit | `npm audit`, lockfile committed, no known vulnerabilities | ☐ |
-
----
-
-## 6. Operations
-
-| # | Check | Guidance | Status |
-|---|-------|---------|--------|
-| 6.1 | Deployment | Docker Compose / K8s. Build → test → deploy pipeline | ☐ |
-| 6.2 | Health checks | `/health/live` + `/health/ready` endpoints | ☐ |
-| 6.3 | Monitoring | Structured logs (pino). Key metrics: latency, error rate, throughput | ☐ |
-| 6.4 | Alerting | Error rate > X% → alert. p95 latency > Yms → alert | ☐ |
-| 6.5 | Backup/Recovery | DB backup strategy. RPO/RTO defined | ☐ |
-| 6.6 | Rollback plan | How to roll back: previous Docker image, DB migration down, feature flag | ☐ |
-
----
-
-## 7. Red Flags
-
-| # | Flag | What this | How to detect |
-|---|------|---------|---------------|
-| 7.1 | Big Ball of Mud | No clear architecture, everything is connected to everything | No layers, circular deps |
-| 7.2 | God Object | One file/class does everything | File > 500 lines, > 10 methods |
-| 7.3 | Tight Coupling | Change one module breaks other | No interfaces/contracts between layers |
-| 7.4 | Magic | Non-obvious behavior without documentation | Mongoose hooks with business logic, implicit globals |
-| 7.5 | Analysis Paralysis | Endless planning | No MVP paths, 3+ alternatives without decisions |
-| 7.6 | Premature Optimization | Optimization without data | Cache/sharding before the first user |
-| 7.7 | Not Invented Here | Refusal of ready-made solutions | Custom auth, custom ORM, custom logger |
-
----
-
-## 8. Output
-
-```markdown
-# System Design Checklist: <feature/project>
-
-**Date:** YYYY-MM-DD
-**Reviewer:** Architect Agent
-
-## Results
-
-| Section | Pass | Missing | Total |
-|---------|------|---------|-------|
-| Functional | 4 | 1 | 5 |
-| NFR | 3 | 2 | 5 |
-| Technical | 5 | 1 | 6 |
-| Data | 4 | 1 | 5 |
-| Security | 5 | 0 | 5 |
-| Operations | 4 | 2 | 6 |
-| Red Flags | 6 | 1 | 7 |
-| **Total** | **31** | **8** | **39** |
-
-## Missing Items
-
-| # | Check | Severity | Recommendation | Task |
-|---|-------|----------|----------------|------|
-| 2.1 | Performance targets | 🟠 P1 | Define p95 targets for critical endpoints | ARCH-12 |
-| 6.4 | Alerting | 🟡 P2 | Set up basic alerts after MVP | ARCH-15 |
-
-## Verdict
-✅ READY for development (with noted ARCH-xx items tracked)
-⚠️ CONDITIONAL — must address P0/P1 items before dev
-❌ NOT READY — significant gaps in <section>
-```
-
----
-
-## See also
-- `$current_state_analysis` — audit current states (before this checklist)
-- `$architecture_doc` — full Architecture Document (after checklist)
-- `$adr_log` — recording decisions
-- `$security_baseline_dev` — detail security check

package/locales/en/.agents/system_design_checklist/agents/claude.json

@@ -1,18 +0,0 @@
-{
-  "name": "system_design_checklist",
-  "display_name": "System Design Checklist",
-  "description": "Checklist system design — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), so that nothing not forget.",
-  "default_prompt": "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill.",
-  "triggers": [
-    "system_design_checklist",
-    "system design checklist",
-    "Checklist system design — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), so that nothing not forget"
-  ],
-  "capabilities": [
-    "system",
-    "design",
-    "checklist"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/system_design_checklist/agents/copilot.json

@@ -1,18 +0,0 @@
-{
-  "name": "system_design_checklist",
-  "display_name": "System Design Checklist",
-  "description": "Checklist system design — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), so that nothing not forget.",
-  "default_prompt": "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill.",
-  "triggers": [
-    "system_design_checklist",
-    "system design checklist",
-    "Checklist system design — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), so that nothing not forget"
-  ],
-  "capabilities": [
-    "system",
-    "design",
-    "checklist"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/system_design_checklist/agents/gemini.json

@@ -1,18 +0,0 @@
-{
-  "name": "system_design_checklist",
-  "display_name": "System Design Checklist",
-  "description": "Checklist system design — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), so that nothing not forget.",
-  "default_prompt": "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill.",
-  "triggers": [
-    "system_design_checklist",
-    "system design checklist",
-    "Checklist system design — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), so that nothing not forget"
-  ],
-  "capabilities": [
-    "system",
-    "design",
-    "checklist"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/system_design_checklist/agents/openai.yaml

@@ -1,8 +0,0 @@
-interface:
-  display_name: "System Design Checklist"
-  short_description: "Checklist system design — functional/non-functional requirements, technical design, operations…"
-  default_prompt: "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill."
-dependencies:
-  tools: []
-policy:
-  allow_implicit_invocation: true

package/locales/en/.agents/system_design_checklist/agents/qwen.json

@@ -1,18 +0,0 @@
-{
-  "name": "system_design_checklist",
-  "display_name": "System Design Checklist",
-  "description": "Checklist system design — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), so that nothing not forget.",
-  "default_prompt": "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill.",
-  "triggers": [
-    "system_design_checklist",
-    "system design checklist",
-    "Checklist system design — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), so that nothing not forget"
-  ],
-  "capabilities": [
-    "system",
-    "design",
-    "checklist"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/system_design_checklist/agents/skill.yaml

@@ -1,22 +0,0 @@
-version: 1
-name: "system_design_checklist"
-display_name: "System Design Checklist"
-description: "Checklist system design — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), so that nothing not forget."
-default_prompt: "Use $system_design_checklist when the task matches the \"System Design Checklist\" skill."
-triggers:
-  - "system_design_checklist"
-  - "system design checklist"
-  - "Checklist system design — functional/non-functional requirements, technical design, operations (deploy/monitoring/backup/rollback), so that nothing not forget"
-capabilities:
-  - "system"
-  - "design"
-  - "checklist"
-tools: []
-invocation:
-  explicit: true
-  implicit: true
-localization:
-  default_locale: "en"
-  available_locales:
-    - "ru"
-    - "en"