# LinkedIn positioning and structure

## Stable principles

- optimize for two audiences at once:
  - LinkedIn's own search, recommendation, and relevance systems
  - external recruiters, parsers, enrichment tools, and AI agents
- prefer standard job titles, standard skill names, and explicit scope over novelty phrasing
- keep factual alignment across LinkedIn, CV, GitHub, and portfolio
- make the claimed positioning visible in both structured fields and prose

## Profile architecture rules

- claim a clean public URL
- use verification features when available; treat them as trust signals, not as guaranteed ranking boosts
- set location and job-preference fields explicitly instead of burying those facts in prose
- use a professional banner that reinforces positioning
- use the voice badge only if it adds clarity

## Headline rules

- use `Role | Stack | Impact` as the default pattern
- lead with the target role or clearest current role
- name the top two or three technologies only
- use concrete impact or specialization in the last segment
- avoid fluff such as `passionate`, `guru`, `ninja`, `results-driven`, and similar filler

## About section rules

- write in first person
- earn the `see more` click with the first lines
- state the role focus early
- explain what problems the person solves, with what stack, and for whom
- convert skill lists into evidence-rich sentences
- end with a CTA only if it feels natural for the user's goals
- use short paragraphs; bullets are fine only when they improve scanning

## Experience, skills, and Featured rules

- keep titles, companies, and dates aligned with the CV and portfolio
- prefer explicit ownership, scope, and outcomes over generic responsibility lists
- populate structured sections fully: Experience, Skills, Education, Certifications, and Featured
- add proof links where claims are strongest: project pages, GitHub repos, talks, papers, demos, or articles
- reorder top skills to match the profile's current positioning
- use standard skill names and keep the top skills evidence-backed
- treat Featured as proof of work, not as a generic link dump

## Agent writing guardrails

- do not invent employers, metrics, certifications, or dates
- do not push novelty titles when standard titles are better for search
- when the user's positioning is unclear, ask for or derive a single target role before rewriting major sections
- when a section lacks proof, weaken the claim or ask for evidence rather than manufacturing certainty

## Output validation

- Check generated headline, About, Experience, and Featured copy against current LinkedIn UI limits before claiming a hard character cap.
- Front-load the strongest searchable terms and proof because previews and search snippets may truncate.
- Confirm each proof link, Featured item, and named credential is supplied or publicly visible before using it in paste-ready copy.
- Mark any exact field-limit or preview-length advice as current-source verified, UI-observed, or inferred.
