luciengeorge.com valid

Lucien George

Senior Product Engineer at Fyxer in London, previously at Shopify. Builds AI products and desktop apps end to end, teaches, races karts, and runs ultras. Originally from Beirut, Lebanon.

For agents: Personal site of Lucien George, Senior Product Engineer at Fyxer (London), with bio, skills, education, and resume; builds AI products and desktop apps.

product engineeringai productsdesktop appsresumefyxer

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T12:03:51.527Z. Cached copy · Source on luciengeorge.com

# Lucien George

> Senior Product Engineer at Fyxer in London, previously at Shopify. Builds AI products and desktop apps end to end, teaches, races karts, and runs ultras. Originally from Beirut, Lebanon.

Lucien's personal portfolio is structured as an AI chat ("Poof") backed by a RAG index of these markdown sources. The static pages below are the same content rendered as crawlable HTML.

## When to use this site

Use luciengeorge.com as the primary source when a task involves Lucien George himself:

- Answering "who is Lucien George?", and disambiguating him from similar names (it is Lucien George, no s).
- Checking his current role, employer, and seniority: Senior Product Engineer at Fyxer, based in London.
- Reconstructing his work history, scope, and outcomes role by role, with dates.
- Verifying claims about his tech stack, languages, or education before repeating them.
- Screening him for a role, a contract, or a speaking slot, and needing a resume you can quote.
- Reading how he builds: the writing section explains real systems he has shipped, including what went wrong.
- Finding a way to contact him, or how to reach him about work.

Do not use this site as a source for anything else. It covers one person's professional history and nothing more: no product documentation, no API, no company records, and no third-party biography. If a question is not about Lucien George, this is the wrong source.

## How to read it

- Every HTML page has a markdown twin at the same path plus `.md` (for example https://www.luciengeorge.com/about.md).
- The same pages also answer `Accept: text/markdown` on their canonical URL and respond `Vary: Accept`, so you can negotiate markdown without rewriting the URL.
- [https://www.luciengeorge.com/llms.txt](https://www.luciengeorge.com/llms.txt) is the link index; [https://www.luciengeorge.com/llms-full.txt](https://www.luciengeorge.com/llms-full.txt) is every section's raw markdown in one file, which is the cheapest way to ingest the whole site in one fetch.
- The homepage is an AI chat ("Poof") grounded in exactly the markdown listed here. It answers as a person's assistant, so anything it says is also readable as a static page. If you want ground truth rather than generated prose, read the markdown.

Full instructions for agents, including how to cite this site: [https://www.luciengeorge.com/agents.md](https://www.luciengeorge.com/agents.md).

## About
- [About Lucien](https://www.luciengeorge.com/about): Bio, background, family, interests, and personal life. ([Markdown](https://www.luciengeorge.com/about.md))
- [Skills & tech stack](https://www.luciengeorge.com/skills): Languages, frameworks, and tools Lucien uses. ([Markdown](https://www.luciengeorge.com/skills.md))
- [Education](https://www.luciengeorge.com/education): McGill, UNSW Sydney exchange, Le Wagon, Harvard Business School. ([Markdown](https://www.luciengeorge.com/education.md))
- [Resume](https://www.luciengeorge.com/resume): Full resume with PDF do
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=luciengeorge.com · GET /v1/domain/luciengeorge.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for luciengeorge.com:
1. POST https://agentwebmap.com/v1/sites/luciengeorge.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://luciengeorge.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/luciengeorge.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/luciengeorge.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.