Menu
Use when you need visual QA, screenshots, or post-deploy smoke testing through a real browser with Playwright.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Complete guide to vibe coding with CodyMaster — from idea to deploy. Read this first if you are new.
Bootstrap any new project: identity, design system, staging+production, i18n, SEO, test infrastructure, 8-gate deploy pipeline. Prevents tech debt from day 0.
Ultimate UI/UX design intelligence: an Anti-Slop layer that kills AI tells (em-dash, AI purple glow, generic names, template layouts), tunable Design Dials (variance/motion/density) and Style Modes (functional, minimalist, brutalist, soft-premium, marketing), 161 industry color palettes in a shadcn-aligned semantic token schema, 48 UX Laws, 37 Design Tests, UX Heuristics (Nielsen + Krug), Harvester extraction, Figma & Google Stitch integration, MCP server, Component Generator, and BM25 search across 17 domains + 19 framework stacks. One command = complete design system. Use when designing or reviewing UI/UX, choosing colors/typography, fixing generic AI-looking designs, or building Web App / SaaS / Mobile screens.
Fallback local Playwright daemon for real-browser visual QA / screenshots / smoke. Use ONLY when the host platform has no native browser mode — prefer the host browser first.
Use when you need to interact with the MCP engineering bridge tools (cm_plan, cm_review, cm_qa, cm_deploy, cm_search).
Self-learning SEO content pipeline: dashboard, multi-agent queue, token budgets, research → write → audit → publish. StoryBrand/Cialdini/JTBD-style frameworks; config-driven. Use for content factory, batch articles, or scaled publishing.
| name | cm-browse |
| description | Use when you need visual QA, screenshots, or post-deploy smoke testing through a real browser with Playwright. |
Full runbook: docs/browse-daemon.md (install Chromium, token, troubleshooting).
cm browse + cm qa-visual.export CM_BROWSE_TOKEN="$(openssl rand -hex 24)"
cm browse start --port 17395 --token "$CM_BROWSE_TOKEN"
POST /session/start body { "headless": true }POST /navigate { "url": "https://…" }POST /refs/refresh — assigns data-cm-ref to interactive nodes; use @e1 style refs.POST /click { "ref": "e1" }POST /fill { "ref": "e2", "value": "text" }GET /screenshot — PNGGET /console / GET /network — ring bufferscm qa-visual --url … calls the daemon locally.cm-canary / cm-safe-deploy for ship verification.