Clément Delestre
Clément Delestre's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.
Totals across every corpus @clementdelestre appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.
What an agent can do with the fliks corpus
fliks-app/fliks: Your self-hosted movie & TV library, streamable anywhere
- Look up how fliks implements media, nodejs, video, with answers cited to file and line.
- Reuse a worked example: the commit “close job races and scope lists to accessible libraries…” (14 files · Rust, TypeScript).
- Answer from fliks's real Rust source instead of memory (API design and specification).
- How does fliks implement media?
- What does server do in fliks?
Search the GitHub repository fliks-app/fliks with XERJ (https://hub.xerj.org/corpus/fliks-app--fliks). Run these in a shell, in order, and check each result before the next: 1. xerj --help (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh 2. git clone https://github.com/fliks-app/fliks fliks && git -C fliks checkout 625b71cb662d7578972022c9938890eda19902bf 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./fliks --url http://127.0.0.1:9200 --prefix fliks --progress plain 5. xerj autoindex map --url http://127.0.0.1:9200 Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt Licence: AGPL-3.0. Read it for the approach only, do not copy code.
corpus fliks-app--fliks · API design and specification
Related corpora: harper, got, asheeshsahu7300/infinity-media-player, vibecook-dev/truffle
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
fliks-app/fliks
The corpus is the whole repository at the pinned commit, not only the files of the selected commit.
Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.
Sign in with GitHub or Hugging Face to see more: every selected commit in full (commit date, every folder, licence review state, pin) and the pack builds of each corpus.
[](https://hub.xerj.org/contributors/clementdelestre)
Included with the author's permission (email, 2026-10-23), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.