Usage guide
Publish the profile as a layer, not a gimmick.
The Markdown file should support your visual portfolio, LinkedIn profile, and conventional resume — not replace them.
Your words
A draft you review
Published in layers
Why Markdown?
AI systems read text and structure — not layout.
Recruiters and sourcing tools increasingly use AI assistants to read, summarize, and compare candidate material. What those systems actually receive is text — and how well they understand you depends on how that text is structured.
Plain text survives every pipeline
A visual portfolio often depends on JavaScript, animation, and images that text-based systems cannot see. A Markdown file is readable by anything that can read at all.
Structure carries meaning
Headings, lists, and front matter map directly to how language models extract facts — so your roles, capabilities, and evidence are less likely to be misread or dropped.
Explicit beats implied
Role fit, boundaries, and keywords stated once, in plain language, leave less room for a summarizer to guess — and hybrid careers suffer most from guessing.
readable ≠ ranked · structure improves how you are understood when your material is read — it does not guarantee you will be found, indexed, or selected
Verify the generated content
- Confirm every employer, client, date, role, tool, award, metric, and project outcome.
- Remove details covered by NDAs, client ownership, or internal confidentiality.
- Replace “Needs confirmation” sections with evidence — or delete them.
- Keep keywords honest. Do not add technologies you cannot discuss in an interview.
Publish on your own domain
Use a simple structure:
/ai-profile Human-readable page /profile.md Raw Markdown profile /llms.txt Optional AI-agent index /case-studies/ Public-safe evidence
The human-readable page should explain what the file is, show the core summary, and link to your visual portfolio, resume PDF, LinkedIn, and a contact route.
Add it to LinkedIn Featured
- Open your LinkedIn profile and locate Featured.
- Add the
/ai-profilewebpage — not only the raw Markdown file. - Use the generated Featured title and description.
- Update your About section manually after adapting the draft to your voice.
Add llms.txt only when useful
Place llms.txt at your website root when you control the domain. Treat it as an experimental discovery aid, not a guaranteed indexing mechanism.
Use the recruiter summary directly
Include the profile-page link and recruiter summary in targeted introductions, proposals, speaker bios, community profiles, and replies to recruiters. Avoid mass-posting the raw file without context.
Recommended framing
“A structured companion to my visual portfolio, making my role focus, capabilities, and public project evidence easier to review.”