Turn Your Résumé Into an AI Career App
Your career history is structured data pretending to be a document. This guide turns it into a working product — and the product itself becomes the portfolio piece.
the stack
Two tools, clear division of labour
Claude
Organize your experience, define the product, write the requirements, and design the AI behaviour.
Lovable
Build the actual screens, data model, and working workflow from those requirements.
Turn my career history into structured data I can build on. For each role and project, extract: - Title, organization, dates, scope - Skills and tools used - Business outcome (mark [NEEDS NUMBER] where missing) - Stakeholders and decisions I owned - A one-line story hook Output as a clean list I can paste into an app builder. My career history: [PASTE]
the product
Three capabilities — nothing more
Experience Library
Stores projects, accomplishments, skills, and career stories in one structured place.
Job Match Workspace
Paste a job description, see which experiences map to it and where the gaps are.
Interview Story Builder
Turns a stored experience into a structured, truthful interview answer.
Write a PRD for a personal AI career assistant with exactly three capabilities: Experience Library, Job Match Workspace, Interview Story Builder. For each capability define: the user goal, the screens, the inputs, the AI behaviour, the empty state, the error state, and the data that needs to be saved. Screens: 1. Landing page 2. Dashboard 3. Experience Library 4. Job Match Workspace 5. Interview Story Builder Keep the scope small enough to prototype in an AI app builder.
Specify the Interview Story Builder. It takes a saved experience plus a question type, and produces a draft structured as: Situation, Task, Action, Result, Reflection. The AI must not write answers for the user to memorize. Instead it should ask for missing context, point out where evidence is thin, suggest a stronger framing, and leave the final wording to the user. Design requirements: editable output, saveable versions, and a clear [NEEDS NUMBER] marker wherever a metric is missing.
the data
Your main records
- Users — account information
- Experiences — projects, roles, accomplishments, skills, outcomes
- Job targets — pasted job descriptions and their extracted requirements
- Matches — which experiences map to which requirement, and how strongly
- Stories — generated and user-edited interview answers, versioned
Ship one workflow, not five
Start with your own redacted résumé and build one path end to end: select an experience → create an interview story → edit and save it. A single working workflow beats five half-built screens.
Next guide
Explain the App You Vibe Coded