Remote placeholder images make visitors contact a third party
Source references: 1When real assets are unavailable, the Skill recommends embedding a picsum.photos URL directly in generated pages. Loading that image causes the browser to contact the third party, which can ordinarily receive the visitor's IP address, request time, browser-supplied request metadata, and the context value included in the URL.
If the generated code is previewed or deployed, visitors may unexpectedly connect to a third party, creating privacy, external-dependency, and organizational network-policy risks. The evidence does not show that the service collects additional data or that any disclosure has already occurred.
The live instruction recommends a remote `picsum.photos` image when real assets are unavailable. If generated pages retain that URL, each visitor’s browser will contact the third party and disclose information normally available with a web request, such as IP address, request time, browser headers, and the `{context}` value in the URL path. This risk applies only when the remote resource is actually embedded and loaded. Users can ask for local placeholders, downloaded/self-hosted assets, or explicit consent before external loading.
- Illustrations: Monochromatic, rough continuous-line ink sketches on a white background, featuring a single offset geometric shape filled with a muted pastel color.- Photography: Use high-quality, desaturated images with a warm tone. Apply subtle overlays (`opacity: 0.04` warm grain) to blend photos into the monochrome palette. Never use oversaturated stock photos. Use reliable placeholders like `https://picsum.photos/seed/{context}/1200/800` when real assets are unavailable.- Hero & Section Backgrounds: Sections should not feel empty and flat. Use subtle full-width background imagery at very low opacity, soft radial light spots (`radial-gradient` with warm tones at `opacity: 0.03`), or minimal geometric line patterns to add depth without breaking the clean aesthetic.