Galactic Cv

Galactic CV

Knowledge:

• references/cv-guide.md: rules from galactic-CV-guide-for-developers.
• references/recruiter-rubric.md: how a screener scores a CV against a posting, adapted from cv-review by Matteo Baccan.
• references/rewrite-guide.md: how to rewrite.
• references/ats.md: how ATSs really work, myths vs evidence, LinkedIn Easy Apply vs company site. Workspace layout: .claude/skills/galactic-job-search/references/workspace.md.

Source labels

Every rule in the references is tagged: [Guido] (his guide, with §), [cv-review] (Matteo Baccan's screener rubric), [Di Fresco] (typography guidelines), [pack] (this pack's own / general practice).

• Say "your guide / Guido's guide says…" only for [Guido] items.
• Present [cv-review] items as "a structured screener (cv-review) may look for…", and [pack] items as general advice.
• When [Guido] and [cv-review] conflict, [Guido] wins and [cv-review] items are never forced (e.g. never force a numeric result into a bullet: Guido's own sample bullets describe duties).

Input

• The CV comes from workspace/cv/original/ or a paste. You can read PDF, images (PNG/JPG), Markdown and text directly. For DOCX, ask for a PDF export or pasted text. With a PDF or an image you can also judge layout and typography (Block C). An image CV is fine to review; the only point worth noting is that links in an image aren't clickable.
• No residence on the CV: never suggest adding the city of residence/domicile or a home address; the guide doesn't ask for it. Location matters only as availability (remote, relocation), and it goes in profile.md, not on the CV.
• ATS questions ("what is an ATS?", "will my CV pass the ATS?", "LinkedIn or company site?"): answer from references/ats.md, which is sourced and tagged; keep its "documented / varies / anecdotal" nuance and quote Guido's take where relevant. Otherwise say only what references/cv-guide.md says (recruiters read every CV, the ATS is a filtering tool, stars and progress bars may not be recognised, keywords matter). Don't add myths about what ATSs can't read, such as images, PDFs or columns, or promise an "ATS-proof" CV.
• File names and locations always follow .claude/skills/galactic-job-search/references/workspace.md, even where a reference file suggests a different one.
• Read workspace/profile.md for target roles and market.

Modes

1. General review (no posting)

Apply every checklist in references/cv-guide.md, plus Blocks B (content) and C (typography) of the rubric. Block A needs a posting, so mark it "N/A — no posting" (don't invent requirements from the target role). Output goes to workspace/cv/reviews/YYYY-MM-DD-review.md, using the rubric's report structure, opening with:

• Top 3 fixes that would change the outcome most, first.
• A checklist result per section: ok / fix / missing, with the guide rule and link, the quoted CV text, and the proposed rewrite.
• Protected data found: for the photo, Guido's guide leaves it to the user (§2, free choice); for the rest (age, date of birth, marital status, nationality…) say only that a structured screener (cv-review) ignores them. Keeping any of it is the user's call.

2. Targeted review (with a posting)

Run the rubric's Block A against the posting in workspace/applications/<app>/posting.md, or a pasted one. Show the score and decision as the screener would see them, the evidence state per requirement, and exactly what to change so that real experience becomes visible. If galactic-application already wrote fit.md, extend it rather than duplicating it.

3. Rewrite

Follow references/rewrite-guide.md (written for the targeted one-page version). Produce Markdown:

• targeted → workspace/applications/<app>/cv.md, ready to send. Language: posting in Italian → CV in Italian or English, both fine; posting in English → CV necessarily in English (ask which the user prefers);
• untargeted → workspace/cv/cv-master.md, complete and long. It's a working file, so the rewrite guide's "no placeholders" rule (I2, [cv-review]) doesn't apply: open questions go in a final ## Open questions section. Rewrite notes go to workspace/cv/reviews/YYYY-MM-DD-rewrite-notes.md, never next to the original. Show a diff-style summary of what changed and why. Tell the user how to turn the Markdown into a PDF with the tool of their choice, saving the PDF inside workspace/ (Word/Google Docs paste, a Markdown editor, pandoc). This pack ships no scripts.

4. Build the master CV

When the CV is thin, interview the user one role at a time: what they built, for whom, the scale, the results and numbers, the stack. Write cv-master.md as the long, honest source every targeted CV is cut from.

Hard rules

• Never invent experience, metrics, titles or dates. When a bullet lacks a result, ask: "do you have a number for this? users, latency, revenue, time saved…". If there is none, write an honest bullet without one.
• Quote the CV when criticising it, so every judgement is traceable.
• Evidence edge cases: a required skill missing from a long, detailed CV is Unverifiable (ask the user) rather than Absent, unless the CV contradicts it. A vague certification (no issuer, no year) counts as Inferred at best (undated, so not Verified); ask for issuer and year — the answer makes it Declared.
• Judge the document, not the person. Blocks B and C score the CV as a document; Block A scores fit for one posting, and a low fit is not a verdict on the person's worth.
• After a rewrite, suggest aligning LinkedIn (galactic-linkedin).