JanDuchscherer104

Use for ARIA-NBV Typst proposal/thesis authoring, shared notation, scientific prose, citations, scientific/geometric figures, tables, Mermaid inclusion, and compile/render QA.

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

Use to localize unknown ARIA-NBV files, symbols, docs, or source families through deterministic local discovery before handoff.

Use when reviewing ARIA-NBV working-tree or PR diffs, following up external/model review findings, or supplying ARIA-NBV domain context to the oh-my-codex code-review harness with severity-ranked file and line findings.

Use to diagnose ARIA-NBV bugs, regressions, failing metrics, Streamlit issues, docs builds, KG failures, or suspicious outputs.

Use when ARIA-NBV work touches pose, camera, coordinate-frame, CW90, PyTorch3D projection, depth backprojection, candidate frusta, or geometry diagnostics contracts.

Stress-test vague, high-impact, research-facing, advisor-facing, or cross-surface ARIA-NBV decisions before implementation, including theory-rich or elaborate Plan Mode option analysis when requested.

Use for ARIA-NBV behavior-preserving pruning of redundancy, dead code, stale compatibility, unused config, or excess LOC.

Use when writing, revising, or reviewing PRML VSLAM final report or slide deliverables under docs/report or docs/slides, including Typst figures, tables, citations, bibliography references, scientific claims, VSLAM metrics, alignment, method or dataset framing, protocol text, limitations, result statements, and final presentation prose.

Create, update, or publish GitHub pull requests with a reviewer-first structure. Use when Codex needs to draft or revise a PR title/body, open a PR from a prepared branch, or reshape an existing PR into a summary paragraph, focused verification list, compact work-package map, and detailed work-package sections instead of a raw changelog.

Create, de-duplicate, structure, sync, and resolve GitHub issues. Use when Codex needs to open a new GitHub issue, rewrite a vague issue into a template-backed body with acceptance criteria, mirror issues between GitHub and another backlog, or close the loop from issue to linked pull request.

Write and refactor concise, contract-focused Python docstrings for modules, public classes, functions, methods, protocols, config models, DTOs, wrappers, and streaming or session APIs. Use when Python docstrings are missing, sparse, misleading, or need better cross-references, examples, units, shapes, lifecycle notes, or boundary semantics.

Use when working with the repo-local MemPalace setup for PRML VSLAM, especially to refresh or search mined docs and Codex chat histories, inspect palace status, or generate wake-up context from the repo-local palace.

Use when the user asks to reduce redundancy, boilerplate, dead code, unused symbols, unused config fields, overcomplication, or Python source LOC through behavior-preserving simplification, pruning, or refactoring in this repo.

Use when working in a repository with graphify-out/, especially before answering architecture or codebase questions and after code edits that should refresh graphify artifacts.

Use when creating, reviewing, or fixing Python Rerun integrations for SLAM, RGB-D, reconstruction, and spatial-vision workflows, especially when work involves transforms and frame conventions, pinhole cameras, depth images, point clouds, timelines, blueprints, or comparing a local integration against official Rerun examples or the repo-local ViSTA-SLAM reference.

Adapt bounded autoresearch loops to litkg-rs. Use when the user wants Codex to run evidence-driven benchmark or code experiments in this repo with a frozen verify harness, explicit baseline, separate guard commands, safe winner/trial branches, and resumable `.logs/autoresearch/` run artifacts.

Use when working on the standalone Rust literature KG toolkit, especially registry merge, arXiv download, TeX parsing, Semantic Scholar REST enrichment, graphify materialization, Neo4j export, and client-repo adapter configs.

Create, update, or publish pull requests for litkg-rs. Use when Codex needs to write a PR title/body for this repository, update an existing PR description, or publish a branch with a structured PR description that follows the general shape of JanDuchscherer104/prml-vslam PR

Use when creating, syncing, triaging, or resolving GitHub issues for this repo or a similar local backlog. Covers issue discovery, de-duplication, issue-body structure, local-stack sync, and issue-closing workflow through linked PRs.

Use when reviewing litkg-rs changes in the working tree or on a GitHub pull request, especially to produce severity-ranked findings with file and line references and to gate autoresearch winner branches before promotion.