codymaster 4.8.0 → 7.0.0

package/skills/cm-ui-preview/SKILL.archive.md

@@ -0,0 +1,153 @@
+---
+name: cm-ui-preview
+description: "Master Design Skill. Orchestrates AI-powered UI generation using Google Stitch MCP, guided by cm-ux-master intelligence and professional prompt enhancement pipelines. Implements the 'Stitch Build Loop', 'Prompt Optimization Structure', and strict design system adherence to generate production-ready UI previews before coding."
+---
+
+# UI Preview — The Master Design Orchestrator
+
+> **See it before you build it.**
+> This skill transforms vague user requests into precise, structured 'Construction Blueprints' for the Google Stitch AI generator, ensuring UI outputs are professional, consistent with project branding, and ergonomically sound.
+
+## When to Use
+
+**ALWAYS trigger when the task involves building, redesigning, or modifying UI:**
+- Creating new pages, screens, or layouts
+- Building components (forms, cards, dashboards)
+- Restyling or beautifying existing UIs
+- Translating a wireframe or concept into high-fidelity UI
+
+**Trigger keywords:** build UI, design page, create screen, landing page, dashboard layout, UI designer, use stitch, stitch me a ui, redesign, restyle
+
+## Architecture & Workflow (End-to-End)
+
+This skill operates as a pipeline. **Do not skip steps.**
+
+```
+  ┌─────────────────────────────────────────────────────────┐
+  │              cm-ui-preview Master Workflow              │
+  ├─────────────────────────────────────────────────────────┤
+  │                                                         │
+  │  Step 1: PREFLIGHT & INTENT                             │
+  │  ├── Detect task: New UI vs. Refine/Beautify            │
+  │  └── Verify Stitch MCP tools availability               │
+  │                                                         │
+  │  Step 2: DESIGN SYSTEM EXTRACTION (The Source of Truth) │
+  │  ├── Check: .stitch/DESIGN.md, css tokens, etc.         │
+  │  └── Fallback: Trigger `cm-ux-master` to generate one   │
+  │                                                         │
+  │  Step 3: PROMPT ENHANCEMENT (The Build Blueprint)       │
+  │  ├── Project Overview (What, who, style vibe)           │
+  │  ├── Design System Specs (Colors, Typography, Layout)   │
+  │  └── Page Structure (Core function + Specific areas)    │
+  │                                                         │
+  │  Step 4: STITCH EXECUTION (The Build Loop)              │
+  │  ├── create_project()                                   │
+  │  ├── generate_screen_from_text()                        │
+  │  ├── Present link + AI insights to user                 │
+  │  └── User Decision: Confirm / Edit / Skip               │
+  │                                                         │
+  │  Step 5: FINALIZATION & BATON PASS                      │
+  │  ├── Save state to .stitch/next-prompt.md               │
+  │  └── Hand off to cm-execution for actual coding         │
+  │                                                         │
+  └─────────────────────────────────────────────────────────┘
+```
+
+## Step 1: Preflight & Intent Classification
+
+1. **Verify Stitch MCP:** Check if `create_project` and `generate_screen_from_text` are available. If not, inform the user they are missing the Stitch tools but proceed with Prompt-Only generation (output the blueprint for them to use manually).
+2. **Classify Intent:**
+   - **New Screen:** Proceed with full generation.
+   - **Refine/Beautify (edit):** Use `edit_screens()` on existing IDs instead of `generate_screen_from_text()`.
+
+## Step 2: Design System Extraction (Source of Truth)
+
+Before assembly, you MUST establish the design constraints.
+
+**Look for:**
+- `.stitch/DESIGN.md` (Primary source for Stitch)
+- `design-system/MASTER.md` (From `cm-ux-master`)
+- `.cm/design-tokens.css` or Tailwind configs
+
+**If no design system exists:**
+*Suggest running `cm-ux-master` or create a `.stitch/DESIGN.md` baseline.*
+A baseline MUST contain:
+- Platform (Web/Mobile)
+- Primary/Secondary Colors (with hex codes)
+- Typography (Font families)
+- Component constraints (Rounded vs Sharp, Shadow levels)
+
+## Step 3: Prompt Enhancement Pipeline (CRITICAL)
+
+**DO NOT send vague prompts to Stitch (e.g., "Make a login page").**
+You must assemble an "Optimized Prompt Structure" — a detailed construction blueprint.
+
+Structure your prompt exactly like this:
+
+```markdown
+[Overall vibe, mood, and purpose of the page: e.g., "A modern fintech dashboard for B2B users. Professional, trustworthy, high data density, light mode."]
+
+**DESIGN SYSTEM (REQUIRED):**
+- Platform: Web Desktop-first
+- Palette: Primary Blue (#0F62FE), Secondary Gray (#F4F4F4), Danger Red (#DA1E28)
+- Typography: Inter for UI, Roboto Mono for numbers
+- Styles: 4px border radius, subtle drop shadows on cards
+
+**PAGE STRUCTURE & FUNCTION:**
+### 1. Dashboard Home
+**Core function**: Overview of recent transactions and account health.
+- **Top Nav**: Brand logo, Global Search input, User Avatar dropdown.
+- **Hero/Header**: Greeting "Welcome back, {User}", Total Balance callout (Large bold text).
+- **Main Function Area**:
+  - Left col: Line chart showing 30-day revenue.
+  - Right col: Vertical list of "Recent Transactions" (Icon, Title, Date, Amount (Green/Red)).
+- **Action Area**: Primary CTA "Send Money" (Blue fill, large), Secondary "Download Statement" (Outline).
+```
+
+*Refine UI terminology:* Replace "nice buttons" with "Primary CTA", replace "boxes" with "Cards". Apply relevant constraints from `cm-ux-master` (e.g., Miller's Law for chunking lists).
+
+## Step 4: Stitch Execution (The Build Loop)
+
+1. **Project Creation:**
+   ```javascript
+   mcp_StitchMCP_create_project({ title: "UI Preview — {Feature}" })
+   ```
+2. **Screen Generation:**
+   ```javascript
+   mcp_StitchMCP_generate_screen_from_text({
+     projectId: "<id>",
+     prompt: "<Your Optimized Prompt Blueprint>",
+     deviceType: "DESKTOP" // or MOBILE
+   })
+   ```
+3. **User Presentation:**
+   Show the output, provide the URL, and present the **AI Insights** (from the tool's `outputComponents` response).
+
+   ```markdown
+   🎨 **UI Preview Generated!**
+
+   - **Stitch Project ID:** `<id>`
+   - **View & Edit:** [Open in Google Stitch](https://stitch.withgoogle.com/projects/<id>)
+   - **AI Insights:** [Any suggestions or notes returned by Stitch]
+
+   What's next?
+   1. ✅ **Confirm** — I will write the code matching this design exactly.
+   2. ✏️ **Edit** — Tell me what to change, I'll update the preview.
+   3. ⏭️ **Skip** — Proceed straight to coding.
+   ```
+
+## Step 5: Finalization & Baton Pass
+
+- **If Confirm:** Proceed to code implementation. You MUST follow the visual layout, spacing, and colors shown in the Stitch preview.
+- **If Edit:** Call `mcp_StitchMCP_edit_screens()` with the specific element changes.
+- **Baton Update (Optional but Recommended):** Maintain a `.stitch/next-prompt.md` to feed into the next agent task or session for continuity.
+
+## Anti-Patterns (Strict Prohibitions)
+
+- ⛔ **NO VAGUE PROMPTS:** Never pass user input straight to Stitch without the Step 3 Enhancement Pipeline.
+- ⛔ **NO FAKE SUCCESS:** If the MCP tool fails or isn't connected, do not hallucinate a success message or URL.
+- ⛔ **NO CODING (Yet):** This phase is purely for DESIGN PREVIEW. Do not write React/Vue code until the user clicks "Confirm" or "Skip".
+- ⛔ **NO APP SCAFFOLDING:** Do not initialize project codebases in this workflow.
+
+## Future: Pencil.dev Support
+*Pencil MCP tools are available and will be integrated as an alternative execution engine in future updates (`batch_design`, `get_editor_state`).*

package/skills/cm-ui-preview/SKILL.md

@@ -1,153 +1,26 @@
 ---
 name: cm-ui-preview
-description: "Master Design Skill. Orchestrates AI-powered UI generation using Google Stitch MCP, guided by cm-ux-master intelligence and professional prompt enhancement pipelines. Implements the 'Stitch Build Loop', 'Prompt Optimization Structure', and strict design system adherence to generate production-ready UI previews before coding."
+description: "[Deprecated] UI preview is part of design system. Use `cm-design-system` instead."
+deprecated: true
+merged_into: cm-design-system
 ---
 
-# UI Preview — The Master Design Orchestrator
+# cm-ui-preview — Deprecated
 
-> **See it before you build it.**
-> This skill transforms vague user requests into precise, structured 'Construction Blueprints' for the Google Stitch AI generator, ensuring UI outputs are professional, consistent with project branding, and ergonomically sound.
+> ⚠️ This skill is deprecated as of CodyMaster v6.0.0 and will be removed in v6.1.0.
+>
+> **Use `cm-design-system` instead.** UI preview is part of design system.
+>
+> See [docs/migration-v2.md](../../docs/migration-v2.md) for the full mapping.
 
-## When to Use
+The original content is preserved at [SKILL.archive.md](SKILL.archive.md) for reference.
 
-**ALWAYS trigger when the task involves building, redesigning, or modifying UI:**
-- Creating new pages, screens, or layouts
-- Building components (forms, cards, dashboards)
-- Restyling or beautifying existing UIs
-- Translating a wireframe or concept into high-fidelity UI
+## Migration
 
-**Trigger keywords:** build UI, design page, create screen, landing page, dashboard layout, UI designer, use stitch, stitch me a ui, redesign, restyle
-
-## Architecture & Workflow (End-to-End)
-
-This skill operates as a pipeline. **Do not skip steps.**
-
-```
-  ┌─────────────────────────────────────────────────────────┐
-  │              cm-ui-preview Master Workflow              │
-  ├─────────────────────────────────────────────────────────┤
-  │                                                         │
-  │  Step 1: PREFLIGHT & INTENT                             │
-  │  ├── Detect task: New UI vs. Refine/Beautify            │
-  │  └── Verify Stitch MCP tools availability               │
-  │                                                         │
-  │  Step 2: DESIGN SYSTEM EXTRACTION (The Source of Truth) │
-  │  ├── Check: .stitch/DESIGN.md, css tokens, etc.         │
-  │  └── Fallback: Trigger `cm-ux-master` to generate one   │
-  │                                                         │
-  │  Step 3: PROMPT ENHANCEMENT (The Build Blueprint)       │
-  │  ├── Project Overview (What, who, style vibe)           │
-  │  ├── Design System Specs (Colors, Typography, Layout)   │
-  │  └── Page Structure (Core function + Specific areas)    │
-  │                                                         │
-  │  Step 4: STITCH EXECUTION (The Build Loop)              │
-  │  ├── create_project()                                   │
-  │  ├── generate_screen_from_text()                        │
-  │  ├── Present link + AI insights to user                 │
-  │  └── User Decision: Confirm / Edit / Skip               │
-  │                                                         │
-  │  Step 5: FINALIZATION & BATON PASS                      │
-  │  ├── Save state to .stitch/next-prompt.md               │
-  │  └── Hand off to cm-execution for actual coding         │
-  │                                                         │
-  └─────────────────────────────────────────────────────────┘
+```bash
+# Old:           cm <use this skill>
+# New (v6.0+):   cm design-system <equivalent action>
 ```
 
-## Step 1: Preflight & Intent Classification
-
-1. **Verify Stitch MCP:** Check if `create_project` and `generate_screen_from_text` are available. If not, inform the user they are missing the Stitch tools but proceed with Prompt-Only generation (output the blueprint for them to use manually).
-2. **Classify Intent:**
-   - **New Screen:** Proceed with full generation.
-   - **Refine/Beautify (edit):** Use `edit_screens()` on existing IDs instead of `generate_screen_from_text()`.
-
-## Step 2: Design System Extraction (Source of Truth)
-
-Before assembly, you MUST establish the design constraints.
-
-**Look for:**
-- `.stitch/DESIGN.md` (Primary source for Stitch)
-- `design-system/MASTER.md` (From `cm-ux-master`)
-- `.cm/design-tokens.css` or Tailwind configs
-
-**If no design system exists:**
-*Suggest running `cm-ux-master` or create a `.stitch/DESIGN.md` baseline.*
-A baseline MUST contain:
-- Platform (Web/Mobile)
-- Primary/Secondary Colors (with hex codes)
-- Typography (Font families)
-- Component constraints (Rounded vs Sharp, Shadow levels)
-
-## Step 3: Prompt Enhancement Pipeline (CRITICAL)
-
-**DO NOT send vague prompts to Stitch (e.g., "Make a login page").**
-You must assemble an "Optimized Prompt Structure" — a detailed construction blueprint.
-
-Structure your prompt exactly like this:
-
-```markdown
-[Overall vibe, mood, and purpose of the page: e.g., "A modern fintech dashboard for B2B users. Professional, trustworthy, high data density, light mode."]
-
-**DESIGN SYSTEM (REQUIRED):**
-- Platform: Web Desktop-first
-- Palette: Primary Blue (#0F62FE), Secondary Gray (#F4F4F4), Danger Red (#DA1E28)
-- Typography: Inter for UI, Roboto Mono for numbers
-- Styles: 4px border radius, subtle drop shadows on cards
-
-**PAGE STRUCTURE & FUNCTION:**
-### 1. Dashboard Home
-**Core function**: Overview of recent transactions and account health.
-- **Top Nav**: Brand logo, Global Search input, User Avatar dropdown.
-- **Hero/Header**: Greeting "Welcome back, {User}", Total Balance callout (Large bold text).
-- **Main Function Area**:
-  - Left col: Line chart showing 30-day revenue.
-  - Right col: Vertical list of "Recent Transactions" (Icon, Title, Date, Amount (Green/Red)).
-- **Action Area**: Primary CTA "Send Money" (Blue fill, large), Secondary "Download Statement" (Outline).
-```
-
-*Refine UI terminology:* Replace "nice buttons" with "Primary CTA", replace "boxes" with "Cards". Apply relevant constraints from `cm-ux-master` (e.g., Miller's Law for chunking lists).
-
-## Step 4: Stitch Execution (The Build Loop)
-
-1. **Project Creation:**
-   ```javascript
-   mcp_StitchMCP_create_project({ title: "UI Preview — {Feature}" })
-   ```
-2. **Screen Generation:**
-   ```javascript
-   mcp_StitchMCP_generate_screen_from_text({
-     projectId: "<id>",
-     prompt: "<Your Optimized Prompt Blueprint>",
-     deviceType: "DESKTOP" // or MOBILE
-   })
-   ```
-3. **User Presentation:**
-   Show the output, provide the URL, and present the **AI Insights** (from the tool's `outputComponents` response).
-
-   ```markdown
-   🎨 **UI Preview Generated!**
-
-   - **Stitch Project ID:** `<id>`
-   - **View & Edit:** [Open in Google Stitch](https://stitch.withgoogle.com/projects/<id>)
-   - **AI Insights:** [Any suggestions or notes returned by Stitch]
-
-   What's next?
-   1. ✅ **Confirm** — I will write the code matching this design exactly.
-   2. ✏️ **Edit** — Tell me what to change, I'll update the preview.
-   3. ⏭️ **Skip** — Proceed straight to coding.
-   ```
-
-## Step 5: Finalization & Baton Pass
-
-- **If Confirm:** Proceed to code implementation. You MUST follow the visual layout, spacing, and colors shown in the Stitch preview.
-- **If Edit:** Call `mcp_StitchMCP_edit_screens()` with the specific element changes.
-- **Baton Update (Optional but Recommended):** Maintain a `.stitch/next-prompt.md` to feed into the next agent task or session for continuity.
-
-## Anti-Patterns (Strict Prohibitions)
-
-- ⛔ **NO VAGUE PROMPTS:** Never pass user input straight to Stitch without the Step 3 Enhancement Pipeline.
-- ⛔ **NO FAKE SUCCESS:** If the MCP tool fails or isn't connected, do not hallucinate a success message or URL.
-- ⛔ **NO CODING (Yet):** This phase is purely for DESIGN PREVIEW. Do not write React/Vue code until the user clicks "Confirm" or "Skip".
-- ⛔ **NO APP SCAFFOLDING:** Do not initialize project codebases in this workflow.
-
-## Future: Pencil.dev Support
-*Pencil MCP tools are available and will be integrated as an alternative execution engine in future updates (`batch_design`, `get_editor_state`).*
+If you depend on a capability that didn't carry over, please file an issue:
+https://github.com/tody-agent/codymaster/issues

package/skills/cm-ux-master/cli/uxmaster/commands/mcp.py

@@ -26,7 +26,7 @@ def mcp():
 
 @mcp.command()
 @click.option('--port', '-p', default=3000, help='Server port')
-@click.option('--host', '-h', default='0.0.0.0', help='Server host')
+@click.option('--host', '-h', default='127.0.0.1', help='Server host')
 @click.option('--detach', '-d', is_flag=True, help='Run in background')
 def start(port: int, host: str, detach: bool):
     """Start the MCP server.

package/skills/cm-ux-master/mcp/mcp-config.json

@@ -8,7 +8,7 @@
     "args": ["-m", "mcp.server"],
     "env": {
       "PORT": "3000",
-      "HOST": "0.0.0.0"
+      "HOST": "127.0.0.1"
     }
   },
   "capabilities": {

package/skills/cm-ux-master/mcp/server.py

@@ -11,7 +11,7 @@ Usage:
 Environment Variables:
     FIGMA_TOKEN - Figma API access token
     PORT - Server port (default: 3000)
-    HOST - Server host (default: 0.0.0.0)
+    HOST - Server host (default: 127.0.0.1)
 """
 
 import os
@@ -736,7 +736,7 @@ async def root():
 if __name__ == "__main__":
     import uvicorn
     
-    host = os.getenv("HOST", "0.0.0.0")
+    host = os.getenv("HOST", "127.0.0.1")
     port = int(os.getenv("PORT", 3000))
     
     print(f"""

package/skills/profiles/design.txt

@@ -3,4 +3,4 @@ cm-design-system
 cm-ux-master
 cm-ui-preview
 cm-brainstorm-idea
-cm-jtbd
+jtbd

package/skills/profiles/full.txt

@@ -1,18 +1,13 @@
 # Complete CodyMaster skill set (same as default install when --profile full or omitted)
 # Kept in sync with skills/cm-*/ — update when adding skills
-cm-ads-tracker
-cm-auto-publisher
 cm-autopilot
-cm-booking-calendar
 cm-brainstorm-idea
 cm-browse
 cm-clean-code
 cm-code-review
 cm-codeintell
 cm-conductor-worktrees
-cm-content-factory
 cm-continuity
-cm-cro-methodology
 cm-dashboard
 cm-debugging
 cm-deep-search
@@ -24,21 +19,16 @@ cm-engineering-meta
 cm-example
 cm-execution
 cm-git-worktrees
-cm-google-form
-cm-growth-hacking
 cm-guardian-runtime
 cm-how-it-work
 cm-identity-guard
-cm-jtbd
 cm-mcp-engineering
-cm-notebooklm
 cm-planning
 cm-post-deploy-canary
 cm-project-bootstrap
 cm-qa-visual-cli
 cm-quality-gate
 cm-reactor
-cm-readit
 cm-retro-cli
 cm-safe-deploy
 cm-safe-i18n
@@ -46,8 +36,12 @@ cm-second-opinion-cli
 cm-secret-shield
 cm-security-gate
 cm-skill-chain
+cm-skill-evolution
+cm-skill-health
 cm-skill-index
 cm-skill-mastery
+cm-skill-search
+cm-skill-share
 cm-sprint-bus
 cm-start
 cm-status

package/skills/profiles/growth.txt

@@ -1,10 +1,10 @@
 # Marketing, CRO, ads tracking, content — use with core or standalone
-cm-ads-tracker
-cm-cro-methodology
-cm-growth-hacking
-cm-booking-calendar
-cm-content-factory
-cm-auto-publisher
-cm-google-form
-cm-readit
+ads-tracker
+cro-methodology
+growth-hacking
+booking-calendar
+content-factory
+auto-publisher
+google-form
+readit
 cm-dashboard

package/skills/profiles/knowledge.txt

@@ -1,5 +1,5 @@
 # Docs, codebase intelligence, research (often larger skills / MCP-adjacent)
-cm-notebooklm
+notebooklm
 cm-deep-search
 cm-codeintell
 cm-dockit

package/skills/profiles/top35.json

@@ -0,0 +1,41 @@
+{
+  "version": 1,
+  "description": "Top 35 canonical skills synced to multi-platform installers (Cursor / Codex / OpenCode). Drives scripts/build-skills.mjs --platforms.",
+  "skills": [
+    "cm-skill-index",
+    "cm-how-it-work",
+    "cm-start",
+    "cm-planning",
+    "cm-execution",
+    "cm-continuity",
+    "cm-status",
+    "cm-tdd",
+    "cm-debugging",
+    "cm-code-review",
+    "cm-clean-code",
+    "cm-quality-gate",
+    "cm-test-gate",
+    "cm-safe-deploy",
+    "cm-secret-shield",
+    "cm-identity-guard",
+    "cm-security-gate",
+    "cm-safe-i18n",
+    "cm-skill-chain",
+    "cm-git-worktrees",
+    "cm-terminal",
+    "cm-brainstorm-idea",
+    "jtbd",
+    "cm-design-system",
+    "cm-ui-preview",
+    "cm-ux-master",
+    "content-factory",
+    "ads-tracker",
+    "cro-methodology",
+    "google-form",
+    "cm-dashboard",
+    "cm-codeintell",
+    "cm-deep-search",
+    "cm-project-bootstrap",
+    "cm-reactor"
+  ]
+}

package/adapters/antigravity.js

@@ -1,15 +0,0 @@
-/**
- * Converts a Universal SKILL.md into Google Antigravity (Gemini) format.
- * Antigravity relies on `<skills>` blocks in system prompts and explicitly
- * supports subagent dispatch via the `browser_subagent` or custom endpoints.
- */
-
-export function buildAntigravityPrompt(skillMeta, context) {
-    return `
-<skills>
-  - ${skillMeta.name}: ${skillMeta.description}
-  To execute, consider using subagents for maximum speed.
-  ${context.join('\n')}
-</skills>
-    `;
-}

package/adapters/claude-code.js

@@ -1,17 +0,0 @@
-/**
- * Converts a Universal SKILL.md into Claude Code format.
- * Claude Code uses customized .claude file configurations or project-level prompts.
- */
-
-export function buildClaudePrompt(skillMeta, context) {
-    return `
-# Skill: ${skillMeta.name}
-${skillMeta.description}
-
-Context values:
-${context.join('\n')}
-
-INSTRUCTIONS:
-You are equipped with this skill. Execute it strictly when the user invokes the corresponding command.
-    `;
-}

package/adapters/cursor.js

@@ -1,16 +0,0 @@
-/**
- * Converts a Universal SKILL.md into Cursor / Windsurf / Cline format.
- * These typically rely on `.cursorrules` or `.windsurfrules` files in the workspace.
- */
-
-export function buildCursorRules(skillMeta, context) {
-    return `
-# @Rule: ${skillMeta.name}
-Description: ${skillMeta.description}
-
-Rules:
-1. Always follow the universal skill format.
-2. Context injected:
-${context.join('\n')}
-    `;
-}