← Ember WebsitesCONTENT HISTORY
WHAT CHANGED
Update to Ember Websites
Snapshot Oct 24, 2026 · 13:39 UTC · version 2.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Ember Websites and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Add, upload, place, or troubleshoot existing images and downloadable files in an Ember site. Use for any image or static-asset work, especially portfolios, galleries, hero photos, source assets, researched stock photography, PDFs, or favicons. Preserves existing and real work, applies automatic optimization correctly, and covers public paths, truthful use, alt text, scrims, and verification.",
"included_files": [],
"name": "add-ember-images-and-files",
"skill_md_contents": "---\nname: add-ember-images-and-files\ndescription: Add, upload, place, or troubleshoot existing images and downloadable files in an Ember site. Use for any image or static-asset work, especially portfolios, galleries, hero photos, source assets, researched stock photography, PDFs, or favicons. Preserves existing and real work, applies automatic optimization correctly, and covers public paths, truthful use, alt text, scrims, and verification.\n---\n\n# Add images and files to Ember\n\n## Success criteria\n\nImage work is complete when every intended visual slot renders a relevant,\nhigh-quality image from a valid non-empty source, uses appropriate alt text,\nfits its crop and layout across viewports, and remains truthful about what it\ndepicts. Keep any working existing image until an equal or better replacement\nis ready. A finished site has no unfilled image placeholders. If truthful\nimagery is unavailable, remove the unused placeholder or ask for the real\nasset instead of presenting an empty frame as completed work.\n\n## Choose a suitable source\n\nUse a direct public HTTPS image URL, including a suitable Unsplash or other\nstock URL; an existing path already in the site; or an Ember-managed\nasset created with `upload_file`. Choose the option that best fits the request.\nUse `upload_file` when a managed copy, optimization, stable local path, or\ndownloadable non-image asset is useful—not as a requirement for every image.\n\nIf calling `upload_file`, pass a complete short, descriptive destination\nfilename rather than only a directory, especially for signed or opaque source\nURLs. Use `referenceInPagesAs` when the result supplies it; otherwise derive the\nserved path from the reported stored path. A small `data:` URI is suitable only\nfor compact assets such as an SVG icon.\n\nSave visitor-facing assets under a typed `/public` directory, such as\n`/public/images/`, `/public/files/`, or the `/public` root for a favicon. The\nserved path drops `/public`: reference `/public/files/menu.pdf` as\n`/files/menu.pdf`.\n\nImages sent through `upload_file` are resized and re-encoded automatically. The\noptimizer may change the filename or extension, so reference the path reported\nby the tool rather than the requested path. The MCP server cannot read the\nuser's local disk; a managed upload requires a publicly retrievable HTTPS URL\nor a small data URI.\n\n## Choose truthful existing imagery\n\nUse the user's real portfolio, products, menu, team, location, and other\nfactual work whenever it is available. For generic atmosphere or editorial\nsupport, use relevant existing stock or editorial photography,\nbut do not label or imply that it depicts the actual business, products,\npeople, work, or location. If a factual image is unavailable, remove the unused\nplaceholder or ask for the real asset rather than inventing one.\n\n## Place assets well\n\n- Give every `<img>` meaningful alt text; use an empty alt only for genuinely\n decorative imagery.\n- Place asset sizing, cropping, overlays, and other visual rules in\n `components/theme.ts` using the selected design's tokens and classes.\n- Put a scrim between text and any photographic hero/background, and verify\n contrast in light and dark themes.\n- Add a favicon link and OG metadata in `PageShell` when the request calls for\n them.\n- Use short descriptive filenames instead of camera defaults.\n\nAfter placing assets, run `check_site` for normal site correctness, then inspect\nthe already-mounted live preview. Confirm that every intended image renders,\nfits its crop and responsive layout, maintains contrast, and has appropriate\nalt text. Call `render_preview` again for the final checked state or a fresh\nshareable link.\n"
}SHA-256 of public snapshot: ddfc5902b5fb22ddc786b8cb90ab6734e6a3fcbad631479421967a98ac5ef4d2