Render markdown to clean HTML + PDF + DOCX with professional resume/cover-letter CSS. Headless Chrome PDF gives exact browser fidelity (no LaTeX needed). Auto-detects cover-letter styling from filename. Use when the user asks to convert markdown to PDF, make a clean printable version, render for sharing or printing, generate ATS-friendly resume/cover-letter exports, or "press" a markdown doc to publication-ready format.
Write prose in the user's published voice (Jake Krajewski / medium.com/@jakekrajewski) — warm-tutor register, peer-not-authority, goofy-specific asides, personifies tools, acknowledges reader frustration directly. Invoke when the user asks for an essay, article, blog post, long-form note, or rewrite in his voice. Do NOT invoke for code, terse chat replies, or bullet-style reference/cheatsheet docs.
Scaffold a new Obsidian vault with the canonical layout — WORKSTATE, ARCHITECTURE, CHANGELOG, README, CLAUDE.md, per-folder READMEs — so the living-docs auto-update hook can maintain it. Invoke when user says "init a new vault", "create a vault", "scaffold a vault", "new Obsidian vault", or similar.
Convert arXiv papers to LLM-consumable markdown. Invoke when user provides an arXiv ID or URL, or when syncing academic papers from a PDF folder to a markdown destination.
Reference documentation for analyzing Claude Code conversation history files
Invoke IMMEDIATELY via python script when user requests codebase understanding, architecture comprehension, or repository orientation. Do NOT explore first - the script orchestrates exploration.
Use when starting a session, switching tasks, or needing project context. Also use when you catch yourself about to ask a question the project docs might answer, or when you're about to jump into implementation without understanding the codebase.
Use when designing team culture, onboarding experiences, gym environments, coaching relationships, or any context where group dynamics matter. Covers belonging cues, psychological safety, vulnerability loops, and purpose signals. Use when the user mentions "team culture", "belonging", "psychological safety", "onboarding experience", "gym culture", "toxic culture", "new member experience", "vulnerability", "trust building", "group dynamics", "bad apples", or "purpose". For motivation systems, see drive-motivation. For habit loops, see hooked-ux.