# Style rules the auditor checks A copy of the application-drafter's rules, so this skill stands alone. "Script" marks what `scripts/check_text.py` checks; the rest is read by the model. ## All texts 1. **No em dashes** (U+2014), no `--` and no spaced en dash (U+2013) standing in for one. Script. A spaced hyphen between words may stand in for one too (script, check). 2. **British spelling**: colour, organise, analyse, centre, modelling, programme (a scheme; a computer program stays program). Employer, product and team names keep their own spelling. Script, check. 3. **Oxford comma** in lists of three or more: "Python, SQL, and Spark". Script, check. 4. **Less is more**: sharp, short sentences, one idea each; cut words that carry nothing. 5. **Banned phrases** (`scripts/banned_phrases.txt`; script): I am passionate about, passionate, I believe I would be a great fit, a great fit, leverage my skills, hit the ground running, drive results, results-driven, synergy, synergies, think outside the box, proven track record, wear many hats, fast-paced environment, dynamic environment, I think I could contribute, I think I could, I feel that I, I hope to be able to, team player, fast learner, quick learner, self-starter, detail-oriented, to whom it may concern, I am writing to apply, I am writing to express my interest, please find attached. The fix replaces the phrase with the evidence it stood in for. 6. **No buzzwords without backing**: every claim carries an example, number or fact. 7. **No humble hedging**: "I bring X, demonstrated by Y", not "I think I could contribute". 8. **No unverified company claims**: products, partnerships, technology, expansion, offices, client segments must trace to a fetched page from the company or independent reporting, never to a snippet or a link inside the posting. 9. **Grounding**: reframed emphasis is fine; changed facts and escalated numbers are not. 10. **Backtrack test**. OK: reordering, natural synonyms, emphasising one aspect of a broad role. Flag: merging academic and industry work into one industry-sounding claim; the posting's exact term for adjacent but different work. Never: experience or a domain the candidate lacks, raised numbers, upgraded titles or ownership. 11. **No icon glyphs** (phone, envelope, pin symbols, emoji). Script. 12. **Voice**: warm but direct, first person and active in letters and posts; CV bullets start with a verb or a bold label; demonstrate, do not state; vary bullet openings. 13. **Language**: letters and forms in the posting's language, written natively; CV headings in the CV's language. 14. **Confidentiality**: no colleague or reference names, no unmasked clients, no private matters, nothing the pitfalls document marks as confidential. ## CV - Two pages, single column. Page one: contact line, a 3-4 line profile, recent experience at most one page (script estimates, check). Page two: earlier experience, education, skills, talks and publications. - **At most 5 bullets per role** (script), fewer for older roles (script, check), **each at most 2 lines**, ideally 1 (script, at 90 characters per line by default). - Measurable results only where the career master has them. - The posting's own terms in section headings and competency labels where truthful; every stated requirement covered or honestly gapped. - In-progress qualifications say so in the entry ("In progress, expected June 2027"). - **ATS**: email and phone as plain text in the body (script: present; not only as a link target; not only in a Word header or footer); date ranges as ASCII `2016-2024`, `Mar 2016-Jul 2016`, `2021-present`, never an en dash or other Unicode dash (script); every role with a start and an end; no layout tables, text boxes or columns (script for .docx, check). ## Cover letter - **250-300 body words** between salutation and sign-off (script). - Forward-looking, not a CV repeat: the employer's tasks the candidate will solve and how; 1-2 past examples back the forward claims. - Why this company early, right after the opening, with verified facts only. - Headline: the candidate's title plus one posting keyword. - Requisition ID and start date where the posting has them; other logistics it raises (location, clearance, languages). - Named salutation where a contact is known; never "To whom it may concern" (script). - Every requirement matched or bridged honestly; no contradiction with the CV. ## Form answers - Counted with code, within the portal limit (script with `--limit`, `--word-limit`, `--max-chars`). - Every claim already defensible from the career master and consistent with the CV and letter. - Project entries: the role on the project, never upgraded; ownership scoped where the candidate contributed; project dates only where the career master gives them. - Short-pitch fields: 4-6 variants, each counted. ## LinkedIn posts All-text rules apply, plus confidentiality with extra care: a post is public.