design-ship
FeaturedOne-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to disk, run /ork:design-import instead.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- yonatangross
- Repository
- yonatangross/orchestkit
- Created
- 8 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship instead.
ship
Explicit-invocation-only orchestrator that takes a completed `.design/YYYY-MM-DD-<slug>.md` to a review-ready PR, unattended — branch off main, draft PR, build per phase, browser-test, warm review, fix, cold review of the whole PR in a fresh session, fix, flip to ready. Use ONLY on /ship or an explicit "ship this", "run the ship pipeline", or "build and open a PR unattended". DO NOT auto-trigger from talk about branches, PRs, building or reviewing — those have their own skills.
ship
Push a committed feature branch, open a PR, watch CI, and (only on explicit confirmation) squash-merge and clean up. Use when the user says "ship this", "push and open a PR", "is CI green yet", or asks to merge a PR that's already open. Assumes the branch is already committed — this skill does not stage or commit anything. Does not require ending at a merge: an open, CI-green PR is a valid stopping point.