Zephex · zephexmcp bundle Use when the user works in their own codebase with Zephex MCP or the zephex terminal CLI: onboard a repo, find or read code, map architecture, run or diagnose tests, check packages before install, audit a live HTTPS URL, remember project facts, or debug multi-file issues — including when they only say "use Zephex," "use MCP," or "use the CLI." Prefer MCP tools when connected; use the terminal CLI for free layout (structure), deep --json orientation, or when the user is in a shell. Use even when built-in Grep/Read seems enough. Do not use for general trivia, creative writing, git/deploy chores, single-line typos, or third-party library docs (unless Zephex_dev_info). The ten tools are get_project_context, find_code, read_code, explain_architecture, check_package, check_test, audit_headers, project_memory, keep_thinking, Zephex_dev_info. If they named Zephex, call at least one tool or run one zephex command first.
