agentleFS
KyaniteLabsKyaniteLabs/tastecheck/skills/art-direction/SKILL.md

art-direction

Skill12 starsChanged 12 days agoMITView on GitHub

Imagery, illustration, and iconography direction for web UI. Use for hero images, photo treatment, illustration style, icon sets, favicons, OG/social cards, decorative graphics, image-shaped holes, and removing generic AI imagery.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a one-line stance: audience, moment, desired response, and what imagery communicates that copy cannot.

    line 16
  2. Distinctive:

    Prefer a coherent series over unrelated stock images.

    line 36
  3. Distinctive:

    Use decorative alt only when removing the image loses no task-relevant information.

    line 37
  4. Distinctive:

    Use decision records when competing treatments require a documented trade-off.

    line 48
  5. Very specific:

    Stop / handoff: Stop when source or rights constraints cannot be verified.

    line 72

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Art Direction

Art direction gives imagery a job: orient, explain, establish trust, or create a controlled emotional cue. It is not a list of adjectives.

Set the visual job before selecting assets

Write a one-line stance: audience, moment, desired response, and what imagery communicates that copy cannot. Choose one primary treatment and fallback: documentary detail, diagrammatic illustration, editorial crop, icon system, or no image.

DecisionSpecifyReject when
Subjectpeople, object, place, or abstract conceptit repeats the headline without adding evidence
Point of viewdistance, angle, energy, inclusionit turns a serious task into decoration
Compositionfocal zone, text-safe area, responsive cropthe message disappears at narrow widths
Surfacepalette, texture, line weight, lightingit conflicts with product semantic states
Rightssource, license, attribution, expiryownership or reuse is unknown

Turn the stance into an asset contract

For each asset, record source, allowed use, focal subject, wide/narrow crop anchors, overlay, and alt decision. Without an approved library, deliver a search or commissioning brief—not fabricated filenames or claimed licenses.

  • Make the narrow crop independently legible; do not assume a desktop crop merely shrinks.
  • Reserve readable text space in the composition before applying an overlay.
  • Prefer a coherent series over unrelated stock images. Inclusion must be credible to the subject and setting.
  • Use decorative alt only when removing the image loses no task-relevant information. Otherwise state the information in concise alt text or adjacent copy.

Prove it in the rendered layout

Show wide and narrow compositions with real headline, navigation, and state colors. Check crop survival, overlay contrast, repeated-card noise, and icon legibility at rendered size.

Deliver a treatment board: stance, primary/fallback, two assets or search terms, crop notes, rights status, alt strategy, and reject criterion. Source URLs, licenses, and approval status are evidence, not ornamental credits.

Use decision records when competing treatments require a documented trade-off.

Favicons and app icons

Ship an SVG favicon primary (<link rel="icon" href="/favicon.svg" type="image/svg+xml">) with a PNG fallback. Derive the mark from the stance; test at 16×16 pixels—a bold glyph outperforms a detailed logo. Apple Touch Icon (180), manifest icons (192/512), and OG preview are separate deliverables with their own crop/contrast needs. See patterns.

Ship check

  • The treatment explains a product or content need that copy alone cannot.
  • Every selected image has source, rights, crop, and alt decisions.
  • The narrow composition and text-over-image state have been reviewed.
  • A missing or unlicensed asset is represented as a brief, not an invented deliverable.
<!-- contract:v1:start -->

Contract (generated)

Canonical detail: contract.json.

  • Route: A product needs a committed imagery, illustration, or iconography system with source and rights decisions.; avoid: The request is only a color, type, or layout decision.
  • Exclude: Do not use placeholder imagery when the brief requires a real asset plan. (+1 in contract.json)
  • Stop / handoff: Stop when source or rights constraints cannot be verified. (+1 in contract.json); receives [design-system-interview, improve-existing-website, tasteroll] -> sends [responsive-layout, a11y-pass, deslop-ui, tastecheck-pass]
  • Output: source-aware visual treatment and asset plan
  • Evidence: table_with_evidence with status, reason, remediation, evidence, provenance.
<!-- contract:v1:end -->

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.