Genesis
An interactive resume scaffold lands: one big resume JSON, a Next.js app, and a fixed lucide-react import. Nineteen files.
launchdata19 files+2,130−2
About this site
Present
The site as its own case study: how it was designed, the agents that maintain it, and how far it has come in a short time.
01 The site
The site you are reading. A resume-shaped evidence layer built from scratch, then handed a set of AI agent skills that tailor resumes, keep its documentation honest, and now carry its motion language. It started on June 28, 2026 and has not stopped moving.
- Designed the Blueprint Press system: paper, ink, hairline rules, a fixed blueprint grid, and one easing curve shared by every transition, with ten palettes and a dark mode switchable from a local Studio.
- Built a library of repository agent skills that generate job-targeted resume PDFs, keep an Obsidian vault in sync with the code, and distill a motion vocabulary from svelte-bits into this site's own restrained style.
- Went from a single resume JSON to a data-driven Next.js site with a content editor, analytics, a social card, and a job-application tracker, deploying continuously the whole way.
2 images · click to enlarge
This page is the one part of the site that documents itself. The numbers below come from the repository, the timeline is the commit history with the noise removed, and an agent skill refreshes both as the site grows.
0
Commits
on main and its version branches
0
Days in motion
since the first commit
0
Agent skills
8 repo procedures, 15 registered
0
Vault notes
kept in sync by an agent
0
Applications tracked
each with a tailored PDF
0
Projects queued
written, hidden, waiting
Timeline
Key commits, placed by date, playing through in order. Click a dot, or use the arrow keys, to take over.
Playing01 / 26
Genesis
An interactive resume scaffold lands: one big resume JSON, a Next.js app, and a fixed lucide-react import. Nineteen files.
launchdata19 files+2,130−2
Coming Soon, and learning to deploy
A holding page goes up so the deployment and reverse-proxy questions get answered before the design does.
launch10 files+1,493−686
The data split
One JSON becomes a folder of focused files (header, summary, experience, skills, education, projects, proofs), merged at build time. Every later feature depends on this.
data15 files+1,091−2,305
LIVE!
V1.0 declared complete, a Download PDF button wired up, and the site goes public the same day.
launch1,840 files+223,393−8
First application submitted
The reason the site exists starts working: the first job application goes out with a resume built from the same data, and the tracker begins.
goal963 files+222,787−3
Tailored resume submitted to K2 Space
Application 003, Principal Electro-Mechanical Manufacturing Engineer: the posting goes through the resume builder and the PDF it writes is submitted the same day.
goal
The first agent instructions
"Implemented AI": a SKILL.md tells any coding agent how to generate a tailored resume PDF from a job posting. The agent layer begins.
agents4 files+347
Version 2.0 on main
Analytics, speed insights, and the application archive move onto main. The largest commit in the history by file count.
launch2,830 files+448,026−321
K2 Space reached out to schedule interview
7 days after Tailored resume submitted to K2 Space
An email lands asking to set up an interview — the fastest reply of any application in the tracker, and the first end-to-end proof that a resume written from this site's data gets read.
goal
Sitewide update
Version 2.1: a pass over every page while applications keep going out in the background.
design27 files+2,668−670
The vault joins the repo
An Obsidian vault documenting every route, component, data file, and pipeline is checked in, with a vault-sync skill that makes agents keep it current.
agentsdocs36 files+2,132
Blueprint Press previewed at /v3
A new design direction: paper and ink, hairline rules, a blueprint grid texture, Instrument Serif and Spectral. Built beside the old design so both could be compared live.
design27 files+13,854−19
Blueprint Press goes live, classic retired
The new design is promoted to the root, the old one is deleted so the site has one set of URLs, and a favicon and social card land the same day.
designlaunch20 files+37−3,413
Vault and agent rework
One bundled SKILL.md is split into self-contained procedures, each matching its folder, with a README that routes between them.
agentsdocs46 files+912−808
Dark mode
Paper and ink swap to the palette's dark pair; everything else stays. A theme toggle in the nav, remembered per device.
design9 files+224−36
The Studio
A local, dependency-free content editor that reads and writes the data files through a schema-driven form, with backups, atomic writes, and conflict checks. The projects page is rebuilt alongside it.
studio23 files+3,302−38
Themes and fonts from the Studio
Ten palettes plus custom colors, and three font roles, all chosen from a form and applied site-wide as CSS tokens.
studiodesign25 files+1,607−21
Agent skills reworked
Thirteen generic frontend-design skills are vendored in with a lock file, and every repo procedure is registered so any agent can find it.
agents49 files+15,152−11,693
Projects page: calm, then in motion
The pinned, scroll-jacked project panel is replaced by an editorial flow, then given its motion: staggered bullets, media parallax, a scroll-filled spine, and photo wipes.
designmotion5 files+194−55
First project published
ICARUS-Lite goes live with six photos and a full case study, and resume bullets gain reactive action words that take the accent on hover.
content50 files+13,493−299
A motion language, and this page
Three skills distilled from svelte-bits (what to animate, how to build it, how to compose it) are written, then used to build the page you are reading: the date bar, the timeline, the stats, the pins on the screenshots.
agentsmotioncontent40 files+1,202−464
A design critic joins the repository
The impeccable skill arrives with the site's first PRODUCT.md and a real DESIGN.md, then reviews the site and the Studio. One batch follows: the grey ramp fixed for contrast, every label above a heading gone, the evidence link named, a two-row phone nav, a title block in the footer, and the Studio rebuilt as the site's own drafting room.
designagentsstudio
ExtrusionLine Studio
The LabVIEW metrology project is written and hidden in the Studio, waiting on its two proofs (Modbus negotiation, hands-free start) before it publishes.
content
PROTEOR Print and the network
Remote printer operations and the Ubiquiti network project follow, in the order the resume lists them.
content
The tracker returns
The application timeline and table come back to More Info once the Studio can edit them, so the job search stays visible on the site that supports it.
datastudio
Resume PDFs from the site itself
The custom-resume skill already tailors a PDF per posting; the plan is to generate it from the site's own data at request time, so the download button is never stale.
agentsdata
What it's made of
Blueprint Press
The site is set on paper with ink, one accent, and hairline rules, over a fixed blueprint grid you can see through the page. Which colors those are is not fixed in the code: paper, ink, and accent are CSS tokens, filled from whichever palette is chosen in the Studio's Site Settings, so the page re-inks itself from a form. Headings are Instrument Serif, body is Spectral, and every transition on the site uses one easing curve so the motion reads as a single hand.
Skills in the repository
Standing instructions for any AI coding agent live in .agents/ as plain markdown, one folder per procedure, routed by a README. custom-resume builds a job-targeted PDF from a posting and the site's data. vault-sync keeps an Obsidian vault of 35 notes matching the code in the same session as any change. sync-charts keeps the application tracker identical in two places.
A resume that shows its work
The PDF stays the official application document. The site is the evidence layer behind it: each line of the resume links to a project, and each project opens into the problem, the approach, and what changed.
Behind the site
None of this is on the live site. It runs on my machine and in the repository, and it is most of why the site can keep moving.
Job posting
Requirements
Riley Beenders
- Built an automated LabVIEW QC system for real-time tolerance monitoring
- Integrated a multi-board CAN-bus control architecture that simplified wiring and debugging
- Designed and hosted a redundant Kubernetes cluster running a self-developed ERP/CRM
- Researched high-speed linear motors moving a 30 kg payload at 3 m/s with 5-micron accuracy
- Led the design and development of the ICARUS-Lite, owning mechanical, electrical, and software design
One posting in, one page out
The PDF is still the document that gets submitted. When I apply somewhere, an agent reads the posting, pulls the matching evidence out of the same data this site renders, and writes a one-page PDF in the site's format. Anything the data can't back up is left out, not softened.
The live Download PDF button on the home page is the same generator running on demand, so the resume on the site is never a stale file.
- Reads the posting PDF and data/**/*.json
- Fact-only: unsupported claims are excluded
- Checks page count, links, and layout before delivery
Palette
Electric
“Open to relocation” badge
Edit the site from a form, not a code editor
Every word, image, palette, and font on this site comes from JSON files. The Studio is a small local editor that reads and writes them through a form built from a schema, so a content change never means opening a code file.
It only runs on this machine, backs up every save, and writes back byte-for-byte what it read plus the one thing that changed, so the git diff is just that change.
- Ten palettes plus custom colors, three font roles
- Hidden projects keep their write-up until they publish
- Never deployed: it is not part of the site
Triggers on
"Tailor a resume for this posting"
What it does
Reads the job PDF and the site's data, keeps only the claims the data supports, and writes a one-page PDF in the site's format.
Standing instructions any agent can follow
The repository carries its own instructions for AI coding agents, written as plain markdown so any tool can follow them. Each one is a procedure I would otherwise have to remember: how to tailor a resume, how to keep the documentation honest, how motion on this site should feel.
They are the reason a fresh session can pick up work cold and still do it the way I would.
- Plain markdown in the repo, one folder per procedure
- Registered as first-class skills so they trigger on ordinary requests
- A vault of notes is kept current in the same session as any change