ux-ship

Runs the release-gate ship mode of the nadav-design skill for pre-release measurement.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Nadav011/nadavai-claude --skill ux-ship-nadav011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-ship
Source: https://github.com/Nadav011/nadavai-claude/tree/main/plugins/nadavai/skills/ux-ship
Command: npx skills add https://github.com/Nadav011/nadavai-claude --skill ux-ship-nadav011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing a UI project for release requires a disciplined gate: verifying evidence, running measurements, and confirming readiness step by step. This Skill provides a dedicated shortcut that routes directly into the ship mode of the nadav-design workflow so nothing is skipped before launch. ## Core Features & Use Cases - Release Gate Execution: Invokes the ship mode of the nadavai:nadav-design skill, walking through each release step with evidence after every step and stopping on failure. - Deterministic Delegation: Always loads the master skill from the same plugin and version, with a documented fallback that reads the nadav-design SKILL.md directly if the Skill tool cannot load it. - Use Case: Nadav finishes a UI iteration and types /ux-ship to run the release gate, confirming measurements and readiness checks pass before shipping the feature. ## Quick Start Type /ux-ship followed by any release context to run the ship mode release gate for the current UI project.

Frequently Asked Questions about ux-ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the release gate before shipping a UI feature?

Type /ux-ship with any release context. The skill invokes the ship mode of nadavai:nadav-design, which walks through each release step one at a time, records evidence after every step, and stops immediately on failure.

What is the difference between ux-ship and nadav-design?

ux-ship is a shortcut that only runs the ship mode of the nadav-design skill. nadav-design is the master skill containing all modes of the UI/UX loop, while ux-ship always delegates to it with the ship argument.

What happens if the nadav-design skill fails to load?

The skill falls back to reading the nadav-design SKILL.md file directly from the plugin directory and follows its Hard rules and Mode ship section verbatim. It never looks for the master skill anywhere else.

Does ux-ship make code changes during the release gate?

No, the ship mode is measurement only. It verifies release readiness through evidence-based steps and stops on failure rather than modifying the project.

When should I not use ux-ship in the UX workflow?

Do not use it before earlier loop stages are complete. ux-ship is the final release gate, so setup, planning, screen design, and audit steps should be done through their own commands first.