FrameShelf
Complete pages. Original ideas.
FrameShelf / Practical guide

Vibe coding templates. Start with a real design.

Use a working landing page as the starting point for AI-assisted coding. Explore the preview, download an available source package, then ask your coding tool to make focused changes.

Two free starters, different workflows.

Choose the project format you want to work with. Neither sample requires you to purchase premium access.

HTML / CSS / JavaScript

Orbit — a dark SaaS landing page

A product-led starting point with a dashboard preview, feature sections and pricing. Its source is a single HTML page with embedded styles and JavaScript, plus a README and licence.

Start here if: you want a page you can inspect and edit without installing a framework.

Run it: extract the ZIP and open index.html. Follow the README’s local-server instructions for clipboard features. Google Fonts need an internet connection; fallback fonts are included in the styling.

Get Orbit source Preview Orbit
React / Next.js

AFTERHOURS — an editorial product page

A sneaker campaign with product imagery, a gallery and a demo shopping bag. The download contains a Next.js project, local product assets, setup instructions and a licence.

Start here if: you want to work with components and extend a product-storytelling layout.

Run it: extract the ZIP, follow the README’s Node.js requirement, then run npm install and npm run dev. The demo bag does not process orders or payments.

Get AFTERHOURS source Preview AFTERHOURS

From source files to your own landing page

  1. Inspect the whole preview. Check the page structure and mobile layout. Pick a design that suits your content, not just a hero you like.
  2. Read the Source tab. Confirm the stack, files, licence and access status. Download and extract the available package into a new folder.
  3. Run the unchanged project first. Follow its README and compare it with the preview. This gives you a baseline before an AI tool edits the code.
  4. Give the tool the project and one clear task. Ask it to inspect the existing files, preserve the framework and explain its changes. Start with your headline, product description and button destination.
  5. Review each change. Check the diff, run the page again and inspect the result at desktop and mobile widths. Save a working version before adding another change.

A useful first instruction for your AI tool

After opening the extracted source in your coding tool, replace the bracketed text below with your own content. This is a customisation instruction for files you already have, not a prompt to reproduce a locked template.

Inspect this project and its README before editing.
Keep the existing framework, layout and responsive behaviour.

Change the headline to: [your headline]
Change the introduction to: [your product description]
Set the primary button text and URL to: [label and destination]

Reuse existing components and styles. Do not add dependencies
or invent testimonials, performance claims or working services.
Explain which files changed and how I can check the result.

Avoid pasting passwords, API keys or private client data into an instruction. Configure services through the project’s documented environment settings when you are ready to connect them.

Need a section instead of a complete template?

Use a reusable section when your page already has a structure. The free section collection includes a hero, features, pricing, FAQ and footer. Check each package’s dependencies and how its styles interact with your existing page.

For a full animated page, compare the animated landing page collection. Motion should remain understandable on mobile and with reduced motion enabled. Browsing an animation does not imply its source is free.

Before you publish your adaptation

  • Replace fictional brands, quotes, figures and campaign copy with your own accurate content.
  • Check links, forms, keyboard controls and page overflow at narrow widths.
  • Connect and test any real account, email or payment service. Demo interactions are not a backend.
  • Run the package’s build command where applicable and review the downloaded licence.

See How to use FrameShelf for preview, prompt and source details, or contact us with the template name and the setup step that failed.

Vibe coding template questions

What are vibe coding templates?

They are existing website layouts you can use as the starting point for AI-assisted coding. Instead of asking a tool to invent every detail, give it the available source files and describe a specific change. You still need to review and test the result.

Do I need a particular AI coding tool?

FrameShelf downloads are source files, not an integration with a specific AI service. Use a tool that can work with the downloaded project’s language and files. Check its file-access and project requirements before uploading or importing a package.

Will copying the prompt recreate the preview exactly?

No. Different tools can interpret the same instructions differently. Start from the source package when you want to preserve the implemented layout. A prompt is useful for describing a direction or requesting changes; it is not a substitute for the files.

Can I download every template for free?

No. Orbit, AFTERHOURS and selected sections are free samples. Other source packages and full prompts remain premium, and paid checkout is not open. Each design’s Source tab shows what is available.

Are these WordPress themes or Framer imports?

No. The samples described here are HTML/CSS/JavaScript or React/Next.js source projects. They are not installable WordPress themes or native Framer templates. Check the package requirements before choosing a hosting workflow.

FrameShelf

Explore the library

Build something

Learn & support

Browse by industry
Your ideas. A head start.

Combine a few good sections into a page that feels like you.

Try the composer
A little help getting started