A starter kit built
for how you ship now.
AI tools write the code. duply gives them the context: a real, finished product surface and the exact design language to build it in, so the first prompt ships something that works.
From a real design to your product.
One file carries the look, the kit carries the build. Together they turn a plain-language prompt into a finished screen.
We read a production site and distill it into one DESIGN.md: color roles, the type scale, spacing and radius, the whole visual language as tokens.
Drop the kit and its DESIGN.md into Claude Code, Cursor or Codex. It already knows the stack, the screens, and where every integration plugs in.
Every screen renders complete on mock data. Describe a change in plain language, wire one integration at a time, and go live.
A whole product, already built.
The screens a real app needs are here on day one, clickable on mock data, each one wired the moment you add a key.
Login, social and roles, all behind one marked seam.
A pricing page, checkout, portal and billing screens.
An assistant and semantic search, bring your own provider.
Blog, docs, sitemap, LLMO and the legal pages.
Transactional email, a newsletter and contact forms.
Consent-gated GA4 and product events out of the box.
Independent by design
Each DESIGN.md is our own reading of publicly visible design choices, with no affiliation to the tools we cover. You get the source and the context your AI tool needs, nothing borrowed.
Finished, not flexible to a fault
Nothing is half-built and nothing says "coming soon". Every integration sits behind one seam with a skill that tells your AI tool exactly how to wire it.
See it running, then make it yours.
The fastest way to understand duply is to click through the demo, then hand the kit to your AI tool.