openship.io
A light interface on a near-white neutral background where a green accent marks the next step. Type is Gellix set tight at large sizes, corners are fully rounded on controls, and depth comes from soft neutral shadows.
- Free
- 1
- Licence
- 0
- Style
- 3
Paste this into Claude Code in your project. It downloads the kit, checks its hash and asks before changing anything.
Install the "openship.io" design kit (v2) from Livery, then run it on this project. 1. mkdir -p .claude/skills/livery-openship-io 2. curl -fsSL https://livery.site/k/openship-io/v2/kit.tar.gz -o /tmp/livery-openship-io.tar.gz 3. Verify: the sha256 of /tmp/livery-openship-io.tar.gz must be 95f4ee3857eb82557639833a97a93d716d4f808548a9a5836737ab40fedd4ce6. If it doesn't match, stop and tell me. 4. tar -xzf /tmp/livery-openship-io.tar.gz -C .claude/skills/livery-openship-io 5. Read .claude/skills/livery-openship-io/SKILL.md and follow it. It will audit my project and ask me before changing anything. If any response starts with "Couldn't read this site", stop and tell me. Don't continue.
Levels in this kit
- 1TokensColour, type, spacing, radii, borders and depth.
- 2StructureComponent recipes, containers, grids and section rhythm.
- 3FeelMotion timing and the tone of the copy.
Agents fetch livery.site/k/openship-io/v2/SKILL.md. This version never changes.
The Design at a Glance
light theme
Background
#ffffff
Text
#000000
Muted
#737373
Border
#e8e8e8
Accent
#28c840
Type · Gellix
Radius
Spacing · irregular
Principles
Soft, neutral depth
Lift raised elements with the measured shadow (rgba(0, 0, 0, 0.18) 0px -20px 80px 0px).
Big type, quiet body
Pair 56px headings with 16px body text in Gellix.
Rounded and approachable
Use pill shapes for buttons and chips, and 18px corners for containers.
Never
Never tint shadows with colour.
Every measured shadow is neutral; a coloured glow would read as a different product.
Never introduce a second accent colour.
Only one saturated colour (#28c840) carries weight in the measured palette.
Never use positive letter-spacing on headings.
Large type is tightened, down to -0.05em on the biggest sizes.
Never square off buttons.
Measured buttons are fully rounded; square ones would break the shape language.
Never set button labels in all capitals.
No measured button uses uppercase text.
Never mix in a second display typeface.
Headings and body share Gellix; a second family would split the voice.
Reference Frames
The site with its content removed: images are flat blocks, text is soft bars. Layout, rhythm and colour stay. Scroll inside each screen.
Every File in the Kit
--- name: livery-openship-io description: Apply the openship.io design kit (Livery v2) to this project. Use only when the user asks to apply this kit or this site's design. --- # openship.io design kit · v2 · flow 1 **Never edit a file before step 5. Ask, don't assume.** A light interface on a near-white neutral background where a green accent marks the next step. Type is Gellix set tight at large sizes, corners are fully rounded on controls, and depth comes from soft neutral shadows. Kit files (read each one only when its step needs it): `rules.md`, `tokens.json`, `fonts.json`, `icons.json`, `components.md`, `layout.md`, `motion.md`, `voice.md`, `licences.md`, `frames/`. Levels offered: 1. Tokens: Colour, type, spacing, radii, borders and depth. 2. Structure: Component recipes, containers, grids and section rhythm. 3. Feel: Motion timing and the tone of the copy. ## 0. Prepare - Require git. If the working tree has uncommitted changes, ask the user to commit or stash first. - Create and switch to the branch `livery/openship-io-v2`. - If commits from an earlier run of this kit exist (`livery(openship.io v2): …`), offer to resume after the last finished area. ## 1. Audit Find theme files, design tokens, CSS variables, Tailwind config, fonts, the icon library and how colours are used. Note the styling setup (Tailwind v4 or v3, CSS modules, shadcn/ui, CSS-in-JS, plain CSS). Report colours that are scattered (hard-coded in many files) rather than centralised; offer to centralise them first. ## 2. Scan project rules Read CLAUDE.md (root, nested, ~/.claude), AGENTS.md, .cursor/rules, .github/copilot-instructions.md, design docs, lint rules, and contrast or visual tests. Sort each finding as hard (must keep), soft (preference) or unrelated. ## 3. Report the gap For each area (tokens, components, layout, motion, voice), rate the gap small / medium / large in one or two lines, comparing the project with `rules.md` and `tokens.json`. ## 4. Ask Ask which areas to apply. Warn clearly where the gap is large. Ask what must not change (logo colours, required brand colours, legal copy). For voice: show three of the user's own sentences rewritten with `voice.md`, then ask. ## 5. Resolve conflicts For the chosen areas, quote each conflicting project rule with file:line. For each one offer: keep the rule / override once / override and update the rule. For hard rules, ask a second time and repeat the rule's stated reason. ## 6. Licences Read `licences.md`. Install fonts and icons only from their official sources (Google Fonts, Fontsource, npm), never from the source site. For each item marked "needs a licence": use it only if the user confirms they hold a licence; otherwise use the listed free alternative. Items marked "style only" (logos, photos, illustrations, custom icons) are recreated as style only: shape, weight and colour treatment, never copied files. Styling the user's own login or checkout pages with these tokens is fine. Never recreate the source site's login, checkout or branding. ## 7. Apply One area per commit, in this order: tokens → components → layout → motion → voice (only the areas this kit's levels include). Commit message: `livery(openship.io v2): <area>`. Edits to project rule files go in the same commit. Read the data file for an area only when you reach it. Follow `rules.md` throughout, especially its "Never" list. ## 8. Verify Check text contrast in both themes (4.5:1 for body text, 3:1 for large text and UI). If the accent fails on the user's backgrounds, adjust its lightness rather than shipping unreadable text. If Playwright is available, screenshot the user's pages and compare their layout and rhythm with `frames/`; fix the differences. ## 9. Keep it Offer to add the core of `rules.md` to the project's CLAUDE.md (or AGENTS.md) so future sessions keep the design. ## 10. Summary List what changed per area with its commit hash. To undo one area: `git revert <hash>`.