Introduction
Use human-curated design resources as exact HTML starting points or as design context your coding agent can translate into any stack.
Wish Themes exists because generating code and making good design decisions are different jobs. A coding agent can implement almost anything, but it works better when it receives concrete visual proof, design tokens, layout rules, component anatomy, interaction guidance, and the reasoning behind those choices.
Each published resource gives you a visible implementation and the context needed to preserve its intent. You can use Wish Themes without AI, and you are never locked into a framework.
What you get
A published theme will be useful to both a person and a machine. The planned release unit contains three files:
design.md Design source of truth Tokens, hierarchy, components, responsive behavior, accessibility, content, and rationale.
index.html Working reference A complete, dependency-light implementation you can open, inspect, edit, and deploy.
thumbnail.webp Catalog preview A compact image used to recognize and compare published resources in the catalog.
Tailwind variants, RECOMMENDATIONS.md, and
AGENTS.md are part of the planned expanded bundle.
Quick start
Start with a published resource, or use the catalog to find and support the planned use case you need most.
- 1 Open the catalog
Visit the catalog and search for the product surface, component, or asset you need.
- 2 Review its planned scope
Use the title, category, and description to confirm that the intended information model fits your product.
- 3 Signal demand
Open the wishlist to support an existing request or propose a missing use case through GitHub.
- 4 Return when it ships
Released cards will lose the Planned watermark and provide their implementation, design specification, and preview.
Choose a workflow
Use the HTML directly
Choose this when the page already matches your use case and you want a static, readable starting point.
Follow the HTML workflow →Translate with an agent
Choose this when your product already uses React, Vue, Svelte, Laravel, or another application stack.
Follow the agent workflow →Browse and search
Search by the product you are building, not by a vague visual
adjective. Useful queries include CRM,
developer portfolio, checkout,
medical dashboard, or file upload.
Catalog search expands related concepts and tolerates partial
words and common typos. For example, a search for
login can surface authentication, password, OTP,
sign-in, and SSO resources.
Use the HTML directly
Released index.html files keep markup, styles, and
interactions together. This makes them easy to read and simple to
move into a new folder.
curl -L https://wishthemes.com/theme-files/RESOURCE_SLUG/index.html \
-o index.html
open index.html- Replace the fictional product name, copy, navigation, links, and calls to action.
- Update design tokens before changing individual selectors so the system stays coherent.
- Keep the semantic landmarks, focus states, responsive rules, and reduced-motion behavior.
- Test the result at mobile and desktop widths before deployment.
Use it with an AI coding agent
Give the agent both files. Tell it that design.md is
the source of truth for intent and that index.html is
the reference for visual verification.
Read design.md first and treat it as the source of truth for the
design system, layout, responsive behavior, components, and interaction
rules. Use index.html as the visual reference implementation.
Rebuild this design in my existing stack. Preserve the information
hierarchy and design intent, adapt the content to my product, reuse my
project conventions, and do not paste the original HTML blindly.
After implementation, verify desktop, mobile, keyboard navigation,
focus states, and reduced-motion behavior.Adapt without losing the design
Start with the system, then move toward details. This produces a more coherent result than editing isolated colors and margins.
Map the reference sections and objects to your real product.
Change color, typography, spacing, radius, and elevation centrally.
Preserve anatomy and states while adapting labels and data.
Review responsive behavior, accessibility, motion, and content density.
Bundle reference
In the repository, every release is self-contained under
src/content/themes/<slug>/. Its metadata,
implementation, design specification, component reference, and
thumbnail live together so a theme can be reviewed, moved, or
extended without chasing files across the project.
src/content/themes/inventory-warehouse-admin/
├── index.md
├── index.html
├── components.html
├── design.md
└── thumbnail.png| File | Purpose | Status |
|---|---|---|
design.md | Design intent and system specification | Available |
index.html | Complete reference implementation | Available |
components.html | Selective component and interaction reference | Available |
thumbnail.png / .webp | Catalog preview image | Available |
bundle.zip | Complete theme folder, generated when downloaded | Available |
index.tailwind.html | Optional Tailwind variant | Planned |
RECOMMENDATIONS.md | Compatible JS library guidance | Planned |
AGENTS.md | Agent translation instructions | Planned |
Machine access
Wish Themes exposes three static, unauthenticated discovery files:
GET /registry.jsonPublished theme metadata and absolute file URLs↗ GET /backlog.jsonThe complete planned catalog inventory↗ GET /llms.txtA concise site map written for LLMs and coding agents↗ const response = await fetch("https://wishthemes.com/registry.json");
const registry = await response.json();
for (const theme of registry.themes) {
console.log(theme.slug, theme.files.design, theme.files.html);
}Understand release status
Uses a real screenshot and opens a detail page with preview, copy, and download actions.
Uses a wireframe preview with a Planned watermark. It represents catalog direction, not a released download.
License
Wish Themes resources are published under the MIT License. You may use them in personal projects, commercial products, client work, internal tools, and educational material; modify and redistribute them; and deploy them on unlimited domains.
Keep the copyright and permission notice when distributing a substantial copy of the original software. Attribution in your UI is appreciated but not required.
Read the full license page →Make a wish
If the catalog does not contain what you need, submit a GitHub wish. Describe the surface, category, desired style, required sections, target stack, and useful references. Community reactions are intended to guide build priority.
Get help
For implementation questions, bugs, or contribution ideas, use the project’s public channels so answers can help the next builder.