image-art-direction
Skill0 starsChanged 3 days agoMITView on GitHub
Select and implement imagery that supports a product story while respecting authenticity, accessibility, performance, and licensing.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- waterblower/Omni-Art-Skillstheir own version, first seen Aug 7, 2026
- gracetey-zhang/Omni-Art-Skillstheir own version, first seen Jun 27, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- waterblower/Omni-Art-Skills★ 47same name
- gracetey-zhang/Omni-Art-Skills★ 32same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- accessibilitySkill
- admin-panelSkill
- ai-agent-interfaceSkill
- ai-chat-interfaceSkill
- ai-dashboardSkill
- ai-engineeringSkill
- analytics-and-data-visualizationSkill
- animation-and-motionSkill
- api-engineeringSkill
- authentication-and-rbacSkill
- backend-architectureSkill
- component-engineeringSkill
- dashboard-designSkill
- database-engineeringSkill
- design-intelligenceSkill
- design-systemsSkill
- frontend-engineeringSkill
- iconographySkill
- integrations-and-webhooksSkill
- javascript-typescriptSkill
- performance-optimizationSkill
- premium-landing-pagesSkill
- python-engineeringSkill
- rag-and-knowledge-systemsSkill
- responsive-designSkill
- saas-dashboardSkill
- security-engineeringSkill
- super-admin-panelSkill
- testing-and-qualitySkill
- unslop-engineSkill
- ux-researchSkill
- visual-designSkill
- visual-regressionSkill
- website-architectureSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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 10
Use when choosing photography, screenshots, illustrations, textures, or other visual assets for an interface.
- Distinctive: line 15
Do not add imagery solely to fill space or imply customers, product capabilities, or outcomes that do not exist.
- Distinctive: line 27
Prefer authentic product assets and properly licensed originals.
- Distinctive: line 32
Use responsive sizes, efficient formats, and appropriate loading priority.
- Distinctive: line 38
Never invent product screenshots, customer logos, or testimonials.
- Distinctive: line 39
Do not redistribute an asset when license terms are unclear.
- Distinctive: line 40
Avoid text embedded in images when the information must be searchable or accessible.
- Distinctive: line 57
Check authenticity, license record, responsive crop, alt-text purpose, format/size, loading behavior, and visual contrast.
≈ “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
Image Art Direction
When to use
Use when choosing photography, screenshots, illustrations, textures, or other visual assets for an interface.
When not to use
Do not add imagery solely to fill space or imply customers, product capabilities, or outcomes that do not exist.
Inputs and assumptions
Identify message, audience, brand, placement, crop behavior, source and license, performance budget, and whether the asset is decorative or informational.
Workflow
- State what the image contributes that text or layout does not.
- Prefer authentic product assets and properly licensed originals.
- Match composition, aspect ratio, crop, and focal point to actual responsive placements.
- Provide concise useful alternative text for informative images; use an empty alternative for decorative images.
- Use responsive sizes, efficient formats, and appropriate loading priority.
- Record asset source, creator, license, attribution, and restrictions.
- Review crop and contrast against real content and themes.
Decision rules
- Never invent product screenshots, customer logos, or testimonials.
- Do not redistribute an asset when license terms are unclear.
- Avoid text embedded in images when the information must be searchable or accessible.
- Respect privacy and consent for identifiable people.
Example
A product screenshot may use clearly labeled sample data, but must not be presented as a real customer result or live production metric.
Common failures
- Generic stock images unrelated to the product.
- Hero images that crop away the meaningful subject on mobile.
- Missing attribution, oversized files, or redundant alt text.
Validation
Check authenticity, license record, responsive crop, alt-text purpose, format/size, loading behavior, and visual contrast.
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.