code-ai-installer 1.2.0 → 1.3.1

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

@@ -1,13 +1,13 @@
 {
   "name": "ui_inventory",
   "display_name": "UI Components Inventory",
-  "description": "Compile an inventory of UI components and rules for reuse: basic components, compositional components, patterns (forms, tables, dialogs), design tokens (minimum).",
+  "description": "Compose an inventory of UI components and reuse rules — basic components, composite components, patterns (forms, tables, dialogs), design (minimum).",
   "default_prompt": "Use $ui_inventory when the task matches the \"UI Components Inventory\" skill.",
   "triggers": [
     "ui_inventory",
     "ui inventory",
     "UI Components Inventory",
-    "Compile an inventory of UI components and rules for reuse"
+    "Compose an inventory of UI components and reuse rules — basic components, composite components, patterns (forms, tables, dialogs), design (minimum)"
   ],
   "capabilities": [
     "ui",

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

@@ -1,13 +1,13 @@
 {
   "name": "ui_inventory",
   "display_name": "UI Components Inventory",
-  "description": "Compile an inventory of UI components and rules for reuse: basic components, compositional components, patterns (forms, tables, dialogs), design tokens (minimum).",
+  "description": "Compose an inventory of UI components and reuse rules — basic components, composite components, patterns (forms, tables, dialogs), design (minimum).",
   "default_prompt": "Use $ui_inventory when the task matches the \"UI Components Inventory\" skill.",
   "triggers": [
     "ui_inventory",
     "ui inventory",
     "UI Components Inventory",
-    "Compile an inventory of UI components and rules for reuse"
+    "Compose an inventory of UI components and reuse rules — basic components, composite components, patterns (forms, tables, dialogs), design (minimum)"
   ],
   "capabilities": [
     "ui",

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

@@ -1,6 +1,6 @@
 interface:
   display_name: "UI Components Inventory"
-  short_description: "Compile an inventory of UI components and rules for reuse: basic components, compositional comp…"
+  short_description: "Compose an inventory of UI components and reuse rules — basic components, composite components,…"
   default_prompt: "Use $ui_inventory when the task matches the \"UI Components Inventory\" skill."
 dependencies:
   tools: []

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

@@ -1,13 +1,13 @@
 {
   "name": "ui_inventory",
   "display_name": "UI Components Inventory",
-  "description": "Compile an inventory of UI components and rules for reuse: basic components, compositional components, patterns (forms, tables, dialogs), design tokens (minimum).",
+  "description": "Compose an inventory of UI components and reuse rules — basic components, composite components, patterns (forms, tables, dialogs), design (minimum).",
   "default_prompt": "Use $ui_inventory when the task matches the \"UI Components Inventory\" skill.",
   "triggers": [
     "ui_inventory",
     "ui inventory",
     "UI Components Inventory",
-    "Compile an inventory of UI components and rules for reuse"
+    "Compose an inventory of UI components and reuse rules — basic components, composite components, patterns (forms, tables, dialogs), design (minimum)"
   ],
   "capabilities": [
     "ui",

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

@@ -1,13 +1,13 @@
 version: 1
 name: "ui_inventory"
 display_name: "UI Components Inventory"
-description: "Compile an inventory of UI components and rules for reuse: basic components, compositional components, patterns (forms, tables, dialogs), design tokens (minimum)."
+description: "Compose an inventory of UI components and reuse rules — basic components, composite components, patterns (forms, tables, dialogs), design (minimum)."
 default_prompt: "Use $ui_inventory when the task matches the \"UI Components Inventory\" skill."
 triggers:
   - "ui_inventory"
   - "ui inventory"
   - "UI Components Inventory"
-  - "Compile an inventory of UI components and rules for reuse"
+  - "Compose an inventory of UI components and reuse rules — basic components, composite components, patterns (forms, tables, dialogs), design (minimum)"
 capabilities:
   - "ui"
   - "inventory"

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

@@ -1,48 +1,214 @@
 ---
 name: ux_discovery
-description: Clarify UX introductory to PRD: roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases.
+description: Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/references, localization, edge cases.
 ---
 
 # Skill: UX Discovery
 
-## Target
-Collect the missing UX context before creating the UX Spec.
+Collect the missing UX context before the UX Spec.
 
-## When to use
-- Immediately after receiving the PRD
-- When requirements/roles/flows change
+**Sections:**
+1. [Workflow](#1-workflow)
+2. [Question Bank](#2-questions)
+3. [Priority Matrix](#3-priority)
+4. [Assumptions Framework](#4-assumptions)
+5. [Example: Smart Cart Rescue](#5-example)
+6. [Output Template](#6-output)
 
-## Exit
-- List of clarifying questions (5–15), sorted by criticality
-- Assumptions, if you can’t move without them
-- Draft list of screens/streams
+---
+
+## 1. Workflow
+
+```
+1. Read PRD (from $pm_prd)
+   └── Highlight: goals, user stories, acceptance criteria, constraints
+
+2. Check: what already known vs what needed clarify
+   ├── Known → mark as fact
+   └── Unknown → add in list questions
+
+3. Prioritize questions (section 3):
+   ├── 🔴 Blocking: without answer cannot choose approach
+   ├── 🟠 Important: affects on UX Spec, but can assume
+   └── 🟡 Nice-to-know: useful, but not critical
+
+4. If response critical → ask question to the user
+   If can assume → record assumption + mark "ASSUMPTION"
+
+5. Form Discovery Report (section 6)
+
+6. Pass in → $ux_spec
+```
+
+### When Not needed discovery
+
+| Situation | Action |
+|----------|---------|
+| PRD already contains all responses | Skip discovery → immediately $ux_spec |
+| Iteration over existing UI | Minimum discovery (only new questions) |
+| Bugfix / hotfix | Not needed |
+
+---
+
+## 2. Question Bank
 
-## Questions (ask relevant ones)
-### Platform and layout
-- Is it desktop-first, mobile-first or equivalent to responsive?
-- Key breakpoints/minimum sizes?
+### A) Platform and layout
 
-### Roles and rights
-- What are the user roles? What is prohibited for each role?
-- Do you need admin/moderation?
+| # | Question | Why |
+|---|--------|-------|
+| Q-01 | Desktop-first, mobile-first or responsive? | Defines breakpoints and layout strategy |
+| Q-02 | Minimal support resolutions? | Affects on grid and responsive rules |
+| Q-03 | Is embedded in iframe or standalone? | Critical for dimensions, scrolling, navigation |
+| Q-04 | There is whether dark mode / theme switching? | Affects on design tokens and CSS strategy |
+
+### B) Roles and permissions
+
+| # | Question | Why |
+|---|--------|-------|
+| Q-05 | Which roles users? | Defines navigation and permissions logic |
+| Q-06 | What each role can / cannot do? | Affects on UI visibility and server-side auth |
+| Q-07 | Needed whether admin panel / moderation? | Can require separate layout |
+| Q-08 | There is whether onboarding for new users? | Additional screens/flow |
+
+### C) Navigation and structure
+
+| # | Question | Why |
+|---|--------|-------|
+| Q-09 | Main sections / tabs / pages? | Defines IA (Information Architecture) |
+| Q-10 | There is whether deep linking (URL sharing)? | Affects on routing strategy |
+| Q-11 | Breadcrumbs / back navigation needed? | UX navigation pattern |
+| Q-12 | Single page or multi-page? | Routing, state management |
+
+### D) brand and visuals
+
+| # | Question | Why |
+|---|--------|-------|
+| Q-13 | There is whether Figma / mockup / design system? | Defines «source truth» by UI |
+| Q-14 | There is visual references / inspiration? | Direction for design |
+| Q-15 | Logo / brand colors / fonts? | Brand compliance |
+| Q-16 | Dark / light theme? | Design tokens scope |
+
+### E) Data and states
+
+| # | Question | Why |
+|---|--------|-------|
+| Q-17 | What show with empty data? | Empty state design |
+| Q-18 | Which operations potentially long-running? | Loading/skeleton strategy |
+| Q-19 | What do we do with network/server errors? | Error state design |
+| Q-20 | There is whether real-time updates? | WebSocket / polling strategy |
+| Q-21 | Maximum data volumes (lists/tables)? | Pagination/virtualization |
+
+### F) Localization and i18n
+
+| # | Question | Why |
+|---|--------|-------|
+| Q-22 | One language or several? | i18n setup |
+| Q-23 | RTL support? | CSS direction strategy |
+| Q-24 | Format dates / time / currencies? | Locale-specific formatting |
+
+---
 
-### Navigation and structure
-- What are the main sections?
-- Is there deep linking/link sharing?
+## 3. Priority Matrix
 
-### Brand/visual expectations
-- Is there a design system/references?
-- If not, do we use a “system UI” (for example, standard patterns of the selected framework)?
+| Priority | Meaning | Action |
+|----------|---------|--------|
+| 🔴 **Blocking** | Without answer cannot start the UX Spec | Mandatory ask user |
+| 🟠 **Important** | Affects on UX, but can make an assumption | Ask or record ASSUMPTION |
+| 🟡 **Nice-to-know** | useful for polish, not for MVP | Postpone or assume |
 
-### Localization
-- One language or several?
-- Date/time/currency formats?
+### Type prioritization
 
-### UX edge cases
-- What do we show if the data is empty?
-- What do we do in case of network/validation errors?
-- Which operations are potentially long (need progress/skeletons)?
+| Category | Typical priority |
+|-----------|:------------------:|
+| Platform (iframe / responsive) | 🔴 |
+| Roles & permissions | 🔴 |
+| Navigation / IA | 🟠 |
+| Brand / design system | 🟠 |
+| Empty / error states | 🟠 |
+| Localization | 🟡 |
+| Real-time updates | 🟡 |
+
+---
+
+## 4. Assumptions Framework
+
+When no answer, record assumption:
+
+```markdown
+### ASSUMPTION-01: Desktop-first layout
+**Question:** Q-01 — responsive strategy
+**Assumption:** Desktop-first, min-width 1024px
+**Rationale:** PRD describes dashboard, typical use case — desktop
+**Risk:** Low — easily add mobile breakpoints later
+**need confirm:** To v1.0
+```
+
+---
+
+## 5. Example: Smart Cart Rescue
+
+```markdown
+# UX Discovery: Smart Cart Rescue Dashboard
+
+## Facts from PRD
+- Wix App — is embedded via iframe
+- Dashboard for settings popup-widgets
+- Roles: Site Owner (single role)
+- Templates: Glassmorphism, Neo-Brutalism, Minimal
+
+## Clarified
+- Q-03: iframe inside Wix Editor/Business Manager → 🔴 confirmed
+- Q-13: Design system — WDS (Wix Design System) → 🟠 confirmed
+- Q-17: Empty state — show "Create your first coupon" CTA → 🟠 confirmed
+
+## Assumptions
+- ASSUMPTION-01: Desktop-only (iframe in Wix Editor = desktop) → Low risk
+- ASSUMPTION-02: One language (english) for MVP → Low risk
+- ASSUMPTION-03: No real-time updates (static config) → Low risk
+```
+
+---
+
+## 6. Output Template
+
+```markdown
+# UX Discovery Report
+
+**PRD:** <reference>
+**Date:** YYYY-MM-DD
+**Author:** UX/UI Designer Agent
+
+## Facts (confirmed from PRD)
+| # | Fact | Source |
+|---|------|--------|
+| F-01 | Desktop-first, iframe in Wix | PRD §1 |
+| F-02 | Single role: Site Owner | PRD §2.1 |
+
+## Questions
+| # | Question | Priority | Answer | Status |
+|---|----------|:--------:|--------|:------:|
+| Q-01 | Responsive or desktop only? | 🔴 | Desktop only (iframe) | ✅ Answered |
+| Q-13 | Design system? | 🟠 | WDS (Wix Design System) | ✅ Answered |
+| Q-20 | Real-time? | 🟡 | — | ASSUMED: No |
+
+## Assumptions
+| ID | Assumption | Risk | Confirm by |
+|----|-----------|:----:|-----------|
+| ASSUMPTION-01 | Desktop only | Low | v1.0 |
+| ASSUMPTION-02 | English only | Low | v1.0 |
+
+## Screen / Flow Inventory (draft)
+1. Dashboard → Settings (tabs: General, Design, Timer, Coupon)
+2. Dashboard → Coupons list (CRUD)
+3. Widget → Public popup (end-user facing)
+
+## Next Step
+→ Proceed to $ux_spec with confirmed facts + assumptions
+```
+
+---
 
-## Rule
-If the answer is critical for the architecture/routing/API, be sure to clarify.
-If you can move forward with a safe assumption, make the assumption and celebrate.
+## See also
+- `$pm_prd` — PRD (input for discovery)
+- `$ux_spec` — UX Spec (output of discovery)
+- `$design_intake` — design materials analysis

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

@@ -1,12 +1,12 @@
 {
   "name": "ux_discovery",
   "display_name": "UX Discovery",
-  "description": "Clarify UX introductory to PRD: roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases.",
+  "description": "Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/references, localization, edge cases.",
   "default_prompt": "Use $ux_discovery when the task matches the \"UX Discovery\" skill.",
   "triggers": [
     "ux_discovery",
     "ux discovery",
-    "Clarify UX introductory to PRD"
+    "Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/references, localization, edge cases"
   ],
   "capabilities": [
     "ux",

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

@@ -1,12 +1,12 @@
 {
   "name": "ux_discovery",
   "display_name": "UX Discovery",
-  "description": "Clarify UX introductory to PRD: roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases.",
+  "description": "Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/references, localization, edge cases.",
   "default_prompt": "Use $ux_discovery when the task matches the \"UX Discovery\" skill.",
   "triggers": [
     "ux_discovery",
     "ux discovery",
-    "Clarify UX introductory to PRD"
+    "Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/references, localization, edge cases"
   ],
   "capabilities": [
     "ux",

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

@@ -1,12 +1,12 @@
 {
   "name": "ux_discovery",
   "display_name": "UX Discovery",
-  "description": "Clarify UX introductory to PRD: roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases.",
+  "description": "Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/references, localization, edge cases.",
   "default_prompt": "Use $ux_discovery when the task matches the \"UX Discovery\" skill.",
   "triggers": [
     "ux_discovery",
     "ux discovery",
-    "Clarify UX introductory to PRD"
+    "Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/references, localization, edge cases"
   ],
   "capabilities": [
     "ux",

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

@@ -1,6 +1,6 @@
 interface:
   display_name: "UX Discovery"
-  short_description: "Clarify UX introductory to PRD: roles, main flows, navigation, platforms (responsive), brand/re…"
+  short_description: "Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/referenc…"
   default_prompt: "Use $ux_discovery when the task matches the \"UX Discovery\" skill."
 dependencies:
   tools: []

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

@@ -1,12 +1,12 @@
 {
   "name": "ux_discovery",
   "display_name": "UX Discovery",
-  "description": "Clarify UX introductory to PRD: roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases.",
+  "description": "Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/references, localization, edge cases.",
   "default_prompt": "Use $ux_discovery when the task matches the \"UX Discovery\" skill.",
   "triggers": [
     "ux_discovery",
     "ux discovery",
-    "Clarify UX introductory to PRD"
+    "Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/references, localization, edge cases"
   ],
   "capabilities": [
     "ux",

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

@@ -1,12 +1,12 @@
 version: 1
 name: "ux_discovery"
 display_name: "UX Discovery"
-description: "Clarify UX introductory to PRD: roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases."
+description: "Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/references, localization, edge cases."
 default_prompt: "Use $ux_discovery when the task matches the \"UX Discovery\" skill."
 triggers:
   - "ux_discovery"
   - "ux discovery"
-  - "Clarify UX introductory to PRD"
+  - "Clarify UX inputs by PRD — roles, main flows, navigation, platform (responsive), brand/references, localization, edge cases"
 capabilities:
   - "ux"
   - "discovery"