← MiroMiroCONTENT HISTORY

Update to MiroMiro

Snapshot Nov 20, 2026 · 12:10 UTC · version 1.1.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save MiroMiro and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "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.",
  "included_files": [],
  "name": "section-to-code",
  "skill_md_contents": "---\nname: section-to-code\ndescription: 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.\n---\n\n# A section of a page as starting code\n\nUse `extract_code`. It reads the page in a real browser and returns the section's layout\nand computed styles (colors, fonts, spacing) as code, so the user starts from real values\ninstead of guessing from a screenshot.\n\n## Pick the section\n\nWhen the user names a part of the page (\"their pricing table\", \"the footer\", \"the nav\"),\npass it as `section`: one of `hero`, `header`, `footer`, `pricing`, `features`,\n`testimonials`, `faq`, `cta`. MiroMiro finds that block on the page itself. Never invent a\nCSS selector: one that matches nothing falls back to the hero with a `note`.\n\nWith no `section`, the hero is picked. Every result also lists the page's other `sections`,\neach with a label and a ready `selector`: when the part the user wants is not a named\nsection, find it there and call again with that `selector`.\n\n## Pick the format\n\nMatch the user's project:\n\n- `tailwind` (default): Tailwind classes in the markup\n- `jsx`: a React component (`name` sets its name); repeated items come back as a data\n  array rendered with `.map()`\n- `vue`: a single-file component; repeated items as a `v-for`\n- `html`: plain HTML plus a `css` string\n- `elementor`: a template to import into the user's own WordPress site (Templates > Saved\n  Templates > Import); hand the file over unmodified\n- `shopify`: a theme section for the user's own store (`sections/<name>.liquid` in the theme\n  code editor); hand the file over unmodified\n\nPass `theme: \"dark\"` for the dark version; the result's `theme` field says which one came\nback.\n\n## Make it theirs\n\nThe code is a starting point built from a reference page, not something to republish:\n\n- The page's text, images and logos belong to its owner. Unless the page is the user's own,\n  replace them with the user's content (or clear placeholders) before handing the code over,\n  and say so.\n- Keep the layout and styles the user asked for; adapt names, structure and theme tokens to\n  their project.\n- Give the user `previewUrl` (the section rendered) to compare against, and `downloadUrl`\n  (the file as returned).\n- Fonts and images used on the page have their own licenses: mention it when the user is\n  heading to production.\n\nNot for: copying a whole site, extracting a page's text, or pages behind a login.\n"
}

SHA-256 of public snapshot: 973cc1098468a42392f0b979a73fd1f374a1fe40b02a437dc0d65a3867c5c2b8