github.com/HelixDB/helix-db (link)

commit signals (20)

source signals (3)

• crates/cli/CLAUDE.mdvia claude-code

  # helix-cli
  
  The Helix CLI — binary `helix`, crate `helix-cli` (v3.0.1). It is a **runtime orchestrator**, not a compiler.
  
  ## v2 → v3 shift (read this first)
  
  This CLI has **no `helix compile` and no `helix check`**, and there is **no `.hx` query workflow** in it. (Older notes/memory that mention those commands describe the v2 CLI and are stale.) In v3:
  
  - **Queries are JSON requests** sent to a *running* instance via `POST /v2/query` (`helix query`). Validation happens server-side, in the instance.
  - 

• docs/llms.txtvia unspecified

  # HelixDB
  
  > HelixDB combines a property graph, approximate vector search, and BM25 full-text search behind one operation-tree query model. Requests run through Cloud, a local server, or the embedded runtime.
  
  Quickstart (local instance requires Docker or Podman):
  
  macOS and Linux:
  ```bash
  curl -sSL "https://install.helix-db.com" | bash   # install the helix CLI
  ```
  
  Windows PowerShell:
  ```powershell
  irm https://raw.githubusercontent.com/HelixDB/helix-db/main/crates/cli/install.ps1 | iex
  ```
  
  Then:
  ```bash
  

• AGENTS.mdvia agents-md

  ### approach
  
  - ⁠Make invalid states unrepresentable using algebraic data types (e.g. enums).
  - ⁠Use code coverage tools to make sure unit test coverage covers every edge case. This should be easily doable if invalid states are unrepresentable.
  - Keep things modular.
  - Define clear contract boundaries for testability. Document them all, and make sure doc comment examples are ran as tests.
  - Use assertions for invariants when encoding within types is not feasible.
  - Use clippy and fix code smells reporte

ignorefile signals (0)

none