AddThisFeature

Document Scanner

Turn a phone photo of a paper document into a straight, readable, multi-page file.

involved Documents & Files

What it adds

A camera capture flow that detects page edges, corrects perspective, and assembles the shots into one document.

What your agent is told to do

5
  1. 1

    Lead with the capture screen: live edge detection, a shutter, and a running strip of the pages already taken. Somebody should be able to shoot five pages without leaving the camera.

  2. 2

    Correct perspective and crop to the detected page before saving, then apply a contrast pass so a grey photo of a page reads as black text on white.

  3. 3

    Give the user a review step where pages can be reordered, retaken, or deleted before anything is committed.

  4. 4

    Send the assembled document out through the same upload path a user picking a file would hit. Capturing from the camera changes where the pages came from, not what the app is willing to store, and a camera route that skips the usual checks is exactly the one someone will look for.

  5. 5

    Do not build a desktop scanner-driver integration. The minimum coherent version is a phone camera with a file picker fallback; anything talking to hardware over USB is a different product.

Edge cases it handles

8
  • Edge detection fails on a dark desk, a patterned tablecloth, or a page held over a similarly coloured surface. Always let the user drag the corners by hand instead of blocking the capture.
  • Pages captured in sequence must keep their order through the review step and the upload. A contract whose pages arrive shuffled is worse than no scan at all.
  • Glare from an overhead light, a shadow cast by the phone itself, and a warm indoor bulb all wreck legibility. Warn on the capture screen rather than saving something the recipient cannot read.
  • Compression that looks fine on a full-page view destroys eight-point text. Set the quality floor against the small print, not against the photo as a whole.
  • A user who leaves mid-scan must not lose the pages already taken, and abandoned captures must not sit in temporary storage indefinitely.
  • A phone rotated between shots produces pages at different orientations. Normalise each page to portrait reading orientation before assembly.
  • Camera permission can be denied at the start or revoked mid-session. Fall back to the ordinary file picker with a plain explanation, never a dead screen.
  • Scans of identity documents and medical paperwork are sensitive by default. Apply the same retention and read-back rules as any other uploaded file, and do not silently leave copies in the device photo roll.

Definition of done

8
  • A user captures several pages in one session and receives a single ordered document.
  • Detected page edges can be adjusted by hand before a page is saved.
  • Pages can be reordered, retaken, and deleted before the document is committed.
  • Small text stays legible in the compressed output.
  • Denied or revoked camera permission falls back to a file picker with an explanation.
  • A scan captured from the camera is subject to the same limits, scanning, and retention as a file chosen from disk.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.