It reads your codebase before it writes.
Connect a repository and Shipd explores it like an engineer would, builds an Architecture Brief, and generates code that reuses your real components, tokens, and conventions. Not scaffold primitives.
Four steps, before a line of code.
$ shipd explore acme/web ✓ Framework Next.js (App Router) ✓ Components 8 detected · Button, Card, Nav ✓ Tokens Tailwind config + theme ✓ Fit mode Vendor — reuse real components Ready. New code will match this architecture.
Choose how closely it hugs your code.
Pick per build. From matching your style to reusing your actual components.
Style-match
Generate fresh code that matches your look and patterns, without importing your components.
Vendor
Import and reuse your real components, not scaffold primitives, so output drops straight into your app.
Repo
Generate against the whole repository, wiring into your existing modules and structure.
Real engineering, not keyword search.
Agentic exploration
A Claude-Code-style tool loop navigates your repo, following imports and reading the files that matter.
Code-specialized retrieval
Your code is embedded with Voyage voyage-code-3 into a 1024-dim pgvector index, with asymmetric query and document search.
Architecture Brief
A concise, structured brief drives every build, so generations stay consistent with your repo.
A repo, or a ZIP. That is it.
Point it at your repo.
Connect a repository and see your first codebase-aware build. Free to start.
Further reading: What "codebase-aware" AI generation actually means