cv-studio

cv-studio — one profile → ATS PDF · visual CV · tailored letter · LinkedIn

A CV is two artifacts with opposite constraints (this is the load-bearing insight):

1. The ATS-submitted PDF is a data input, not a design piece. It must be single-column, real selectable text, tagged. A multi-column Figma graphic parses into interleaved garbage — the extractor reads across columns, so "Skills … SQL Senior PM Python" becomes one mangled job title and you drop out of keyword search. → Typeset it with RenderCV (below).
2. The human/portfolio version (personal site, a PDF handed to a person) is where design shines. → Route that to the owner's design-studio / figma / ui-ux-pro-max pipeline.

Never design the submitted CV as a graphic. Typeset it; design the portfolio variant only.

The one input: profile.yaml (JSON Resume superset)

Everything derives from a single YAML file — a JSON Resume document plus three x_ extensions that enforce honesty. See assets/sample-profile.yaml for a complete worked example and references/schema.md for the field map.

• Standard blocks: basics, work, education, skills, projects, publications, awards, certificates, languages, volunteer, interests, references.
• x_master — per-role achievement bank, keyed "Company|Position". The ONLY sanctioned source for bullets. You rewrite these long-form notes into punchy bullets; you never invent.
• x_metrics — verified figures only. A bullet may cite a number iff it appears here.

Modes

The pipeline (deterministic; scripts do the mechanics, you do the content)

The zero-fabrication discipline (non-negotiable)

Cover-letter mode

LinkedIn mode (folded in — a separate skill would be catalogue tax)

Visual / design-led CV

Acceptance

References (pulled on demand — do not inline)