Build a Resume Editor With a Large-and-Small Model Split
At a glance
A first-time web builder used a larger model to plan and smaller models to implement a resume editor. This workflow is listed under Coding Agents, App Development.
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Set up the front-end and back-end infrastructure first; the author needed a friend's help connecting Vercel, Render and Supabase. 2) Use a larger model, such as Opus 4.6, to brainstorm an implementation plan and write it in Markdown. Hand that plan to smaller models for the coding, then repeat the planning and implementation cycle as the application develops. 3) When an agent incorrectly claims a newer API does not exist, supply its current documentation in the session and continue the implementation. The author iterated on the UI and launched the resume editor for others to try.
How it went
The author estimated roughly 180–200 hours over four months, averaging about 10 hours per week, and said some hover-overlay alignment often took a couple of tries.
Worth knowing
The initial infrastructure required another person's help; the account does not provide a complete deployment recipe.