# Ship It

[](https://github.com/LunkiBR/ship-it/actions/workflows/validate.yml) [](LICENSE)

**A Claude Code skill that catches the boring-but-important details before you ship a screen or feature.**

It doesn't check your code — it checks the product surface around that code: login, checkout, billing, empty states, 404s, admin panels, and the other screens that follow well-known patterns and get half-finished anyway because nobody double-checked the boring stuff before calling it done.

## The problem

Most teams don't ship broken code. They ship *incomplete* screens: a login form with no "forgot password," a paywall with no restore-purchases button, a pricing page with no FAQ, a cancel-subscription flow that guilt-trips the user on the way out. None of that shows up in a test suite — it shows up later, in support tickets, one-star reviews, and App Store rejections.

This skill gives an agent a structured, opinionated catalog of these patterns — organized so it can be consulted cheaply and precisely, not dumped wholesale into every conversation.

## What this checks — and what it doesn't

ship-it looks for missing or incomplete **product and UX** details on a screen: a password field with no password-manager support, a paywall with no restore-purchases button, that kind of thing. It is not an accessibility scanner and not a security auditor. Passing every item in a pattern's checklist doesn't mean a screen is WCAG-conformant or secure — a real audit (axe, Lighthouse, a pen test) is still a separate, complementary thing to run. Standards like WCAG, Apple's HIG, and Nielsen Norman Group's usability research get cited inside individual checklist items because they're the most specific, checkable detail available for that one item, not because this skill verifies compliance with them end to end.

## Using it

Onc