A CV like this

Give this prompt to a coding agent and it builds you a CV site like mine.

My CV is a small Astro site: the content lives in one data file, the page prints on a single A4 sheet, and GitHub Pages publishes it on every push. The prompt asks the agent to follow the same structure, to collect your existing CV, your LinkedIn profile and any other material you have, and to go back and forth with you on drafts until the content is right, before publishing anything.

You need a coding agent that can run commands (Claude Code, Codex, Cursor or similar), Node and a GitHub account. Open an empty folder, start the agent and paste:

The prompt

Build me a personal CV website on the model of https://github.com/ilmeskio/ilmeskio.github.io (the CV at https://consiglio.fyi/cv/). Read that repository first to understand its structure. Use it as a model, not as content: none of its text, photo or personal data goes into my site.

What I want:
- A static site built with Astro and TypeScript, managed with pnpm, with the Node version pinned.
- All the CV content in one typed data file (src/data/cv.ts), separate from the markup. Every text is a pair (or a set) in the site's languages, so the languages change together.
- One CV page per language, with a switch between them.
- Print styles that fit the CV on a single A4 page (check it by printing to PDF), and a "Print / PDF" button.
- Light and dark themes from colour tokens on :root, and a layout that reads well on a phone.
- Deploy to GitHub Pages with a GitHub Actions workflow on every push to main.

How to proceed, in rounds:
1. Setup. Before writing any code, ask me my name, which languages the site should have, whether I have a photo and a custom domain, and whether I also want the same CV in the Europass format.
2. Material. Ask me for everything that describes my work, one source at a time: my existing CV (a file or a link); my LinkedIn profile, exported as PDF (on the profile: More → Save to PDF), since LinkedIn pages usually cannot be read without a login; then anything else, such as a portfolio, GitHub profile, project pages, articles, talks, references or notes. For each source, tell me what you took from it and what is still unclear.
3. Draft. Fill the data file only with facts from that material. Do not invent roles, dates, figures or skills: where something is missing or two sources disagree, leave the field out and add it to a list of open questions.
4. Review. Run the type-check and the build, start the dev server and show me the CV together with the open questions. Take my corrections and any new material, update the data, and repeat from step 2 until I say the content is right. Then check the printed page count again.
5. Publish. Ask me before creating the GitHub repository and before the first push.