epistemelisted

# Episteme Knowledge Graph Hybrid search + graph traversal over a curated database of design patterns, engineering laws, code smells, and refactoring techniques. All queries use the Episteme HTTP API via curl. ## Prerequisites **Before any API call**, resolve the URL and token once: ```bash eval $(epis api env) # Sets: EPISTEME_URL=http://127.0.0.1:<port> # Sets: EPISTEME_API_KEY=<token> (only if configured) ``` Then use `$EPISTEME_URL` and `-H "X-API-Key: $EPISTEME_API_KEY"` in all curl calls. - API server must be running: `curl -sf $EPISTEME_URL/health` or start with `epis api start` - Auth header (when key is set): `X-API-Key: $EPISTEME_API_KEY` ## Arguments | Arg | Action | |-----|--------| | `verify` | Check server is running → `eval $(epis api env)` → `curl $EPISTEME_URL/health` → print status | | `rag status` | Same as verify | ## When to Use Activate automatically when the user expresses any of the following, regardless of technical phrasing: **Code problems — translate complaint into a knowledge graph query:** | User says | API call (run via Bash) | |-----------|---------| | "this class does too much" / file > 300 lines | `curl -s '$EPISTEME_URL/search?q=god+class+large+class+single+responsibility&limit=5'` | | "this function is too long" | `curl -s '$EPISTEME_URL/search?q=long+method+extract+method&limit=5'` | | "code is too complex" / hard to follow | `curl -s '$EPISTEME_URL/search?q=complexity+smell+cognitive+overload&limit=5'` | | "calling DB directly