codyhxyz

Convert an existing vanilla MV3 Chrome extension (hand-authored manifest.json + flat HTML/JS/CSS) into a WXT-based factory clone. Auto-detects popup/options/sidepanel/welcome/background/content profiles from the manifest, auto-detects whether React or Tailwind is actually in use (default-off for pure vanilla), scaffolds the factory skeleton at a sibling directory, moves vanilla files into the WXT entrypoint layout, wraps background/content scripts, translates manifest fields into wxt.config.ts, and runs `npm install` + `wxt prepare` + `npm run check:cws` to leave a structurally-green extension ready for the rest of CCE's skill pipeline. Use when the user says things like "convert my extension to WXT", "import this vanilla extension", "migrate to the factory", "I have an existing extension I want to use with CCE", or "/cce-import".

First-time onboarding for a freshly-cloned Chrome Extension Factory. Orients the user on the factory's philosophy, walks through extension-shape profile selection (deleting unused entrypoints), delegates to `cws-content` for listing copy, optionally runs `cws-screens` for screenshots, optionally walks through OAuth setup, confirms structural green, and drops a `.cce-init-done` marker. Idempotent — re-invoking on an already-initialized factory offers a sub-recipe menu instead of re-running the whole flow.

Rename a Chrome Extension Factory project — change the display name, slug, description, and (optionally) the parent folder in one pass. Updates wxt.config.ts, package.json, marketing/og.config.mjs, and per-entrypoint configs (welcome/screenshots/video), then lists prose files (README, CHANGELOG, etc.) that still mention the old name for manual follow-up. Idempotent; supports dry-run. Use when the user says things like "rename this extension", "change the extension name", "rebrand", "I renamed the project", or "/cce-rename".

Interview the user to fill out Chrome Web Store screenshot config. Picks 5 screenshots (surface + copy per shot), writes to screenshots/config.ts, regenerates PNGs. ALSO produces the two promo tiles (440×280 small + 1400×560 marquee) by default, because skipping them disqualifies the extension from Featured-badge placement. Distinct from the iOS app-store-screenshots skill.

Orchestrate the full Chrome Web Store submission flow — gate on ship-mode validator, reconcile version, summarize, submit via `npm run ship`, and interpret the terminal state (live / in-review / rejected / failed / timeout). Delegates content fixes to `cws-content`, screenshot fixes to `cws-screens`, and video fixes to `cws-video` rather than duplicating their recipes. Does NOT implement any deterministic checks itself; it reads `--json` from the existing scripts.

Interview the user to fill in Chrome Web Store listing and welcome-page copy, clearing the ship-mode content errors flagged by `scripts/validate-cws.ts`. Does NOT submit and does NOT zip — this skill only turns red ship-mode content rules green.

Walk the user through obtaining the four Chrome Web Store API credentials (CWS_EXTENSION_ID, CWS_CLIENT_ID, CWS_CLIENT_SECRET, CWS_REFRESH_TOKEN) and a GCP project. Automates everything Google exposes an API for; provides handholding (optional computer-use + GUI wizard) for the one step Google forces you to do by hand — creating an OAuth 2.0 Desktop client ID.

Generate a launch promo video for a Chrome extension — used both as the CWS listing's embedded promo (≤30s, YouTube) and as a launch asset for ProductHunt, Twitter, LinkedIn. Wraps `heygen-com/hyperframes` to do the actual generation. Interviews the user for hook, beats, and exports; writes `video/config.ts`; invokes hyperframes; verifies the exported video clears the `ship-ready-video` validator rule.

Use when the user wants to create, package, publish, resume mid-development, maintain, rename, or check the status of a Claude Code plugin — including converting a personal `.claude/` config into a shareable plugin, adding a marketplace, hosting on GitHub, submitting to the official Anthropic plugin marketplace, picking up a plugin scaffolded in an earlier session, shipping an update to an already-published plugin, renaming an existing plugin, or syncing plugin.json changes out to marketplace entries and the GitHub repo. Triggers on phrases like "make a Claude plugin", "package this skill", "publish to the Claude store", "claude-plugin-official", "/plugin marketplace add", "what's left on my plugin", "plugin status", "am I ready to submit", "resume my plugin", "ship an update", "rename my plugin", "change the plugin name", "sync plugin metadata", "update the GitHub repo description", "my marketplace is out of sync", "check for drift", "plugin.json and marketplace.json don't match", or any request to scaffold,

Use when [SPECIFIC_TRIGGERING_CONDITIONS_AND_SYMPTOMS]. Triggers on phrases like [EXAMPLE_PHRASES].

Use when generating a proof-of-value artifact for a Claude Code plugin — a visual before/after, benchmark chart, terminal diff, output-quality comparison, coverage checklist, or file-tree diff — so the README answers "what does this plugin give me that I can't already do?" with evidence instead of adjectives. Invoked from Phase 5.5 of the `create-claude-plugin` skill, or directly when the user says "prove the value", "add a demo", "before after", "benchmark image", "show the proof", "receipts", "show me it works".

Use when generating an Open Graph social-preview image (1200×630 PNG) for a Claude Code plugin repo, so link unfurls in Twitter / Slack / iMessage / LinkedIn / GitHub's social-preview slot render as a branded card instead of a grey placeholder. Invoked from Phase 5.5 of the `create-claude-plugin` skill when the user picks "Draft og-card now", or directly when the user says "make an og image", "og card", "social preview image", or "link unfurl card". Mirrors the Chrome Web Store `cws-screens` skill's shape: interview → typed config → render → PNG.

Use when output quality matters and diverse approaches would strengthen the result — dispatches N parallel drafters, ranks via a decisive judge, optionally synthesizes a best-of-all artifact. Good for cold emails, naming, short prose, plans, brainstorms. Not for deterministic code tasks.

Use before starting any research, data gathering, or knowledge-base build to set up the right folder structure.

Use when your previous reply reached for "can't" / "cannot" / "can not" — shift from constraint-first framing to high-agency, chief-of-staff problem-solving. Triggered automatically by the high-agency-mode Stop hook; can also be invoked directly on phrases like "reframe this", "find another way", "no, actually solve it".

Recreate a font from a specimen image using bitmap tracing. Analyzes the specimen, identifies a matching OFL base font from Google Fonts, renders glyphs at high resolution, traces with potrace into clean vector outlines, and builds an OTF font file. Invoke when the user shows you a font they like and wants their own version of it.

Use when the user wants to save, recall, list, or search notes about a song they are listening to on the Spotify desktop app — without opening a browser or authenticating. Triggers on phrases like "note: ...", "take a note about this song", "save that thought", "what did I write about this song", "what songs have I annotated", "find my notes about [topic]", "pull up my song notes".

Use when reviewing an existing codebase, extension, plugin, app, or project — especially AI-generated code — to understand it deeply and propose meaningful improvements. Triggers on phrases like "review this code", "review this repo", "review this extension/app/project", "audit this repo", "tell me what to change", "what could be better", "make this killer", or any request to analyze and improve an existing implementation.