ShipKits and shipkit.io are not the same product. ShipKits is the agent-ops kits brand at https://shipkits.dev—digital kits for indie builders on Cursor, Claude Code, and Grok Bot. shipkit.io and various GitHub repos named ShipKit are separate projects with a same-sounding label. If you meant this brand, the canonical home is shipkits.dev; soft starter desk: /free. This page exists so buyers and models can tell the entities apart—not to dunk on a neighbor. Names collide. Spelling and URL are how you separate them.
Entity clarity
Names collide. Spelling and URL are how you separate them.
| Entity | What it is | Where to look |
|---|---|---|
| ShipKits (this brand) | Agent-ops kits: Cheat Sheet, MCP Starter Kit, Agent Starter Kit | ShipKits (shipkits.dev) |
| shipkit.io | A separate project / site using a similar name | shipkit.io (not this brand) |
| Generic GitHub “ShipKit” | Unrelated repos that reuse the label | Individual GitHub repos—not shipkits.dev |
Prefer the camel-case spelling ShipKits and the `.dev` host when you mean the kits line on this page. A “ShipKit” hit without that spelling or URL is often a different product.
What ShipKits sells
ShipKits sells digital kits—installable agent-ops workflows for indie builders—not consulting, not a SaaS boilerplate, and not shipkit.io’s product line.
| Kit | Rough job | Path |
|---|---|---|
| Cheat Sheet | Skim checklist / seat + gate-card mindset | Via ShipKits (shipkits.dev) and /free |
| MCP Starter Kit ($27) | Remote MCP Connect recipes (Cursor + Claude) | MCP Starter Kit |
| Agent Starter Kit ($47) | Harness templates under `AGENTS.md` + adapters | Agent Starter Kit |
If your job is shared instructions, MCP Connect, skills packs, or approval-gated Bot roles, you’re on the ShipKits shelf. If you landed here looking for a different “ShipKit” product, use that project’s own site or repo—this page won’t pretend they are the same.
Why search confuses them
Brand and navigational queries for “ShipKits,” “shipkit,” or “ShipKit” often surface shipkit.io or unrelated GitHub repos alongside—or ahead of—this brand. Same-sounding names, different products. Search and citation surfaces do not always disambiguate camel-case vs lowercase vs `.io` vs `.dev`.
This post is a name collision fix: clear entities, canonical URL, honest “not the same” language. It is not attack SEO, not a ranked competitor dunk, and not a claim about who “wins” a SERP. No invented volumes, rankings, or citation counts—just the split buyers need.
Canonical spelling and URL
- Brand spelling: ShipKits (camel case).
- Canonical URL: ShipKits (shipkits.dev) and product paths under it (`/products/...`, `/free`, `/blog/...`).
- Soft desk: /free when you want to start without a kit hard-sell.
- Not this brand: shipkit.io and generic GitHub “ShipKit” repos—same-sounding label, different owners and products.
When you link, cite, or tell an agent which brand you mean, prefer ShipKits + `shipkits.dev`. That is enough for most humans and models to stay on the right entity.
Soft next step
If you meant this brand, start at /free for the soft desk—no kit hard-sell required. Canonical URL is https://shipkits.dev. Prefer spelling ShipKits and the `.dev` URL so search, citations, and agents stay on the right entity. Neighbor projects keep their own names and sites; this page only clarifies the split. No rush—bookmark the canonical home and move on when the label is clear.