Maintain one durable experiment note in the user's Obsidian vault. Use when planning, launching, updating, resuming, or reviewing a comparable research experiment that needs a hypothesis, core pseudocode, source commit, execution lineage, artifacts, status,…
Plan, launch, monitor, cancel, and hand off a Slurm workload only when the user explicitly invokes `$slurm-execution-contract` or explicitly asks to submit, monitor, cancel, replace, scale, or diagnose a Slurm job. Do not use for routine debugging, short…
Bootstrap or deliberately refresh a Codex Slurm storage-topology policy. Use after installing Codex or these dotfiles on a new Slurm system, after scheduler or storage topology changes, or when the user explicitly asks to reinitialize the Slurm environment.…
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Systematically review and understand old code, data, and analysis files. For reviving old projects, auditing inherited code, or preparing for R&R.
Split large sets of uncommitted changes into logical, well-organized commits. Use when the user has many uncommitted changes and wants structured commits, or proactively suggest when detecting a large diff that would benefit from splitting.
Generate a single-file HTML slide deck from a set of source notes (Obsidian or plain Markdown), a technical writeup, or a cluster of experiment logs. Use this skill whenever the user asks for slides, a presentation, a 발표자료, a deck, a lab-meeting summary, a…
Polish Obsidian or plain Markdown notes by tightening structure, logic, wording, and tone while preserving the author's intent and note type. Use when Codex needs to revise rough notes, expand underwritten sections, improve mixed Korean/English technical…