Run any Skill in Manus with one click

ship

Stars0

Forks0

UpdatedJune 21, 2026 at 17:30

Assemble an accepted changeset and dispatch the implementation handoff over MCP to ai-dev / developerz.ai. Use when touching src/mcp, the ship flow in src/entrypoints/background.ts, or when the task mentions handoff, shipping a design, MCP task creation, or turning edits into a PR.

Installation

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.

Run Skill in Manus

Source

developerz-ai

developerz-ai/ai-designer

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	ship
description	Assemble an accepted changeset and dispatch the implementation handoff over MCP to ai-dev / developerz.ai. Use when touching src/mcp, the ship flow in src/entrypoints/background.ts, or when the task mentions handoff, shipping a design, MCP task creation, or turning edits into a PR.

Ship turns a Changeset into a real code task. Runs in the service worker (owns keys + MCP clients). See docs/idea/handoff.md, docs/idea/mcp.md, docs/architecture/handoff.md.

Rules

User-triggered only. Never auto-ship. "Ship" is an explicit button → ship message. The agent never calls handoff on its own.
The changeset is the spec: intent + stable selector + frameworkHints map the visual change to source.
MCP client lives in the service worker. Connect via @ai-sdk/mcp createMCPClient over Streamable HTTP (not SSE). See docs/reference/agent-sdk.md.

Flow

Assemble + validate the Changeset (Zod, src/shared/changeset.ts). Refuse empty/invalid.
Resolve the configured backend + auth token (ai-dev: admin/worker key or OAuth user token).
Open the MCP client, call task with action: 'create', changeset as the task spec.
Stream status back to the panel; surface the PR link when the dev-agent opens it.
On failure: report the MCP error to the panel, keep the changeset (don't discard the user's work).

Don't

Don't persist mutations to any server — the only durable output is the changeset → PR.
Don't embed keys/tokens in the changeset or any content-script message.

More from this repository

same repository

live-edit

developerz-ai/ai-designer

Implement or modify the in-browser live-edit engine — DOM mutation primitives, the element picker, stable-selector heuristics, and the changeset recorder. Use when touching src/dom, src/entrypoints/content.ts, or src/shared/changeset.ts, or when the task mentions live editing, DOM tools, selectors, or recording changes.

2026-06-210

mv3

developerz-ai/ai-designer

Manifest V3 extension gotchas — the three execution worlds, key custody, CSP / no-remote-code, the ephemeral service worker, and the typed message bus. Use when touching the manifest, wxt.config.ts, entrypoints, cross-world messaging, or when something behaves differently in the extension than in tests.

2026-06-210

solid-srp

developerz-ai/ai-designer

SolidJS + single-responsibility conventions for the side-panel UI — one component per file with co-located SCSS, thin stores, no logic in components. Use when creating or editing anything under src/entrypoints/sidepanel, Solid components, signals/stores, or SCSS.

2026-06-210

test-extension

developerz-ai/ai-designer

Testing patterns for the extension — Vitest unit + integration projects and Playwright E2E on a loaded extension. Use when writing or fixing tests, setting up mocks for the agent loop / DOM tools / MCP, or when CI test jobs fail.

2026-06-210

name	ship
description	Assemble an accepted changeset and dispatch the implementation handoff over MCP to ai-dev / developerz.ai. Use when touching src/mcp, the ship flow in src/entrypoints/background.ts, or when the task mentions handoff, shipping a design, MCP task creation, or turning edits into a PR.

Ship turns a Changeset into a real code task. Runs in the service worker (owns keys + MCP clients). See docs/idea/handoff.md, docs/idea/mcp.md, docs/architecture/handoff.md.

Rules

User-triggered only. Never auto-ship. "Ship" is an explicit button → ship message. The agent never calls handoff on its own.
The changeset is the spec: intent + stable selector + frameworkHints map the visual change to source.
MCP client lives in the service worker. Connect via @ai-sdk/mcp createMCPClient over Streamable HTTP (not SSE). See docs/reference/agent-sdk.md.

Flow

Assemble + validate the Changeset (Zod, src/shared/changeset.ts). Refuse empty/invalid.
Resolve the configured backend + auth token (ai-dev: admin/worker key or OAuth user token).
Open the MCP client, call task with action: 'create', changeset as the task spec.
Stream status back to the panel; surface the PR link when the dev-agent opens it.
On failure: report the MCP error to the panel, keep the changeset (don't discard the user's work).

Don't

Don't persist mutations to any server — the only durable output is the changeset → PR.
Don't embed keys/tokens in the changeset or any content-script message.