# Image Focal Point Cropping

## Objective

Keep the subject of an image in frame at every card size and aspect ratio.

A focal point stored per image and honoured by every crop the app renders, at any ratio.

## 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. Identify every place the app crops an image to fit a fixed shape — card thumbnails, list rows, avatars, hero banners, share previews — and record the ratios each of them uses.
2. Store the focal point as relative coordinates on the image record itself, not on any one crop, so the same point drives the square thumbnail, the wide banner, and any ratio added later.
3. Give whoever uploads the image a way to set the point directly on the image, with the common crops previewed live beside it, so the choice is made against the shapes it will actually appear in.
4. Define a sensible default for images that have never been given a focal point, and apply it everywhere rather than letting each surface choose its own — an inconsistent default is harder to diagnose than a wrong one.
5. Do not crop by scaling the image down to fit the frame. Letterboxing a portrait photo into a wide card produces bars and a subject too small to read, which is the problem the crop was meant to solve.

## 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

- The focal point belongs to the image, not to a crop or a card. Storing it per surface means the same photo is corrected three times and drifts apart the moment one of them is edited.
- Rotating or re-orienting an image invalidates its stored coordinates. Recompute or clear the point when orientation changes, or the crop will centre on the wrong part of the picture.
- A focal point chosen against one ratio can still lose the subject in another. Show the common responsive crops during selection so the person setting it sees the square, the wide, and the tall result at once.
- Replacing the image file without replacing the record leaves a stale focal point pointing at nothing in particular. Reset to the default on replacement and prompt for a new point.
- Extreme ratios — a very wide banner or a very tall panel — may still cut the subject even with a correct focal point. Clamp the crop so the point stays within the frame rather than sliding off the edge.
- Images narrower or shorter than the frame must not be upscaled past the point of visible softness; pad them against a neutral surface instead.
- Text overlaid on a cropped image must stay legible whatever the crop lands on, which means a scrim or a reserved area rather than trusting the image to be dark enough.

## 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 image record carries a focal point stored in relative coordinates independent of any crop.
- [ ] All crop surfaces in the app derive their framing from that single stored point.
- [ ] The upload flow lets the point be set on the image with the common crops previewed.
- [ ] Images without a set focal point use one documented default across every surface.
- [ ] Changing orientation or replacing the file clears or recomputes the stored point.
- [ ] The subject stays within the frame at every ratio the app renders, including the widest and tallest.
- [ ] No crop letterboxes or upscales an image beyond legibility.
- [ ] 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.