demo-assets
Skill2 starsChanged 3 months agoMITView on GitHub
Sourcing and art-directing imagery for demos and mockups - curated photo sources, licensing, local hosting, treatment consistency. Use whenever a demo or real page needs product/lifestyle imagery, or when tempted to draw abstract vector "product art".
In this repository18 other files it gives its agents.
- art-director-reviewSkill
- b2b-landingSkill
- brand-voiceSkill
- checkout-trustSkill
- composition-gridsSkill
- copy-chiefSkill
- design-tokensSkill
- experimentation-measurementSkill
- layout-compositionSkill
- marketing-strategySkill
- motion-performanceSkill
- navigation-searchSkill
- pixel-qaSkill
- post-purchase-lifecycleSkill
- product-page-croSkill
- promotions-eventsSkill
- typography-craftSkill
- visual-identitySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
When assembling multiple images on one page (gallery, features, lifestyle).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Demo Assets
Born from a real failure: our first demo shipped an abstract SVG headphone in the hero. It passed every lint, and it still read "AI-generated" at first glance. Imagery is where premium is won or lost — a page with flawless tokens and a fake-looking hero is not top tier.
When to use
- Any demo, mockup, or real page that shows a product, a person, or a space.
- The moment you're tempted to draw an abstract SVG "product" — that's the signal to source a photograph instead.
- When assembling multiple images on one page (gallery, features, lifestyle).
Rules
- [LAW] Hero and product visuals are photographs (or true photoreal 3D renders) — never abstract vector art. Vector art standing in for the product is an automatic MAJOR genericness finding in art-director review. SVG remains correct for icons, diagrams, logos, and decorative motifs.
- [FRAMEWORK] Photo sources for demos, in order of preference: Unsplash (unsplash.com), Pexels (pexels.com), Pixabay (pixabay.com) — free licenses, no attribution required for use in designs. Verify the license page at download time; terms change. For a real client, client photography beats all of these.
- [LAW] Download assets locally into the project (
assets/img/ordemo/img/) — never hotlink. Hotlinking adds third-party requests (performance budget), breaks offline demos, and violates most stock licenses' redistribution terms less predictably than a local copy. - [FRAMEWORK] One art direction per page: one light temperature (all warm or all cool), one camera-angle family, consistent background tones. A mixed-temperature stock collage is the #1 "assembled from stock" tell.
- [FRAMEWORK] Grade photos toward the brand palette — a subtle 5–10% tint/duotone overlay using brand tokens makes disparate photos read as one shoot.
- [LAW] Serve AVIF/WebP with explicit
width/heightattributes,srcsetfor 1x/2x,loading="lazy"below the fold only — the motion-performance image rules apply fully to sourced photos. - [LAW] Alt text describes and sells: "AURI A1 earcup stitching in matte titanium", never "product image" or empty alt on meaningful photos.
- [FRAMEWORK] Fictional demo brands: pick logo-free shots or crop visible real brandmarks out — a real logo on a fictional product page is a legal and honesty problem.
- [FRAMEWORK] People photos: natural, doing the actual activity (wearing the headphones at a desk), diverse, no stock clichés (handshakes, pointing at screens, forced laughter at salad).
- [FRAMEWORK] Payment/trust marks are never bordered text chips. Use a muted single-color text row with separators, or proper monochrome SVG marks at consistent height, at reduced emphasis (muted token) — they are reassurance, not content.
Art direction judgment
- [FRAMEWORK] Frame every hero/product photo with rule-of-thirds subject placement — subject on the left or right third, never centered — so the opposite two-thirds stays clear as negative space for the headline/CTA overlay. Check this at sourcing time, before any scrim treatment is chosen. — composition-canon.md rule 32 (Shorthand, "The Rule of Thirds in Photography")
- [FRAMEWORK] Orient subject gaze, pointing, or implied motion so its directional vector points inward toward the CTA, not off-frame or out of the composition — this extends the continuity principle (an established visual line should terminate at the next action) to photographic direction, not just graphic elements. — composition-canon.md rules 19 (NN/g Continuation) and 32 (rule-of-thirds), applied to photo-subject direction
- [FRAMEWORK] Translate brand personality into shooting-language choices before sourcing, not after: name the light temperature, camera-angle family, and depth of field the brand's tone calls for (e.g. "warm, low-angle, shallow DOF" for approachable/premium vs. "cool, level, deep DOF" for clinical/precise), and hold every sourced photo to that spec. This is the brand-fit layer on top of rule 4's "one art direction per page" consistency requirement. — synthesis of this skill's rules 4-5 (art-direction consistency, brand-palette grading) with composition-canon.md rule 27 (visual weight factors as carriers of intent)
- [LAW] Any headline or CTA text placed over a photo must clear WCAG SC 1.4.3 at the single worst-case pixel neighborhood it overlaps — ≥4.5:1 for body/UI-scale text, ≥3:1 for large text (≥18.5px regular or ≥24px bold) — measured against the lightest/darkest region under the text, never the image's average color. — canonical owner: composition-grids (its text-over-photo rules govern; on any numeric drift, defer there); provenance: composition-canon.md rules 10-11 (W3C WCAG 2.1 SC 1.4.3; NN/g)
- [LAW] Scrim opacity starts at 20–40% black (dark scrim over a light/busy photo) or 40–60% white (light scrim over a dark photo); tune within that band per image and re-verify contrast at the worst-case point (rule 14) before shipping. Prefer an eased gradient scrim over a flat overlay when only part of the photo needs protection, and move the headline into a flat-color panel instead when even a tuned scrim can't clear contrast. — canonical owner: composition-grids (defer there on drift); provenance: composition-canon.md rules 12-13, 15 (Google Material Design imagery spec; Ahmad Shadeed; Smashing Magazine Part 2)
Anti-patterns
- Abstract gradient blobs or concentric-circle "product art" standing in for the product photo.
- Hotlinked images from any CDN in a shipped demo.
- Five photos from five different shoots on one page.
- Payment badges as outlined text boxes (looks templated/cheap).
- Meaningful photos with decorative-only empty alt.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

