mettafore

Use when building, styling, or reviewing any Jyotish Helper UI — components, colors, fonts, the North Indian chart, the time slider, glass panels — to keep the look consistent with the approved "Saffron Gold" direction.

Use after merging a branch to main or cutting a release, to bring README.md and docs/architecture.md in sync with what actually shipped.

Use when the user wants to deploy, ship, or push the Jyotish Helper app live to production (Vercel) — merges/pushes to main and runs the Vercel prod deploy.

Use when the user wants to run, start, preview, or view the Jyotish Helper app locally in a browser — starts the Vite dev server and opens it.

Pedagogical mode for gdl-papers. Trigger: user message starts with "?" (e.g. "? what next in model.py"). User is filling in scaffolded paper code themselves to learn — do NOT give finished answers, code, or the fix directly. Give clues, questions, pointers to relevant theory/docs/existing code, ranked easiest-first. Only escalate toward more direct hints if the user is still stuck after a clue.

Explains how the gdl-papers repo is organized. Use when asked where code should go (src/gdl vs papers/), how to add a new paper, what the run-folder or config.json layout is, or how train/evaluate/skills fit together. A map for navigating and extending the repo — NOT for running training (that's run-paper).

Run a paper's training or evaluation in the gdl-papers repo. Use when the user says "train <paper>", "evaluate <paper>", "run <paper> with lr/epochs/...", or asks to sweep a hyperparameter. Reads the paper's README ## Run + ## Hyperparameters, builds the command, forwards any overrides to CLI args, runs it, and reports the result. NOT for explaining repo layout (that's gdl-repo-map).