The career master and the pitfalls document are facts the user pastes or attaches per chat; every rule lives in the skills. build.sh zips each skill into claude-skills/dist/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
79 lines
4.2 KiB
Markdown
79 lines
4.2 KiB
Markdown
# Writing style
|
|
|
|
Applies to every text the skill writes: CV, cover letter, form answers.
|
|
|
|
## Hard rules
|
|
|
|
1. **No em dashes** (U+2014), and no `--` or spaced en dash (U+2013) standing in for one. Use a comma, a full stop, a colon or a new sentence.
|
|
2. **British spelling**: colour, organise, analyse, centre, modelling, programme (a scheme; a computer program stays program). Keep the employer's own spelling in its product and team names.
|
|
3. **Oxford comma** in lists of three or more: "Python, SQL, and Spark".
|
|
4. **Less is more.** Sharp, short sentences. One idea per sentence. Cut any word that carries nothing.
|
|
5. **No clichés or filler.** The banned phrases below never appear. A posting's own buzzword is not a licence to use it as self-description.
|
|
6. **No buzzwords without backing.** Every claim carries a specific example, number or fact.
|
|
7. **No apologetic or humble hedging.** Not "I think I could contribute" but "I bring X, demonstrated by Y."
|
|
8. **No unverified company claims.** Every company-specific statement is verified against a fetched page (see `posting-research.md`), never from a snippet, reviewer research or a link in the posting.
|
|
9. **Reframe emphasis, not substance.** Apply the interview backtrack test below.
|
|
|
|
## Banned phrases
|
|
|
|
- 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
|
|
- I think I could contribute / I think I could
|
|
- I feel that I / I hope to be able to
|
|
- to whom it may concern
|
|
- team player
|
|
- fast learner / quick learner
|
|
- self-starter
|
|
- detail-oriented
|
|
- proven track record
|
|
- think outside the box
|
|
- I am writing to apply / I am writing to express my interest
|
|
- please find attached
|
|
- fast-paced environment / dynamic environment
|
|
- wear many hats
|
|
|
|
Replace the phrase with the evidence it was standing in for. "Fast learner" becomes the thing learnt and how quickly it went into production.
|
|
|
|
## Interview backtrack test
|
|
|
|
Could the candidate explain this line in an interview without saying "well, what I actually meant was..."? If not, it has gone too far.
|
|
|
|
- **OK**: reordering to lead with what is most relevant; natural synonyms for the target domain; emphasising one aspect of a broad role.
|
|
- **Flag**: merging academic and industry work into one claim that implies all of it was industry; describing adjacent work in the posting's exact terminology when the work was not the same.
|
|
- **Never**: claiming experience the candidate does not have; implying a domain they have not worked in; raising a number; upgrading a title or ownership.
|
|
|
|
For each line in the flag zone, ask after drafting: "This bullet is a stretch because X. Keep, soften, or drop?"
|
|
|
|
## Tone
|
|
|
|
- Warm but direct. Confident, not arrogant.
|
|
- Conversational professional: how a confident person talks in a good interview.
|
|
- First person, active voice in the letter ("I built", not "a system was developed"). CV bullets start with the verb and drop the "I".
|
|
- Demonstrate, do not state. Not "I am a team player" but the teamwork and its outcome.
|
|
|
|
## Headline
|
|
|
|
The letter's headline or subject line is the candidate's title plus one keyword from the posting: "Data engineer specialising in streaming pipelines", not "Application for the Data Engineer position".
|
|
|
|
## Bullets
|
|
|
|
- Start with an action verb or a bold label.
|
|
- Be specific: numbers, tools, outcomes.
|
|
- Vary the structure; not every bullet starts the same way.
|
|
|
|
## Emphasis by role type
|
|
|
|
- **Technical roles**: lead with languages, frameworks, architectures, data volumes, pipeline complexity; include independent projects.
|
|
- **Domain roles**: lead with domain expertise and methods; technical skills are tools serving the domain.
|
|
- **Consulting or advisory roles**: lead with stakeholder communication, coordination, client work, bridging technical and business views.
|
|
- **Leadership roles**: lead with delivery ownership, mentoring, building teams or programmes.
|
|
|
|
## Language
|
|
|
|
- The cover letter and form answers use the posting's language and must read as written in it, not translated.
|
|
- The CV language is a profile-level choice (from the career master, or ask once) and does not switch per posting. All CV section headings follow the CV's language.
|