code-ai-installer 2.4.1 → 3.0.0

package/locales/en/.agents/skills/ui-inventory/agents/skill.yaml

@@ -1,21 +0,0 @@
-version: 1
-name: "ui-inventory"
-display_name: "UI Inventory"
-description: "Compile an inventory of UI components and reuse rules — base components, composition components, patterns (forms, tables, dialogs), design tokens (minimum)."
-default_prompt: "Use $ui-inventory when the task matches the \"UI Inventory\" skill."
-triggers:
-  - "ui-inventory"
-  - "ui inventory"
-  - "Compile an inventory of UI components and reuse rules — base components, composition components, patterns (forms, tables, dialogs), design tokens (minimum)"
-capabilities:
-  - "ui"
-  - "inventory"
-tools: []
-invocation:
-  explicit: true
-  implicit: true
-localization:
-  default_locale: "en"
-  available_locales:
-    - "ru"
-    - "en"

package/locales/en/.agents/skills/ux-discovery/SKILL.md

@@ -1,213 +0,0 @@
----
-name: ux-discovery
-description: Clarify UX inputs based on PRD — roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases.
----
-
-# Skill: UX Discovery
-
-Gather missing UX context before creating the UX Spec.
-
-**Sections:**
-1. [Workflow](#1-workflow)
-2. [Question Bank](#2-questions)
-3. [Priority Matrix](#3-priority)
-4. [Assumptions Framework](#4-assumptions)
-5. [Example](#5-example)
-6. [Output Template](#6-output)
-
----
-
-## 1. Workflow
-
-```
-1. Read PRD (from $pm-prd)
-   └── Extract: goals, user stories, acceptance criteria, constraints
-
-2. Check: what is already known vs what needs clarification
-   ├── Known → mark as a fact
-   └── Unknown → add to the list of questions
-
-3. Prioritize questions (section 3):
-   ├── 🔴 Blocking: cannot choose an approach without an answer
-   ├── 🟠 Important: affects UX Spec, but an assumption can be made
-   └── 🟡 Nice-to-know: useful, but not critical
-
-4. If the answer is critical → ask the user
-   If an assumption can be made → document the assumption + mark "ASSUMPTION"
-
-5. Generate Discovery Report (section 6)
-
-6. Hand off to → $ux-spec
-```
-
-### When discovery is NOT needed
-
-| Situation | Action |
-|----------|---------|
-| PRD already contains all answers | Skip discovery → go straight to $ux-spec |
-| Iteration on existing UI | Minimal discovery (only new questions) |
-| Bugfix / hotfix | Not needed |
-
----
-
-## 2. Question Bank
-
-### A) Platform and layout
-
-| # | Question | Why |
-|---|--------|-------|
-| Q-01 | Desktop-first, mobile-first or responsive? | Determines breakpoints and layout strategy |
-| Q-02 | Minimum supported resolutions? | Affects grid and responsive rules |
-| Q-03 | Embedded in iframe or standalone? | Critical for sizing, scrolling, navigation |
-| Q-04 | Is there a dark mode / theme switching? | Affects design tokens and CSS strategy |
-
-### B) Roles and permissions
-
-| # | Question | Why |
-|---|--------|-------|
-| Q-05 | What are the user roles? | Determines navigation and permissions logic |
-| Q-06 | What can / cannot each role do? | Affects UI visibility and server-side auth |
-| Q-07 | Is an admin panel / moderation needed? | Might require a separate layout |
-| Q-08 | Is there onboarding for new users? | Additional screens/flow |
-
-### C) Navigation and structure
-
-| # | Question | Why |
-|---|--------|-------|
-| Q-09 | Main sections / tabs / pages? | Determines IA (Information Architecture) |
-| Q-10 | Is there deep linking (URL sharing)? | Affects routing strategy |
-| Q-11 | Are 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 | Is there Figma / mockup / design system? | Determines the "source of truth" for UI |
-| Q-14 | Are there visual references / inspiration? | Direction for design decisions |
-| 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 do we show for empty data? | Empty state design |
-| Q-18 | Which operations are potentially slow? | Loading/skeleton strategy |
-| Q-19 | What do we do on network/server errors? | Error state design |
-| Q-20 | Are there 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 multiple? | i18n setup |
-| Q-23 | RTL support? | CSS direction strategy |
-| Q-24 | Format of dates / times / currencies? | Locale-specific formatting |
-
----
-
-## 3. Priority Matrix
-
-| Priority | Meaning | Action |
-|----------|---------|--------|
-| 🔴 **Blocking** | Cannot start UX Spec without an answer | Must ask the user |
-| 🟠 **Important** | Affects UX, but an assumption can be made | Ask or document ASSUMPTION |
-| 🟡 **Nice-to-know** | Useful for polish, not for MVP | Postpone or assume |
-
-### Typical prioritization
-
-| Category | Typical Priority |
-|-----------|:------------------:|
-| Platform (iframe / responsive) | 🔴 |
-| Roles & permissions | 🔴 |
-| Navigation / IA | 🟠 |
-| Brand / design system | 🟠 |
-| Empty / error states | 🟠 |
-| Localization | 🟡 |
-| Real-time updates | 🟡 |
-
----
-
-## 4. Assumptions Framework
-
-When there is no answer, document an assumption:
-
-```markdown
-### ASSUMPTION-01: Desktop-first layout
-**Question:** Q-01 — responsive strategy
-**Assumption:** Desktop-first, min-width 1024px
-**Reasoning:** PRD describes a dashboard, typical use case is desktop
-**Risk:** Low — easy to add mobile breakpoints later
-**Needs confirmation by:** Before v1.0
-```
-
----
-
-## 5. Example
-
-```markdown
-# UX Discovery: SaaS Admin Panel
-
-## Facts from PRD
-- Admin dashboard for content configuration
-- Roles: Admin (full access), Viewer (read-only)
-- Features: Settings, Content CRUD, Preview
-
-## Clarified
-- Q-01: Desktop-first, responsive later → 🔴 confirmed
-- Q-13: Design system — shadcn/ui → 🟠 confirmed
-- Q-17: Empty state — show "Create your first item" CTA → 🟠 confirmed
-
-## Assumptions
-- ASSUMPTION-01: Desktop-first (admin panel = 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, standalone app | PRD §1 |
-| F-02 | Two roles: Admin, Viewer | PRD §2.1 |
-
-## Questions
-| # | Question | Priority | Answer | Status |
-|---|----------|:--------:|--------|:------:|
-| Q-01 | Responsive or desktop only? | 🔴 | Desktop-first | ✅ Answered |
-| Q-13 | Design system? | 🟠 | shadcn/ui | ✅ Answered |
-| Q-20 | Real-time? | 🟡 | — | ASSUMED: No |
-
-## Assumptions
-| ID | Assumption | Risk | Confirm by |
-|----|-----------|:----:|-----------:|
-| ASSUMPTION-01 | Desktop-first | Low | v1.0 |
-| ASSUMPTION-02 | English only | Low | v1.0 |
-
-## Screen / Flow Inventory (draft)
-1. Admin Panel → Settings (tabs: General, Appearance, Notifications)
-2. Admin Panel → Items list (CRUD)
-3. Public UI → Content display (end-user facing)
-
-## Next Step
-→ Proceed to $ux-spec with confirmed facts + assumptions
-```
-
----
-
-## See also
-- `$pm-prd` — PRD (input for discovery)
-- `$ux-spec` — UX Spec (output of discovery)
-- `$design-intake` — design materials analysis

package/locales/en/.agents/skills/ux-discovery/agents/claude.json

@@ -1,17 +0,0 @@
-{
-  "name": "ux-discovery",
-  "display_name": "UX Discovery",
-  "description": "Clarify UX inputs based on PRD — roles, main flows, navigation, platforms (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 inputs based on PRD — roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases"
-  ],
-  "capabilities": [
-    "ux",
-    "discovery"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/ux-discovery/agents/copilot.json

@@ -1,17 +0,0 @@
-{
-  "name": "ux-discovery",
-  "display_name": "UX Discovery",
-  "description": "Clarify UX inputs based on PRD — roles, main flows, navigation, platforms (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 inputs based on PRD — roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases"
-  ],
-  "capabilities": [
-    "ux",
-    "discovery"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/ux-discovery/agents/gemini.json

@@ -1,17 +0,0 @@
-{
-  "name": "ux-discovery",
-  "display_name": "UX Discovery",
-  "description": "Clarify UX inputs based on PRD — roles, main flows, navigation, platforms (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 inputs based on PRD — roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases"
-  ],
-  "capabilities": [
-    "ux",
-    "discovery"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/ux-discovery/agents/openai.yaml

@@ -1,8 +0,0 @@
-interface:
-  display_name: "UX Discovery"
-  short_description: "Clarify UX inputs based on PRD — roles, main flows, navigation, platforms (responsive), brand/r…"
-  default_prompt: "Use $ux-discovery when the task matches the \"UX Discovery\" skill."
-dependencies:
-  tools: []
-policy:
-  allow_implicit_invocation: true

package/locales/en/.agents/skills/ux-discovery/agents/qwen.json

@@ -1,17 +0,0 @@
-{
-  "name": "ux-discovery",
-  "display_name": "UX Discovery",
-  "description": "Clarify UX inputs based on PRD — roles, main flows, navigation, platforms (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 inputs based on PRD — roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases"
-  ],
-  "capabilities": [
-    "ux",
-    "discovery"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/ux-discovery/agents/skill.yaml

@@ -1,21 +0,0 @@
-version: 1
-name: "ux-discovery"
-display_name: "UX Discovery"
-description: "Clarify UX inputs based on PRD — roles, main flows, navigation, platforms (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 inputs based on PRD — roles, main flows, navigation, platforms (responsive), brand/references, localization, edge cases"
-capabilities:
-  - "ux"
-  - "discovery"
-tools: []
-invocation:
-  explicit: true
-  implicit: true
-localization:
-  default_locale: "en"
-  available_locales:
-    - "ru"
-    - "en"

package/locales/en/.agents/skills/ux-spec/SKILL.md

@@ -1,280 +0,0 @@
----
-name: ux-spec
-description: Generate UX Spec — user flows, IA, list of screens, specification of each screen (actions/sections/validations/states), UX quality criteria for development and testing.
----
-
-# Skill: UX Spec (Flows + Screens + States)
-
-Specification that allows implementing UI without "guesswork".
-
-**Sections:**
-1. [Workflow](#1-workflow)
-2. [UX Spec Structure](#2-structure)
-3. [Screen Spec Format](#3-screen-format)
-4. [Interaction Patterns](#4-interactions)
-5. [Quality Checklist](#5-quality)
-6. [Handoff Checklist](#6-handoff)
-7. [Example: Settings Screen](#7-example)
-8. [Output Template](#8-output)
-
----
-
-## 1. Workflow
-
-```
-1. Input: UX Discovery Report (from $ux-discovery) + PRD
-2. Define users & roles
-3. Map user flows (trigger → steps → outcome)
-4. Define IA (screens, navigation, routes)
-5. For each screen → spec (section 3)
-6. Define interaction patterns (section 4)
-7. Run quality checklist (section 5)
-8. Create handoff package (section 6)
-```
-
----
-
-## 2. UX Spec Structure
-
-### 1) Users & Roles
-
-```markdown
-| Role | Permissions | Access |
-|------|------------|--------|
-| Admin | Full CRUD, settings | Dashboard, admin panel |
-| End User | View content, interact | Public-facing UI |
-```
-
-### 2) Key User Flows
-
-For each flow:
-
-```markdown
-### Flow: Create Item
-
-**Trigger:** User clicks "Add Item" in Items section
-**Preconditions:** Logged in, authorized
-
-| Step | Action | Result |
-|------|--------|--------|
-| 1 | Click "Add Item" button | Form appears |
-| 2 | Fill name, value, type, expiry | Fields validated inline |
-| 3 | Click "Save" | Loading state → toast "Saved" |
-
-**Success:** Item appears in list
-**Failure:** Validation errors shown inline
-**Edge:** Duplicate name → error "Name already exists"
-```
-
-### 3) Information Architecture
-
-```markdown
-Admin Panel
-├── Settings
-│   ├── General tab (title, description, CTA)
-│   ├── Appearance tab (colors, fonts, layout)
-│   └── Notifications tab (alerts, triggers)
-├── Items
-│   ├── List (table with CRUD)
-│   └── Create/Edit form
-└── Preview (side panel)
-```
-
-### 4) Screen Specs → section 3
-
-### 5) UI Rules → section 4
-
----
-
-## 3. Screen Spec Format
-
-### Template
-
-```markdown
-## Screen: <Name>
-
-**URL/Route:** /admin/settings
-**Purpose:** Configure application appearance and behavior
-**Role access:** Admin
-
-### Layout
-- [ ] Two-column: config panel (left) + preview (right)
-- [ ] Tabs: General | Appearance | Notifications
-
-### Sections & Components
-| Section | Components | Notes |
-|---------|-----------|-------|
-| Header | Title, Breadcrumbs | — |
-| Config Panel | Tabs → FormFields | Tab-specific content |
-| Live Preview | PopupPreview | Real-time updates |
-| Actions | Save button, Reset link | Bottom of config panel |
-
-### Primary Actions
-| Action | Element | Behavior |
-|--------|---------|----------|
-| Save | Primary button | POST → toast "Saved" → refresh preview |
-| Reset | Ghost link | Confirm dialog → reset to defaults |
-| Switch tab | Tab buttons | Update config panel content |
-
-### Forms & Validation
-| Field | Type | Required | Validation | Error message |
-|-------|------|:--------:|-----------|--------------|
-| Title | Text | ✅ | 1-100 chars | "Title is required" |
-| Subtitle | Textarea | ❌ | max 300 chars | "Too long (max 300)" |
-| BG Color | ColorPicker | ✅ | valid hex | "Invalid color" |
-
-### States
-| State | Visual | Trigger |
-|-------|--------|---------|
-| **Loading** | Skeleton in config panel + preview | Initial fetch |
-| **Empty** | — (always has defaults) | — |
-| **Error** | Inline field errors + toast for server errors | Save fails |
-| **Success** | Toast "Settings saved" | Successful save |
-| **Saving** | Button shows spinner, disabled | During POST |
-
-### Notifications
-| Event | Type | Message | Duration |
-|-------|------|---------|----------|
-| Save success | Toast (success) | "Settings saved" | 3s auto-dismiss |
-| Save error | Toast (error) | "Failed to save. Try again." | Manual dismiss |
-| Reset confirm | Modal (confirm) | "Reset to defaults?" | — |
-
-### Responsive Notes
-- Desktop only (admin panel)
-- Min width: 700px
-```
-
----
-
-## 4. Interaction Patterns
-
-### Standard patterns (apply globally)
-
-| Pattern | Rule |
-|---------|------|
-| **Primary action** | One primary button per screen (filled, accent color) |
-| **Secondary action** | Outlined or ghost button |
-| **Destructive action** | Red button + confirmation modal |
-| **Loading** | Skeleton for initial load, spinner for in-flight actions |
-| **Save** | Button shows spinner + disabled during save |
-| **Form errors** | Inline below field, red text, shown on blur + submit |
-| **Toast** | Bottom-right, auto-dismiss 3-5s for success, manual dismiss for errors |
-| **Empty list** | Illustration + message + CTA ("Create your first item") |
-| **Pagination** | Bottom of list, show total count + page controls |
-| **Hover** | Subtle background change on interactive elements |
-| **Transitions** | 200-300ms ease for all state changes |
-
-### Keyboard interactions
-
-| Element | Enter | Escape | Tab |
-|---------|-------|--------|-----|
-| Button | Activate | — | Next element |
-| Modal | — | Close | Trap focus inside |
-| Dropdown | Select item | Close | Navigate items |
-| Tab | Switch tab | — | Next tab |
-| Form | Submit (if last field) | — | Next field |
-
----
-
-## 5. Quality Checklist
-
-| # | Check | Status |
-|---|-------|--------|
-| UX-01 | Every PRD user story has a corresponding flow | ☐ |
-| UX-02 | Every flow has a screen spec | ☐ |
-| UX-03 | Every screen has all 4 states (loading/empty/error/success) | ☐ |
-| UX-04 | Every form has validation rules + error messages | ☐ |
-| UX-05 | Destructive actions have confirmation | ☐ |
-| UX-06 | All components listed (no vague "and more...") | ☐ |
-| UX-07 | All user actions documented (clicks, navigation, forms) | ☐ |
-| UX-08 | Responsive behavior specified (or explicitly desktop-only) | ☐ |
-| UX-09 | Permissions affect UI visibility (documented) | ☐ |
-| UX-10 | Edge cases covered (duplicate, max length, empty, concurrent) | ☐ |
-
----
-
-## 6. Handoff Checklist
-
-What UX/UI Designer passes to Architect / DEV:
-
-| # | Deliverable | For whom | Status |
-|---|------------|:--------:|--------|
-| 1 | UX Spec document | Architect + DEV | ☐ |
-| 2 | Screen list + routes | Architect | ☐ |
-| 3 | UI Inventory (`$ui-inventory`) | DEV | ☐ |
-| 4 | A11y Baseline (`$a11y-baseline`) | DEV + Tester | ☐ |
-| 5 | Design reference (Stitch/Figma/HTML) | DEV | ☐ |
-| 6 | Component states mapping | DEV + Tester | ☐ |
-| 7 | Validation rules table | Architect (→ API contracts) | ☐ |
-
----
-
-## 7. Example: Settings Screen
-
-```markdown
-## Screen: Settings
-
-**URL/Route:** /admin/settings
-**Purpose:** Configure application appearance
-**Role:** Admin
-
-### Layout
-Two-column: Config Panel (left, 60%) + Preview (right, 40%)
-
-### Sections
-| Section | Tab | Components |
-|---------|-----|-----------|
-| Title & Subtitle | General | TextInput, Textarea |
-| CTA Button | General | TextInput, Switch (show/hide) |
-| Appearance | Appearance | ColorPickers (4 tokens), FontSelect |
-| Notifications | Notifications | Switch (enable), frequency Select |
-
-### States
-| State | Loading | Empty | Error | Success |
-|-------|---------|-------|-------|---------|
-| Config | Skeleton fields | N/A (defaults) | Inline + toast | Toast "Saved" |
-| Preview | Skeleton preview | Default template | Error illustration | Live update |
-```
-
----
-
-## 8. Output Template
-
-```markdown
-# UX Spec: <Feature/Project>
-
-**Date:** YYYY-MM-DD
-**Author:** UX/UI Designer Agent
-**PRD:** <reference>
-**Discovery:** <reference>
-
-## 1. Users & Roles
-<section 2 table>
-
-## 2. Key User Flows
-<section 2 flow format × N flows>
-
-## 3. Information Architecture
-<IA tree>
-
-## 4. Screen Specs
-<section 3 format × N screens>
-
-## 5. Interaction Patterns
-<section 4 tables>
-
-## 6. Quality Checklist
-<section 5 — all checked>
-
-## Handoff
-<section 6 — all checked>
-```
-
----
-
-## See also
-- `$ux-discovery` — discovery before spec
-- `$ui-inventory` — component inventory
-- `$a11y-baseline` — accessibility requirements
-- `$design-intake` — analyze design materials
-- `$google-stitch-skill` — generate UI screens from spec

package/locales/en/.agents/skills/ux-spec/agents/claude.json

@@ -1,17 +0,0 @@
-{
-  "name": "ux-spec",
-  "display_name": "UX Spec",
-  "description": "Generate UX Spec — user flows, IA, list of screens, specification of each screen (actions/sections/validations/states), UX quality criteria for development and testing.",
-  "default_prompt": "Use $ux-spec when the task matches the \"UX Spec\" skill.",
-  "triggers": [
-    "ux-spec",
-    "ux spec",
-    "Generate UX Spec — user flows, IA, list of screens, specification of each screen (actions/sections/validations/states), UX quality criteria for development and testing"
-  ],
-  "capabilities": [
-    "ux",
-    "spec"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/ux-spec/agents/copilot.json

@@ -1,17 +0,0 @@
-{
-  "name": "ux-spec",
-  "display_name": "UX Spec",
-  "description": "Generate UX Spec — user flows, IA, list of screens, specification of each screen (actions/sections/validations/states), UX quality criteria for development and testing.",
-  "default_prompt": "Use $ux-spec when the task matches the \"UX Spec\" skill.",
-  "triggers": [
-    "ux-spec",
-    "ux spec",
-    "Generate UX Spec — user flows, IA, list of screens, specification of each screen (actions/sections/validations/states), UX quality criteria for development and testing"
-  ],
-  "capabilities": [
-    "ux",
-    "spec"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/ux-spec/agents/gemini.json

@@ -1,17 +0,0 @@
-{
-  "name": "ux-spec",
-  "display_name": "UX Spec",
-  "description": "Generate UX Spec — user flows, IA, list of screens, specification of each screen (actions/sections/validations/states), UX quality criteria for development and testing.",
-  "default_prompt": "Use $ux-spec when the task matches the \"UX Spec\" skill.",
-  "triggers": [
-    "ux-spec",
-    "ux spec",
-    "Generate UX Spec — user flows, IA, list of screens, specification of each screen (actions/sections/validations/states), UX quality criteria for development and testing"
-  ],
-  "capabilities": [
-    "ux",
-    "spec"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/ux-spec/agents/openai.yaml

@@ -1,8 +0,0 @@
-interface:
-  display_name: "UX Spec"
-  short_description: "Generate UX Spec — user flows, IA, list of screens, specification of each screen (actions/secti…"
-  default_prompt: "Use $ux-spec when the task matches the \"UX Spec\" skill."
-dependencies:
-  tools: []
-policy:
-  allow_implicit_invocation: true