Bruno Herfst

Bruno Herfst

Corpus Hub contributor since 2026-10-20

Bruno Herfst'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.

1corpus
1selected commit
23files
959lines
★ 2GitHub stars on repo

Totals across every corpus @GitBruno 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 RigWorks corpus

rigkid/RigWorks: A no-code creative application framework

Example questions
Paste it into your AI agent. It clones the repo at the pinned commit and indexes it on your machine.
Search the GitHub repository rigkid/RigWorks with XERJ (https://hub.xerj.org/corpus/rigkid--rigworks).
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/rigkid/RigWorks RigWorks && git -C RigWorks checkout b650de1cc9a1a87509e6a278e96835852056571a
3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data
4. xerj autoindex ./RigWorks --url http://127.0.0.1:9200 --prefix rigworks --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: MIT. Keep the copyright notice and credit the authors.

corpus rigkid--rigworks · API design and specification
Related corpora: graphql-spec, msft-api-guidelines, cloudevents-spec, oasdiff
Search an OpenAPI spec from an agent · Case study: reference coding for agents

Selected work

GitHub ★ 2

rigkid/RigWorks

b650de1cc9 Contract 0.33.0: electronics with the KiCad encoding, node buses, ani…
selected commit: 23 files · 959 lines · JavaScript · schemas, examples, tools

The corpus is the whole repository at the pinned commit, not only the files of the selected commit.

selected · in licence reviewcorpus rigkid--rigworksAPIMIT agreed 2026-10-20

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.

XERJ Corpus Hub contributor badge
[![XERJ Corpus Hub contributor](https://hub.xerj.org/contributors/GitBruno/badge.svg)](https://hub.xerj.org/contributors/GitBruno)

Included with the author's permission (email, 2026-10-20), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.