Agent skill · design visual · yonatangross
design-ship
Turns a claude.ai/design link into a PR: design-import, then cover, then expect, then open the PR. Use when a design should come back as a PR. For files on disk only, use design-import.
Why this skill is useful
Adds a complete executable pipeline for turning design handoff URLs into GitHub pull requests, automating multiple steps that the AI cannot generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-06. 215 stars on the source repository.
What this skill does
Design Ship One command: Claude Design handoff URL → reviewable GitHub PR. Standalone Claude Design closes by 2026-12-14 (CC 2.1.302 adds this notice to /design-sync and /design-login). After that date a claude.ai/design handoff URL may stop resolving. Export the bundle to a local file now and pass the file path, which this skill accepts. When to use You have a Claude Design handoff URL (or file) and want a PR opened against the current branch. No intermediate steps, no manual test generation, no manual PR drafting. For just-the-import (no tests, no PR), use design-import instead. Pipeline Pre-flight Before starting the pipeline, verify the working tree is clean enough to ship: Phase 1 — Import Set bundlesource from the argument first, so Phase 4 can link it for either input: URL input: bundlesource is the handoff URL as given. Local file input: bundlesource is the source URL the bundle file records, else the file path. Delegate to design-import with the bundle argument. Capture its output (the import manifest): it includes the bundleid, list of components written, and the provenance file path. If import fails, stop. Do NOT proceed to test generation against partially-imported components. Phase 2 — Cover Run cover scoped to the components written by phase 1: Phase 3 — Expect Run expect to do diff-aware browser verification. This produces the screenshots that go into the PR body: Phase 4 — Create PR Use create-pr with a body templated from the bundle and verification results: Phase 5 — Update provenance Patch the provenance file with the opened PR number and URL: Failure modes Phase Failure Behavior --- --- --- Pre-flight Dirty tree, on main AskUserQuestion, do not proceed silently 1. Import Schema deviation, token conflict design-import already prompts; if user cancels, abort 2. Cover Test generation fails Continue to expect — tests are recoverable in PR review 3. Expect Browser verification fails Continue to PR — failures noted in PR body 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yonatangross/design-ship--bd2bd9