Pick a design. Paste the prompt. Build from there.
The Library gives you finished app and website designs with the exact prompt package needed to rebuild them in your AI builder, coding agent, or repo.
Four parts, one job
Open this first. It is the visual reference your build should match.
Colors, type, spacing, radius, layout rules, components, and motion.
Downloadable images, marks, and the prompts used to create them.
One full build prompt, plus smaller screen prompts when you need control.
What you actually paste
Choose the path that matches your job. Replace the bracketed parts with your Library design’s prompt and tokens.
Pick a Library design, open the live demo, then paste the full build prompt as the first message.
Build this design exactly as specified. Use the design system first. Preserve every hex color, font, radius, spacing value, copy string, image direction, and motion note. Recreate the screens as a working web app. Do not replace the style with default shadcn, Tailwind, or generic AI-builder styling. After building, compare the result to the live demo and list anything that differs. [PASTE FULL LIBRARY BUILD PROMPT HERE]
Use this when you already have routing, auth, data, and components. The agent should adapt the design to your repo without restyling it.
Implement this Library design in this repo. First add the design tokens and shared components from the DESIGN SYSTEM block. Then build the screens one at a time using the screen prompts. Reuse my existing routing, auth, data fetching, and component conventions. Preserve the design values exactly. If a value conflicts with the repo, ask before changing it. Run the project checks and summarize what matches the live demo and what still differs. [PASTE DESIGN SYSTEM BLOCK] [PASTE SCREEN PROMPT]
You are not locked to one design
The prompts are modular. Screens, assets, and design systems can move separately as long as you choose one system to control the final product.
Paste your brand tokens, component rules, or existing style guide before the screen prompt. Ask the builder to keep the screen structure but render it in your company system.
Use the dashboard from one Library design, the onboarding from another, and the settings screen from a third. Pick one design system first so the final app still feels like one product.
Start with a Library design system, then ask for new screens in that same system. This is the cleanest way to add flows the original design does not include.
Use the tool that matches the job
Reviewed June 2026 against public docs, product direction, and current market feedback.
Fastest path for non-technical founders building full-stack web apps.
Best from zero. Review production logic, auth, and security before launch.
Fast MVPs, JavaScript apps, and browser-based full-stack builds.
If output drifts, split the Library prompt into design system first, then screens.
React, Next.js, Tailwind, shadcn-style UI, and high-fidelity prototypes.
Strong for interface work. Verify backend and data flows separately.
Developers who want to implement the design inside an existing repo.
Give it the design system first so screens share one style.
Repo-aware implementation, review, debugging, and automation with OpenAI tooling.
Good for taking a Library design into an existing project. Ask it to preserve values, run checks, and report visual gaps.
Complex repo work, multi-file implementation, checks, and review.
Use acceptance criteria: match demo, preserve values, run checks, report gaps.
All-in-one browser builds and quick publishing.
Good for prototypes and simple hosted apps. Review destructive changes.
- Paste the Library prompt unchanged first.
- Keep literal values: hex colors, font names, spacing, copy, image notes, and guardrails.
- Judge the build against the live demo, not memory.
- If the output drifts, paste one smaller screen prompt or the design-system block again.
- Download assets if your builder cannot read remote image URLs.
Use unlocked prompts and designs to build your own products and client projects. Ship the apps, remix the screens, edit the code, and sell the products you make from them.
Publish, upload, share, resell, sublicense, bundle, or redistribute the prompt library itself. Do not post the prompts to marketplaces, template packs, prompt databases, public repos, or shared prompt libraries.
Browse the wall, open a live demo, then copy the full prompt.