eldar

# /eldar — Consult the Eldar The Eldar audit a project's moflo + Claude Code setup for portable, high-leverage gaps. **Audit is read-only by default; `--fix` walks through remediation.** The Eldar consult the **Healer** (`flo healer`, the thematic alias for `flo doctor`), they do not replace them. **Arguments:** $ARGUMENTS ## Modes | Mode | Trigger | What it does | |------|---------|--------------| | Audit | no flag (default) | Read-only scan; produces categorized findings + top-3 recommendation | | Fix | `--fix` | Audit, then interactive triage menu; user picks findings to address one at a time | ## Step 0 — Memory First Before any file reads, run: ``` mcp__moflo__memory_search { query: "guidance rules project conventions stack", namespace: "guidance" } ``` The memory-first gate blocks reads otherwise. The search also surfaces any project-specific conventions the Eldar should weigh in their findings. ## Step 1 — Run the Audit Walk the checklist below in order. Each check is a single category in the final report. Be explicit about what you find — both presence and absence. Severities: `error` (blocks productive work), `warn` (degrades quality), `info` (suggestion). ### 1a. Setup Health — call the Healer ```bash npx moflo healer --json ``` Parse the JSON output. Surface every `failed` check as `error`, every `warn` as `warn`. Do **not** invoke `flo doctor` directly — use the `healer` alias for thematic consistency. ### 1b. Index Freshness Check for `.moflo/moflo...