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.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- apply-project-updatesSkill
- audit-project-updatesSkill
- design-agent-capabilitySkill
- engineer-cli-toolsSkill
- maintain-agent-instructionsSkill
- maintain-project-docsSkill
- maintain-project-memorySkill
- maintain-web-design-systemSkill
- red-team-technical-planSkill
- release-web-applicationSkill
- research-software-versionsSkill
- verify-software-changeSkill
- web-discovery-artifactsSkill
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
- Very specific: line 11
When Portable Web Toolkit manages the project, use its brand-doctor and image-pipeline where applicable.
- Distinctive: line 20
Do not redraw trademarks, alter supplied official logos, or replace approved assets without authorization.
- Distinctive: line 23
If source quality is insufficient, report the limitation before inventing a replacement.
- Distinctive: line 28
Use SVG for suitable logos, icons, diagrams, and scalable illustrations.
- Distinctive: line 30
Use AVIF or WebP for photographic assets when project and browser support justify it.
- Distinctive: line 32
Keep PNG where transparency, lossless detail, or platform tooling requires it.
- Distinctive: line 33
Avoid recompressing already degraded sources.
- Very specific: line 36
Use references/asset-matrix.md for common web destinations.
- Distinctive: line 40
Use stable, collision-resistant filenames consistent with project conventions.
- Distinctive: line 43
Use meaningful alternative text for informative imagery.
- Distinctive: line 44
Use empty alternative text or presentation semantics for decoration.
- Distinctive: line 45
Do not put essential text only inside an image.
- Distinctive: line 46
Keep social-card, favicon, app-icon, and inline-image concerns distinct.
- Distinctive: line 47
Avoid embedding secrets, private metadata, or unintended EXIF location data.
- Distinctive: line 51
Use an image-generation tool only when the user explicitly requests new visual content or editing.
- Distinctive: line 57
Check file integrity, dimensions, transparency, color behavior, file weight, references, responsive selection, browser rendering, …
≈ “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
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
- Locate official masters, brand guidance, licenses, attribution requirements, and existing asset manifests.
- Preserve originals separately from generated derivatives.
- Do not redraw trademarks, alter supplied official logos, or replace approved assets without authorization.
- Record provenance for externally sourced material.
- 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
srcsetandsizesbased 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.
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.

