agentleFS
ImYourBoyRoyImYourBoyRoy/agent-continuity-stack/skills/prepare-web-assets/SKILL.md

prepare-web-assets

Skill1 starsChanged 4 months agoMITView on GitHub

Prepare and integrate production web images, icons, logos, favicons, and social assets with correct formats, derivatives, accessibility, provenance, and performance. Generate artwork only when explicitly requested.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 14 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When Portable Web Toolkit manages the project, use its brand-doctor and image-pipeline where applicable.

    line 11
  2. Distinctive:

    Do not redraw trademarks, alter supplied official logos, or replace approved assets without authorization.

    line 20
  3. Distinctive:

    If source quality is insufficient, report the limitation before inventing a replacement.

    line 23
  4. Distinctive:

    Use SVG for suitable logos, icons, diagrams, and scalable illustrations.

    line 28
  5. Distinctive:

    Use AVIF or WebP for photographic assets when project and browser support justify it.

    line 30
  6. Distinctive:

    Keep PNG where transparency, lossless detail, or platform tooling requires it.

    line 32
  7. Distinctive:

    Avoid recompressing already degraded sources.

    line 33
  8. Very specific:

    Use references/asset-matrix.md for common web destinations.

    line 36
  9. Distinctive:

    Use stable, collision-resistant filenames consistent with project conventions.

    line 40
  10. Distinctive:

    Use meaningful alternative text for informative imagery.

    line 43
  11. Distinctive:

    Use empty alternative text or presentation semantics for decoration.

    line 44
  12. Distinctive:

    Do not put essential text only inside an image.

    line 45
  13. Distinctive:

    Keep social-card, favicon, app-icon, and inline-image concerns distinct.

    line 46
  14. Distinctive:

    Avoid embedding secrets, private metadata, or unintended EXIF location data.

    line 47
  15. Distinctive:

    Use an image-generation tool only when the user explicitly requests new visual content or editing.

    line 51
  16. Distinctive:

    Check file integrity, dimensions, transparency, color behavior, file weight, references, responsive selection, browser rendering, …

    line 57

≈ “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.

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

Prepare Web Assets

Produce traceable, appropriately licensed, accessible assets without replacing official source material.

When Portable Web Toolkit manages the project, use its brand-doctor and image-pipeline where applicable. Do not create a competing asset manifest, derivative pipeline, or brand-validation command.

Establish source authority

  1. Locate official masters, brand guidance, licenses, attribution requirements, and existing asset manifests.
  2. Preserve originals separately from generated derivatives.
  3. Do not redraw trademarks, alter supplied official logos, or replace approved assets without authorization.
  4. Record provenance for externally sourced material.
  5. If source quality is insufficient, report the limitation before inventing a replacement.

Select formats

  • Use SVG for suitable logos, icons, diagrams, and scalable illustrations.
  • Sanitize externally sourced SVG and remove scripts or unsafe references.
  • Use AVIF or WebP for photographic assets when project and browser support justify it; provide the required fallback.
  • Keep PNG where transparency, lossless detail, or platform tooling requires it.
  • Avoid recompressing already degraded sources.
  • Generate only sizes the interface or metadata actually consumes.

Use references/asset-matrix.md for common web destinations.

Integrate correctly

  • Use stable, collision-resistant filenames consistent with project conventions.
  • Include width and height or aspect ratio to reduce layout shift.
  • Provide srcset and sizes based on real layout behavior.
  • Use meaningful alternative text for informative imagery.
  • Use empty alternative text or presentation semantics for decoration.
  • Do not put essential text only inside an image.
  • Keep social-card, favicon, app-icon, and inline-image concerns distinct.
  • Avoid embedding secrets, private metadata, or unintended EXIF location data.

Generation boundary

Use an image-generation tool only when the user explicitly requests new visual content or editing. Treat generated output as a candidate requiring human review for brand, factual, licensing, and accessibility suitability.

Validate

Check file integrity, dimensions, transparency, color behavior, file weight, references, responsive selection, browser rendering, alternative text, and licensing records. Use lossless or reversible operations on masters.

Report source assets, derivatives, transformation commands, quality tradeoffs, integration changes, checks, and unresolved rights or brand questions.

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.