Real features designs you can copy into Claude Code. Claude Code turns a pasted template into code in whatever stack your project already uses, from plain HTML to Next.js or SvelteKit. Below: the designs, how to set Claude Code up so it keeps the design, and what makes a good features section.
82 features design templates for Claude Code. Browse the full BrowserMoon library for every template category.
48 of 82
Pick a design
Choose a features design above and open it to see it live.
Copy the template
Copy the template from its page. It is one HTML file with no dependencies.
Set up Claude Code
Save the template in your repo, for example as design/template.html, and point to it from CLAUDE.md so Claude Code reads it at the start of every session.
Prompt, then refine
Paste it and describe your product. Then follow up with: "Rebuild this section in our stack using design/template.html. Keep its spacing, type sizes and colours exactly; change only the text."
Common types: bento grids, alternating rows of text and screenshots, icon grids and tabbed feature sections.
Each block says what the visitor can now do.
A screenshot or small demo per feature makes it real.
Short headings and two-line descriptions.
Common mistake: Grids of icons with vague one-word labels. Features section design ideas →
Claude Code works in your terminal on a real codebase, so it suits developers who want the design built into an existing project and kept consistent across many sessions.
Code in whatever stack your project already uses, from plain HTML to Next.js or SvelteKit.
Save the template in your repo, for example as design/template.html, and point to it from CLAUDE.md so Claude Code reads it at the start of every session.
Without a rule in CLAUDE.md, later sessions drift back to generic spacing and colours. Paste the template again with your follow-up prompt if it starts to drift.
Keep the grid or bento layout, and write each feature as a benefit in under fifteen words.
Set it up once with our CLAUDE.md design template.
A full landing page for a SaaS product: hero, logos, features, how it works, pricing, FAQ and a closing call to action.
Template: Pixel SaaS landing page
“Build a landing page for [product name], a SaaS product that helps [audience] [main outcome]…”
More in Claude Code prompts.
Ask Mon, the AI design assistant, describe your product and Mon suggests the features design and how to prompt Claude Code with it.
Paste the template code into your Claude Code session and tell it what to build around the design. Save the template in your repo, for example as design/template.html, and point to it from CLAUDE.md so Claude Code reads it at the start of every session.
Code in whatever stack your project already uses, from plain HTML to Next.js or SvelteKit.
Without a rule in CLAUDE.md, later sessions drift back to generic spacing and colours. A follow-up prompt that helps: "Rebuild this section in our stack using design/template.html. Keep its spacing, type sizes and colours exactly; change only the text."
Benefits, not just features: each block says what the visitor can now do. Something to look at: a screenshot or small demo per feature makes it real. Easy to scan: short headings and two-line descriptions.
Without a rule in CLAUDE.md, later sessions drift back to generic spacing and colours. Paste the template again with your follow-up prompt if it starts to drift.
More Claude Code template categories
Features templates for other tools