# Copy to Clipboard

## Objective

Make copying an exact value one click, with feedback the user can trust.

A copy control on every value people currently select by hand — IDs, API keys, share links, snippets.

## 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. Find every value a user would plausibly copy: record IDs, tokens, invite links, code blocks, error references.
2. Copy the exact value. Strip the surrounding whitespace and any zero-width or formatting characters the UI added for display.
3. Confirm the copy in place, next to the control, and revert to the idle state after a couple of seconds.
4. Do not copy a masked or truncated value. If the UI shows dots or an ellipsis, either copy the full underlying value or require the user to reveal it first.
5. Do not move focus on copy. The user is usually mid-flow and about to paste somewhere else.

## 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 Clipboard API fails on insecure origins and when permission is denied. Fall back to a selectable field and tell the user to copy manually.
- Code snippets keep their line breaks and indentation; IDs and URLs must not carry a trailing newline.
- A secret shown masked must never end up on the clipboard by accident.
- Confirmation must be announced to screen readers, not conveyed by a colour change alone.
- Copying twice in quick succession must not stack two confirmations on top of each other.
- On mobile the confirmation must not appear under the user's thumb.

## 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 copyable value in the app has a copy control.
- [ ] The copied value matches the real value exactly, with no stray whitespace.
- [ ] Masked secrets cannot be copied without being revealed.
- [ ] A blocked or unavailable Clipboard API degrades to a manual fallback rather than failing silently.
- [ ] Success is announced accessibly and focus does not move.
- [ ] 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.