Build Resurf
KINDAback to the verdict
Before step 1
you will need
- Chrome or any Chromium browser you are willing to load an unpacked extension into
- Node and pnpm for the build
- Disk space for a few hundred MB of page text and vectors
- Optional OpenAI key if you want better embeddings than the on-device model
Delivery order
Scaffold the smallest runnable application and document its commands.
done whenThe project starts from a documented command in a clean checkout.
Implement the primary data model and core workflow.
done whenThe main object can be created, read and changed end to end.
Add validation, safe failure states, and persistence.
done whenBad input is refused with a readable message and nothing is left corrupted.
Cover the critical path with automated tests.
done whenThe highest-risk behavior fails the suite when it breaks.
Exercise a clean install from the README and fix every missing step.
done whenA fresh clone reaches the first successful workflow using only the README.
That is the whole plan for Resurf. What it deliberately does not cover is below · check the gaps before you call it a replacement.
- Sync across devices and browsers, so your phone reading never enters the index
- Capture on anything that is not desktop Chrome: Safari, mobile apps, in-app browsers
- Robust extraction on SPAs, infinite scrolls, PDFs, and anything behind a login wall
- Curation judgment: your version will resurface plenty of pricing pages and airline confirmations
- Someone else maintaining it against Chrome manifest changes that break extensions on a schedule
Need the files? The project pack on the verdict page hands your agent the whole brief · more bookmarks.