Use when the user asks what GitNexus is, when to use it (vs sem), what the web UI offers, or how the index/embeddings work. Conceptual reference for the manual human GitNexus setup. Examples: "what is gitnexus for?", "should I use gitnexus or sem?", "what can…
Use when the user wants to run GitNexus to explore or document a codebase: build/refresh its index, open the web UI, generate a wiki, or check status. GitNexus is a manual human tool here — help the user run the `gnx` commands. Examples: "index this repo with…
Expert in Claude prompting, skill creation, hooks management, MCP configuration, sub-agents, memory management, and Claude Desktop app features. Use when writing prompts, creating Claude Code skills, configuring hooks, setting up MCP servers, creating custom…
Analyzes past Claude Code conversations to roast your prompting habits and compute efficiency. Reads user prompts, cross-references with tool errors and corrections, analyzes model/reasoning choices (Fable vs Opus vs Sonnet vs Haiku), then generates dual…
Analyzes past Claude Code conversation logs to learn from mistakes. Extracts tool errors, user corrections, and repeated failures, then writes actionable learnings to auto memory. Use when you want Claude to stop repeating the same mistakes across sessions.
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?"
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree one question at a time. Use proactively while in plan mode and before finalizing or presenting any implementation plan,…
Generates personalized learning plans for any topic (tech or non-tech). Assesses current knowledge, researches official documentation and resources, creates structured learning paths with theory and practice modules. Stores the plan in Obsidian for…