Ship It

Use this skill whenever building, reviewing, or auditing any product surface — a mobile app screen, a web app (in-product) screen, a marketing website page, or a cross-screen interaction flow — especially right before calling it done or shipping it. Start here to identify which section (mobile app, web app, website, flow, and more as they're added) the surface belongs to, then drill down to name every pattern (login, checkout, billing, pricing, admin panel, empty state, and more) it should have and flag which are missing — weighed against what this specific product actually is, never applied a

19 stars 1 forksMobile Development

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add LunkiBR/ship-it --skill ship-it

Manual install

git clone --depth 1 https://github.com/LunkiBR/ship-it.git /tmp/ship-it
mkdir -p ~/.claude/skills
cp -r /tmp/ship-it/. ~/.claude/skills/ship-it

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Ship It

Catalog of product/UX patterns — one section per surface type (mobile app, web app, website, flow, more to come), one file per pattern within a section. Never load a pattern file, or a section you're not working in, before you need it.

## Steps

1. **Build a one-line picture of the product** — what it does, who it's for, and which capabilities it actually has (sells something, runs subscriptions, accepts uploads, has teams/multi-user accounts). Pull this from the code, README, or prior conversation first; ask the person directly only for the specific unknowns that would change a judgment call (see Judgment calls). This picture is what step 3 is weighed against — skipping it is what turns a checklist into noise.
2. **Identify the section(s) in scope** — mobile app, web app, website, flow, or a section added later (see `sections/`). A task usually touches one section; ask only if genuinely ambiguous.
3. **Open that section's index** (table below) and, from its pattern names, tiers, and one-liners alone, list which patterns the current project already has, is currently building, or lacks outright. Start from each pattern's tier as the default assumption, then weigh it against the picture from step 1 before naming a gap — see Judgment calls. Don't open a pattern file for this step.

Read the full skill on GitHub

Details

Skill name: ship-it
Repository: LunkiBR/ship-it
License: MIT
Repo updated: 9 August 2026

FAQ

What does the Ship It skill do?

How do I install the Ship It skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add LunkiBR/ship-it --skill ship-it. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Ship It popular?

It lives in LunkiBR/ship-it, which has 19 GitHub stars and 1 forks.

Related skills

Swift Patterns

efremidze/swift-patterns-skill

Review, refactor, or build SwiftUI features with correct state management, modern API usage, optimal view composition, navigation patterns, performance optimization, and testing best practices.

Mobile DevelopmentIn 1 list

Shadertoy to Flutter

FlutterFlow/shadertoy_to_flutter_skill

Convert Shadertoy GLSL fragment shaders into Flutter-compatible GLSL fragment shaders (.frag files) for use with Flutter's FragmentProgram / FragmentShader API, Impeller, or the material_palette "fill shader" / "wrap shader" pattern. Use whenever the user pastes a Shadertoy shader (or points to one on shadertoy.com) and wants to run it in Flutter, asks to port or adapt a fragment shader to Flutter, mentions making Shadertoy-style uniforms (iResolution, iTime, iMouse, iChannel*, mainImage, fragCoord) work in Flutter, or has a .frag file that won't compile in Flutter because of Shadertoy-style c

Mobile Development

Adb Android Control

hah23255/adb-android-control

Comprehensive Android device control via ADB (Android Debug Bridge). Use when user asks about: Android device management, app installation/uninstallation, APK operations, package management, file transfer (push/pull), screenshots, screen recording, input simulation (tap/swipe/text/keyevents), shell commands, logcat viewing, device info (battery/memory/storage), automation scripts, wireless ADB connection, scrcpy mirroring. Keywords: adb, android, phone, tablet, device, apk, install app, uninstall app, screenshot, screen record, tap, swipe, type text, keyevent, logcat, push file, pull file, she

Mobile Development

Swiftui Autotest Skill

yusufkaran/swiftui-autotest-skill

AI-powered visual testing and accessibility setup for iOS/SwiftUI apps. Build, launch in Simulator, test with computer use, detect crashes, analyze memory leaks, and add accessibility identifiers — all from the terminal.

Mobile Development

Burner

useburner/burner

Use when the user says "use my burner", "on my burner", "what's on my burner?" (screenshot its screen and send the image), or asks you to do something in a phone app (open an app, tap, type, scroll, check an order). burner gives you a real Android phone the user set aside for you, for apps with no API or website you can automate. Also covers first-time setup.

Mobile Development

Swift Focusengine Pro

mhaviv/Swift-FocusEngine-Agent-Skill

Reviews, writes, and fixes focus management code for all Apple platforms (tvOS, iOS/iPadOS, watchOS, visionOS, macOS), covering SwiftUI, UIKit, AppKit, and RealityKit. Use when reading, writing, or reviewing apps that handle focus, hover, key view loops, or Digital Crown navigation.

Mobile Development

Browse the most popular Claude skills, all mobile development skills, or write your own with the skills generator.