# Visual Asset Optimization Pipeline

## Objective

Turn source artwork into small, correct derivatives without losing the detail that matters.

A repeatable processing step that derives sized and compressed variants for every image, icon, and illustration the app ships.

## Before You Begin

This feature is being added to an application that already exists and already
works. Do not scaffold a new project, and do not assume a blank slate.

Inspect the codebase first and establish:

- The existing application structure and where code of this kind already lives.
- The framework and version in use.
- The existing design system — colours, spacing, typography, and component conventions.
- Existing UI components you can reuse instead of writing new ones.
- The existing database structure, if this feature needs to persist anything.
- The existing authentication and authorization system, if this feature is user-scoped.
- Dependencies already installed, so you don't add a library that duplicates one.
- The existing test setup and conventions.

Only start writing code once you understand the above. If the application
already implements part of this feature, extend it rather than replacing it.

## Implementation Instructions

1. Locate every visual asset the app serves — bundled artwork, icons, illustrations, and user uploads — and bring them all through one processing path instead of optimising some by hand.
2. Keep the untouched original of every asset in a place the pipeline can reach, so a change in format or quality target can be applied by reprocessing rather than by re-sourcing artwork nobody can find.
3. Set the compression target per kind of asset. A photograph tolerates aggressive compression; a screenshot containing text and a flat illustration with hard edges show artefacts at the same setting.
4. Emit a manifest describing every derivative produced — its dimensions, format, and the original it came from — and let the Adaptive Media Source Component read that manifest rather than construct URLs for files the pipeline may never have made.
5. Do not reprocess everything on every build. Key derivatives by the content of the source so an unchanged asset is reused, or the pipeline becomes slow enough that someone disables it.

## UI and UX Requirements

Match the application's existing design system exactly. Reuse its components,
spacing, and typography. This feature should look like it was always there.

## Responsive Requirements

Works on mobile, tablet, and desktop. Touch targets are large enough to hit on a
phone, and nothing overflows horizontally at 320px.

## Accessibility Requirements

- Fully keyboard navigable.
- Correct semantic elements and ARIA roles.
- Visible focus states.
- Meets WCAG AA contrast.
- Dynamic changes are announced to screen readers.
- Respects prefers-reduced-motion.

## Edge Cases

- Originals must survive. Once the pipeline overwrites its own input, the next change of format or quality has nothing to work from and the artwork has to be recovered from a designer's machine.
- One quality setting cannot serve every kind of asset. Verify a photograph, a text-bearing screenshot, and a flat vector-style illustration side by side before fixing the defaults.
- Transparency and animation must survive conversion. An alpha channel flattened to white and an animated file reduced to its first frame are both silent failures that only show up on the page.
- Every derivative must be checked before it is published — that it opens, that its dimensions are right, and that it is genuinely smaller than the source. A conversion that produced a larger file should be discarded in favour of the original.
- Orientation metadata must be applied and then stripped, so a photograph does not publish sideways, and location and camera metadata never reach a public URL.
- Colour profiles must be converted rather than dropped, or brand colours will shift between the source file and the rendered page.
- User uploads have to travel the same path at runtime, with a size and dimension limit and a defined behaviour for a file the pipeline cannot process.

## Testing

Exercise the feature end to end in the running application. Cover every edge case
above, then run the existing test suite and confirm nothing regressed.

## Acceptance Criteria

- [ ] Every visual asset the app serves is produced by the pipeline rather than optimised by hand.
- [ ] Untouched originals are retained and reprocessing regenerates all derivatives from them.
- [ ] Compression targets differ by asset type and were validated against a photograph, a screenshot, and an illustration.
- [ ] Transparency and animation are preserved in every derivative that claims to support them.
- [ ] Each derivative is verified for openability, dimensions, and size before publication, and a larger-than-source result is rejected.
- [ ] Published files carry no camera or location metadata.
- [ ] An unchanged asset is not reprocessed on a rebuild.
- [ ] The feature matches the existing design system.
- [ ] No existing functionality is broken.

## Adaptation Rules

- Match the existing design system. Do not introduce a new colour palette,
  spacing scale, or component library.
- Reuse existing components and utilities wherever they fit.
- Follow the naming, file layout, and code style already present.
- Do not upgrade, replace, or remove existing dependencies to make this
  feature fit. Adapt the feature to the app, not the app to the feature.
- Do not break existing functionality. If a change is genuinely required in
  existing code, make the smallest one that works and say so.
- If something in these instructions conflicts with how the application is
  built, follow the application and explain the deviation.

## Final Verification

Before you report the work as done:

1. Re-read the acceptance criteria above and check each one against what you
   actually built.
2. Run the application and exercise the feature end to end.
3. Run the existing test suite and confirm you have broken nothing.
4. Check the feature on mobile, tablet, and desktop widths.
5. Check keyboard navigation and focus handling.
6. Summarize what changed: files added, files modified, and anything you
   deliberately did differently because of how this application is built.

If any acceptance criterion is unmet, fix it before reporting completion.