Update to Ember Websites

{
  "description": "Rebuild or migrate an existing website, Google Business profile, social profile, or other online business presence into Ember. Use when the user asks to import, recreate, migrate, modernize, or improve an existing site. Preserves verified identity, content, navigation, branding, forms, social links, locations, and source images while adapting them to Ember's design system and static-site boundaries.",
  "included_files": [],
  "name": "import-sites-to-ember",
  "skill_md_contents": "---\nname: import-sites-to-ember\ndescription: Rebuild or migrate an existing website, Google Business profile, social profile, or other online business presence into Ember. Use when the user asks to import, recreate, migrate, modernize, or improve an existing site. Preserves verified identity, content, navigation, branding, forms, social links, locations, and source images while adapting them to Ember's design system and static-site boundaries.\n---\n\n# Import an existing presence into Ember\n\nRebuild the source in Ember; do not pixel-clone its layout. Preserve the\nsource's purpose, verified identity, information architecture, substantive\ncontent, branding, and real assets inside the selected Ember design. Never\ninvent missing facts or testimonials.\n\nUse the `build-ember-sites` workflow for account preflight, site creation, the\ninteractive design studio, batching, checks, previews, and publishing. Also use\n`structure-ember-content`, `build-ember-forms`, and\n`add-ember-images-and-files` wherever their triggers apply.\n\n## Inventory before authoring\n\nBuild a migration manifest before creating or editing an Ember site. This is a\nhard gate: do not select/apply a design or author pages, components, content,\nconfiguration, or public assets until the manifest is complete. Start with\n`sitemap.xml` when available, then follow every same-origin link reachable from\nnavigation and page bodies. Record each source URL and destination route,\ntitle and metadata, navigation position, substantive copy, contact facts, form\nbehavior, download, and image. Preserve source paths when Ember can represent\nthem; record every intentional exclusion.\n\nThe manifest must include all of the following:\n\n- Desktop, tablet, and mobile captures, with viewport dimensions and source\n  URL. If a full-page capture is unreadable, use viewport and section captures\n  rather than inferring what it contains.\n- A source-order section geometry inventory: approximate heights, container\n  widths, columns, alignment, image/text placement, major spacing, and how\n  those relationships change across the three viewports.\n- An asset inventory covering logo, favicon, every meaningful `<img>`,\n  `picture`/`srcset` candidate, CSS background, carousel slide, gallery item,\n  factual team/product/location image, and download. Record role, source page,\n  exact candidate URLs, selected highest-suitable original, alt/caption,\n  intended Ember reference, and status. Enumerate every carousel/gallery state,\n  not only the item visible during capture.\n- An interaction inventory covering desktop/mobile navigation, sticky or\n  overlay headers, anchors, carousels, tabs/accordions, buttons and links,\n  forms and validation, maps, embeds, downloads, and unsupported behavior.\n- Reconciliation totals for pages, sections, assets, forms, social links,\n  maps, downloads, and interactions, with a named exception for every gap.\n\nWhen the site exists, persist this working checklist as\n`/.ember/import-manifest.md` before authoring so subsequent passes can reconcile\nagainst the same evidence. Do not claim discovery is complete while a count is\nunknown or an observed source element has no manifest row.\n\nUse the host's available browsing or user-provided material to inventory all\nin-scope pages, navigation order and hierarchy, headings, copy, offerings,\nprices, identifiers, contact details, locations, hours, forms, social links,\nlogo, fonts, colors, and meaningful images. Preserve a multi-page source as\nreal pages rather than flattening navigation into anchors; keep a genuinely\nsingle-page source single-page.\n\nIf the source cannot be inventoried, do not create or edit an Ember site. State\nexactly what is missing and ask for a reachable URL, site export,\nscreenshots/assets, or explicit approval for a partial migration. If sources\nconflict, surface the conflict and ask rather than choosing or inventing a\nfact. Do not fill unknown business facts with plausible prose.\n\n## Rebuild faithfully\n\n- Keep the verified business or project name prominent in text, not only in a\n  logo, slogan, or image. Rename the Ember site with `update_site` once known.\n- Preserve exact addresses, phones, emails, hours, prices, location details,\n  and social destinations. Use the full verified address in map embeds.\n- Preserve the source's page and content grouping while adapting presentation\n  to the chosen Ember components.\n- Recreate repeated content as Markdown collection entries, not arrays in JSX.\n- Classify every form and interactive flow before rebuilding it. Map only\n  submit-to-owner forms to Ember's supported `data-ember-form` contract and a\n  real thank-you page; match field order, labels, types, choices, required\n  states, validation hints, consent, and CTA. Preserve every distinct source\n  workflow as a distinct Ember form with its own stable id; there is no\n  per-site form-count cap, so never merge a waitlist, RSVP, application, or\n  quote request into the contact form to conserve forms. Reuse an id only for\n  the same logical form with the same fields and behavior. Tell the user to\n  configure recipients in Ember's Forms view. Until they do, describe the form\n  as built but not configured; afterward, describe it as configured but not\n  yet verified until the owner confirms a real submission, inbox entry,\n  redirect, and notification. Never claim inbox or notification delivery was\n  verified from the MCP host. Do not silently replace file\n  uploads, payments/carts, accounts, live booking/inventory, calculators, or\n  custom integrations; preserve an honest external link or supported\n  third-party embed when possible, otherwise explain the gap and ask the user.\n- For every meaningful source asset, record its URL, role, and alt/caption.\n  Success means the highest suitable original is represented by a stable,\n  reachable source with the right semantics. A direct public HTTPS URL or an\n  Ember-managed path returned by `upload_file` are both valid; choose the\n  strategy that best preserves fidelity and reliability. Exclude only duplicate\n  variants, trackers, or inaccessible/licence-restricted files, report each\n  exclusion, and never substitute unrelated imagery for available original\n  work.\n- Apply identifiable brand colors and practical font choices through token\n  values in `components/theme.ts`; keep logos legible rather than forcing them\n  into a text-only wordmark slot.\n\n## Compare and hand off\n\nAfter the build, reconcile the migration manifest row by row and report\npage/form/asset counts plus exceptions. Compare every in-scope source page against the Ember result.\nConfirm all substantive content, forms, social links, locations, and usable\nsource images are represented; remove every piece of demo content. Run\n`check_site`, fix every issue, and inspect every route in `render_preview`.\n\nTell the user what was retained and name any page, image, link, or fact that\ncould not be accessed. Let the user review the preview and decide when to\npublish.\n"
}