Sardor-M

Diagnose Lumen CLI or MCP issues — common errors, SQLite problems, search returning no results, compilation failures. TRIGGER when user reports a bug, error, or unexpected behavior.

Pre-deploy verification for Lumen monorepo — type check, lint, test, build across all workspaces. TRIGGER when user says deploy, ship, release, pre-merge, or CI check.

Reference for navigating the Lumen turborepo — workspace commands, where things live, cross-app imports. TRIGGER when user asks about project structure, where to put files, or how workspaces connect.

Review changed code for Lumen project conventions — catches gotchas that linters miss like wrong hash function, FTS5 quoting, missing .js extensions, interface instead of type. TRIGGER when user asks to review, check, or audit code they wrote.

Search, query, and explore the Lumen knowledge base via MCP tools. TRIGGER when user invokes /lumen or asks about their knowledge base, sources, concepts, or graph.

Scaffold a new page or component for the Lumen Next.js web app. TRIGGER when user asks to create, add, or build a new page, route, or dashboard section.

Scaffold a new Lumen CLI command following the Commander.js register pattern. TRIGGER when user asks to create, add, or implement a new CLI command or subcommand.

Scaffold a new Lumen module (store, ingest, search, chunker, etc.) following project patterns. TRIGGER when user asks to create, add, or scaffold a new module, extractor, or store layer.

How to produce a performance or cost number for FleetLM that is safe to publish. Use before adding any throughput, latency, cost, or efficiency claim to the README, a benchmark file, or a post.

Start a local FleetLM fleet and drive real work through it - orchestrator, one or more nodes, an interactive request, and a batch. Use when asked to run, demo, or verify FleetLM end-to-end, or after changing the orchestrator, node agent, or wire protocol.

Always-on knowledge brain. Fires on every message to check memory first and capture new knowledge after.