CV.Pro: One Resume, Many Versions via Claude Code

Developer Builds Smart Resume Tool That Eliminates the Multi-PDF Nightmare

A developer known as LAWTED has launched CV.Pro, an open-source online resume tool that solves one of the most tedious problems in job hunting: maintaining multiple versions of the same resume for different roles. Built to work seamlessly with Claude Code, the tool lets users generate tailored resume variants through simple URL parameters — no more juggling Word documents, Figma files, or stacks of exported PDFs.

The project, hosted at cv.ha7ch.com with its source code available on GitHub, represents a growing trend of developers using AI coding assistants not just to build software, but to reshape everyday workflows that have remained frustratingly manual for decades.

Key Takeaways

• One resume, infinite versions: URL parameters like ?focus=research or ?role=engineer dynamically adjust which experiences get highlighted
• Claude Code integration: Users can paste a job description and ask Claude Code to rewrite their resume for a specific role in seconds
• No more PDF hell: Eliminates the cycle of editing in Word/Figma, reformatting, exporting, and re-uploading
• Open source: Full codebase available on GitHub for customization and self-hosting
• Role-specific tailoring: Automatically emphasizes papers and research assistantships for academic roles, or shipping experience and tech stacks for engineering positions
• Web-native approach: Resumes live as URLs, making sharing and updating frictionless

The Problem: Why One Resume Has Never Been Enough

Anyone who has seriously job-hunted knows the dirty secret of resume writing: a single version rarely works. When applying for a research position, you want to foreground your publications, research assistantships, and academic contributions. When targeting an engineering role, the emphasis shifts to projects shipped, technical stacks mastered, and production systems built. Product roles demand yet another lens — user empathy, growth metrics, and product thinking.

Traditionally, this means maintaining 3, 5, or even 10 different PDF files, each requiring manual updates whenever your experience changes. One new project means opening every version, editing each individually, adjusting formatting, and re-exporting. It is a workflow that has barely evolved since the early 2000s.

CV.Pro attacks this problem at the architectural level. Instead of storing multiple documents, users maintain a single source of truth — their complete experience set. The tool then uses URL parameters to determine which aspects to emphasize for any given application. A link ending in ?focus=research automatically surfaces academic credentials, while ?role=engineer highlights technical shipping experience. The approach mirrors how modern web applications handle content personalization, applied to the surprisingly static world of resume management.

How Claude Code Transforms the Resume Editing Workflow

The second innovation in CV.Pro is not a feature of the tool itself — it is the workflow it enables with Anthropic's Claude Code. The developer describes the experience of editing resumes with Claude Code as remarkably smooth, a stark contrast to the traditional process.

The old workflow looked something like this:

• Open Word, Google Docs, or Figma
• Manually rewrite bullet points to match a job description
• Adjust formatting that inevitably breaks
• Export to PDF
• Upload to job application portals
• Repeat for every role variation

The new workflow with Claude Code is dramatically simpler:

• Paste the job description into Claude Code
• Say 'Here is the JD — rewrite this resume to better fit an AI engineer position'
• Or: 'Emphasize my research and HCI experience'
• Claude Code edits the underlying resume data directly
• Changes are instantly live at the URL

Because CV.Pro stores resume content as structured code rather than opaque document formats, Claude Code can read, understand, and modify the content with full context. There is no need to parse PDF layouts or navigate complex document object models. The AI assistant simply edits the source files, and the web-based resume reflects changes immediately.

This represents a broader pattern emerging in the developer tools space: applications designed from the ground up to be 'AI-editable,' where the data format and architecture deliberately accommodate AI-assisted modification.

A Growing Trend: AI-Native Personal Tooling

CV.Pro sits at the intersection of 2 significant trends reshaping how developers build personal productivity tools. The first is the rise of AI-native workflows — tools designed not just to be used by humans, but to be efficiently manipulated by AI assistants like Claude Code, GitHub Copilot - AI Tool Review" target="_blank" rel="noopener">GitHub Copilot, and Cursor.

Unlike traditional resume builders such as Canva, Resume.io, or even LaTeX-based templates, CV.Pro treats the resume as a living web application rather than a static document. This architectural choice has profound implications. Web-based resumes can be version-controlled with Git, collaboratively edited, A/B tested with different URL parameters, and — critically — modified by AI coding tools that understand code far better than they understand proprietary document formats.

The second trend is the democratization of software development through AI coding assistants. Projects like CV.Pro, which might have taken weeks of focused development time 2 years ago, can now be prototyped and iterated rapidly with tools like Claude Code. The developer's enthusiasm about using Claude Code to build the tool itself mirrors the end-user experience of using Claude Code to edit resumes — both leverage the same fundamental capability of AI understanding and modifying structured text.

Comparable projects have emerged in adjacent spaces. Tools like JSON Resume pioneered the idea of structured resume data, but lacked the AI integration layer. Services like Reactive Resume offer open-source alternatives to commercial builders, but still operate in the traditional edit-export-upload paradigm. CV.Pro's URL parameter approach and explicit Claude Code workflow represent a meaningful step forward in combining these concepts.

Technical Architecture and How It Works

While the developer has not published extensive technical documentation yet, the GitHub repository reveals a web-based architecture that prioritizes simplicity and AI editability. The resume content is stored as structured data within the codebase, rendered dynamically based on URL query parameters.

The URL parameter system supports several targeting modes:

• ?focus=research — Highlights academic and research experience
• ?role=engineer — Emphasizes engineering projects and technical skills
• ?company=alibaba — Potentially customizes content for specific company applications
• Custom combinations for product, design, or hybrid roles

This approach effectively turns a resume into a lightweight content management system with role-based filtering. Each parameter acts as a lens that adjusts the weight, ordering, and visibility of different resume sections without duplicating any underlying data.

The project is still in early stages — the developer notes that the cv.pro domain has not yet been acquired, and the tool is currently accessible through the ha7ch.com subdomain. The open-source nature of the project invites community contributions and customization, a model that has proven successful for developer-focused tools.

What This Means for Job Seekers and Developers

For job seekers, CV.Pro offers a glimpse of what resume management could look like in an AI-augmented world. Instead of spending hours manually tailoring documents, candidates could maintain a single comprehensive profile and generate role-specific views on demand. Combined with AI assistants that can rewrite content to match job descriptions, the time from 'found an interesting job posting' to 'submitted a tailored application' could shrink from hours to minutes.

For developers, the project serves as a compelling case study in building AI-native tools. The key design decisions — structured data over opaque formats, web-based rendering over static exports, URL parameters over multiple files — all optimize for a world where AI assistants are active participants in content creation and modification.

The broader implication is that document formats themselves may need to evolve. As AI coding assistants become more capable, tools that store content in code-friendly formats gain a significant advantage over those locked in proprietary or binary formats. The resume is just the beginning — the same principles could apply to portfolios, proposals, reports, and any document that needs to exist in multiple contextual versions.

Looking Ahead: The AI-Editable Document Future

CV.Pro is a small project with a big idea embedded within it: documents should be living, parameterized, and AI-editable. As Anthropic continues to enhance Claude Code's capabilities, and as competing tools from OpenAI, Google, and others push the boundaries of AI-assisted development, the gap between 'building software' and 'editing a document' will continue to narrow.

The project's success will likely depend on community adoption and whether the developer can secure the cv.pro domain and build out additional features. But even as a proof of concept, it demonstrates a workflow that many developers and job seekers will find immediately compelling.

In a job market where candidates routinely apply to 50 or more positions, each ideally with a tailored resume, tools that reduce friction from hours to seconds are not just convenient — they are potentially transformative. CV.Pro may be early, but it is pointing in a direction the entire productivity software industry is heading: AI-native, parameterized, and perpetually editable.