git404hub

what is resume-as-code fr?

nathanfox/resume-as-code — explained in plain English

Analysis updated 2026-05-18

16ShellAudience · vibe coderComplexity · 2/5LicenseSetup · easy

tl;dr

A template that manages a resume as small reusable Markdown files, built with an AI coding agent, so one edit updates every tailored version.

vibe map

mindmap
  root((resume-as-code))
    What it does
      Resume as small partials
      Recipe based variants
      One script builds all
    Tech stack
      Shell
      Markdown
      Pandoc
      Chrome
    Use cases
      Reuse shared content
      Tailor resume per job
      Export PDF and DOCX
    Workflow
      Track sent applications
      Tag applied commits
      AI agent reads CLAUDE.md
    Audience
      Job seekers
      AI agent users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Maintain resume content once in shared partial files and reuse it across multiple tailored variants.

VIBE 2

Generate a new job-specific resume by writing just a headline, summary, and recipe file.

VIBE 3

Build finished resumes as Markdown, HTML, PDF, and DOCX with a single shell script.

VIBE 4

Track which resume version and commit was sent to each employer for later reproduction.

what's the stack?

ShellMarkdownPandocChrome

how it stacks up fr

nathanfox/resume-as-codeai-engineer-skool/zen-agentic-engineer-configali-expandings/mactune
Stars161616
LanguageShellShellShell
Setup difficultyeasyeasyeasy
Complexity2/52/51/5
Audiencevibe coderdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 30min

Requires pandoc and Google Chrome installed locally to build PDF and DOCX output.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

in plain english

Resume as Code is a template for managing a resume the way developers manage source code, and it is meant to be maintained with the help of an AI coding agent such as Claude Code. Instead of keeping one big resume document, the content lives in small Markdown files called partials, one per section or one per job role. A separate recipe file lists which partials to include, in what order, for a given version of the resume. One build script then turns each recipe into a finished Markdown file, an HTML page, a PDF, and a Word document. The main benefit of this setup is that editing a single partial updates every resume variant that uses it, so accomplishments and wording never drift apart between versions. To create a new tailored resume for a specific job posting, a person writes three small files: a headline, a summary, and a recipe listing which partials to pull in and in what order, rather than copying and editing an entire document from scratch. The same job role can even have two different opening framings, such as a general version and a manager-focused version, while sharing the same underlying accomplishments text. Building a resume requires the pandoc document converter and Google Chrome, since PDFs are produced by converting Markdown to HTML and then printing that HTML with a headless Chrome instance. After a build finishes, the script reports each PDF's page count, warns if any resume goes over a configurable page limit, and flags any partial files that are not referenced by any recipe. The repository ships with three example variants already set up: a general, ATS-friendly version for standard online applications, a leadership-focused version for management roles, and a portfolio-focused version that highlights writing and open source work for direct outreach. The project also tracks which resume version and commit was sent to which employer in a log file, so an applicant can check out that exact commit later and rebuild the exact document they originally submitted. A CLAUDE.md file documents the project's conventions so that an AI agent reads them at the start of every session, and the recommended habit is to record any correction given to the agent back into that file. The project is released under the MIT license.

prompts (copy fr)

prompt 1
Walk me through setting up this resume-as-code template with my own content in src/partials/.
prompt 2
Explain how a variant recipe file decides which partials appear in a built resume.
prompt 3
Show me how to create a new tailored resume variant for a specific job posting.
prompt 4
Describe how build.sh converts partials into a PDF using pandoc and headless Chrome.

Frequently asked questions

what is resume-as-code fr?

A template that manages a resume as small reusable Markdown files, built with an AI coding agent, so one edit updates every tailored version.

What language is resume-as-code written in?

Mainly Shell. The stack also includes Shell, Markdown, Pandoc.

What license does resume-as-code use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is resume-as-code to set up?

Setup difficulty is rated easy, with roughly 30min to a first successful run.

Who is resume-as-code for?

Mainly vibe coder.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.