← Plugin catalog
Developer Tools

MiroMiro

MiroMiro v1.1.1

Extract any website's design

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Interactive
  • Read

Declared limitations

  • Copying a whole website
  • Extracting page text
  • Pages behind a login

Not specified in the available declarations: pricing & account requirements.

Onboarding example

Turn the stripe.com hero into a React component for my landing page
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.

View package source →

Description

From the marketplace listing

MiroMiro reads a public web page's real CSS and returns its design in a form you can build with: the color palette with roles and names, the fonts, the design tokens, and any section of the page as starting code for your own project. Use it as a design reference: see how a site you admire lays out its pricing table or hero, get its palette and type scale as CSS variables, or start your own section from real values instead of guessing from a screenshot. Results also open as a card in the chat: the section rendered, its colors and fonts, or its tokens. What you can do: - Get a site's colors and fonts: the palette with roles and names, fonts by role, the light or dark theme, and a note saying whether each color was declared by the site or inferred from how often it is used - Get the full design token set (colors, typography, spacing, radii, shadows, with usage counts) as JSON, CSS variables, a Tailwind config or a W3C Design Tokens file - Turn a section of a page (hero, pricing, features, FAQ, footer and more) into Tailwind, React, Vue or HTML+CSS starting code, or into an Elementor template or Shopify section to import into your own site, in its light or dark version. Every result lists the page's other sections, so you can pick the next one by name - See which fonts, images, SVG icons and Lottie animations a page uses, as links to the files the page already serves Reference, not reuse: a page's text, images, logos and fonts belong to its owner. MiroMiro tells you to replace them with your own content, and to check the license before you use a font or an image. Works on JavaScript-heavy sites too: pages are read in a real browser, so you get what a visitor actually sees. Reads public pages only, with no login. Sign in with your MiroMiro account to connect. Best for developers and designers who want real design values from live sites instead of eyeballing them.

Language: English · Automatically detected from descriptions.

What changed

· 3 observations

Pricing references

App-6a60e68db3908191b0af3727742ab020 updated; open the comparison for details. Miromiro updated; open the comparison for details. Full description changed from “Extract design from any website MiroMiro lets you pull real design data out of any live website from ChatGPT: brand colors, fonts, logos, design tokens,...”...

View comparison →
Pricing references

App-6a60e68db3908191b0af3727742ab020 updated; open the comparison for details. Miromiro updated; open the comparison for details. Full description changed from “Extract design from any website MiroMiro lets you pull real design data out of any live website from ChatGPT: brand colors, fonts, logos, design tokens,...”...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package6 files · 6.6 KBBrowse files →
Skill instructions
design-reference1.97 KB

View saved version →

---
name: design-reference
description: Read a public website's colors, fonts and design tokens as a reference for the user's own UI. Use when the user asks what colors or fonts a site uses, wants a palette, CSS variables, a Tailwind theme or a W3C design tokens file based on a site, or wants new UI to match their own brand's live site.
---

# Colors, fonts and tokens as a reference

Two tools cover this; pick one, not both by reflex.

**`extract_brand`**: the short answer. Color roles (primary, accent, background, text) as
hex with readable names, the wider palette, fonts by role, the light or dark theme, and
`signals` explaining where the colors came from. Use it for "what colors does X use" and
"make something that feels like X".

**`extract_design_tokens`**: the complete system. Every color, font family, size, weight,
spacing value, radius and shadow, with usage counts. Use it when the user wants a theme
file or a full scale. Ask for the format their project uses instead of converting:
`format: "css"` (a `:root` block), `"tailwind"` (a config fragment) or `"dtcg"` (W3C
Design Tokens).

## Say where the colors came from

Read `signals.explanation` and repeat it to the user. `signals.primarySource` says how
sure the result is:

- `css-var` or `theme-color`: the site declares these colors itself
- `logo` or `cta`: taken from its logo or its main buttons, close but not declared
- `usage`: ranked by how often each color appears. This is an estimate: say so, and never
  present it as the brand's official palette

## Fonts

For type alone, `extract_fonts` lists every font the page loads with weights and formats.
Knowing which font a site uses is not a license to use it: commercial fonts need their own
license, and Google Fonts are free to use. Point the user to the license before production.

## Use it as a reference

Colors and type scales are ideas to build on. A brand's logo, name and imagery belong to
its owner: use them only when the site is the user's own, or to refer to that brand.
section-to-code2.63 KB

View saved version →

---
name: section-to-code
description: Turn a section of a public web page into starting code for the user's own project, using the page as a design reference. Use when the user wants a hero, pricing table, header, footer, features, FAQ or call-to-action styled like one on a page they name, as Tailwind, React, Vue, HTML+CSS, an Elementor template or a Shopify section, filled with their own content.
---

# A section of a page as starting code

Use `extract_code`. It reads the page in a real browser and returns the section's layout
and computed styles (colors, fonts, spacing) as code, so the user starts from real values
instead of guessing from a screenshot.

## Pick the section

When the user names a part of the page ("their pricing table", "the footer", "the nav"),
pass it as `section`: one of `hero`, `header`, `footer`, `pricing`, `features`,
`testimonials`, `faq`, `cta`. MiroMiro finds that block on the page itself. Never invent a
CSS selector: one that matches nothing falls back to the hero with a `note`.

With no `section`, the hero is picked. Every result also lists the page's other `sections`,
each with a label and a ready `selector`: when the part the user wants is not a named
section, find it there and call again with that `selector`.

## Pick the format

Match the user's project:

- `tailwind` (default): Tailwind classes in the markup
- `jsx`: a React component (`name` sets its name); repeated items come back as a data
  array rendered with `.map()`
- `vue`: a single-file component; repeated items as a `v-for`
- `html`: plain HTML plus a `css` string
- `elementor`: a template to import into the user's own WordPress site (Templates > Saved
  Templates > Import); hand the file over unmodified
- `shopify`: a theme section for the user's own store (`sections/<name>.liquid` in the theme
  code editor); hand the file over unmodified

Pass `theme: "dark"` for the dark version; the result's `theme` field says which one came
back.

## Make it theirs

The code is a starting point built from a reference page, not something to republish:

- The page's text, images and logos belong to its owner. Unless the page is the user's own,
  replace them with the user's content (or clear placeholders) before handing the code over,
  and say so.
- Keep the layout and styles the user asked for; adapt names, structure and theme tokens to
  their project.
- Give the user `previewUrl` (the section rendered) to compare against, and `downloadUrl`
  (the file as returned).
- Fonts and images used on the page have their own licenses: mention it when the user is
  heading to production.

Not for: copying a whole site, extracting a page's text, or pages behind a login.

Release notes

Results now open as a visual card in the chat: the section rendered, the palette and fonts, the design tokens or the icons. The listing and skills describe MiroMiro as a design reference and remind users to replace a site's text and images with their own.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
MiroMiro
Keywords
See keywords
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Interactive
  • Read

Package observed Nov 21, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 22, 2026 · 00:00 UTC
Latest observed change
Nov 20, 2026 · 12:10 UTC
Collection status
Collected

plugin_asdk_app_6a60e68db3908191b0af3727742ab020

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.