Guidance for using external MCP tools safely.

Guidance for routing math queries between calculator and Wolfram Alpha.

Guidance for workspace file tools vs shell commands.

Guidance for using Developer Studio tools to inspect, edit, test, and review code workspaces safely.

Guidance for creating and editing designs using the designer tool.

Guidance for data visualisation and chart creation.

Guidance for Google Calendar event creation and management.

Guidance for delegating focused work to child Agents.

Strategic patterns for effective browser automation — research, forms, and data extraction.

Design effective automated workflows using scheduled tasks, prompt chaining, and delivery channels.

Periodically review memory for contradictions, gaps, stale information, and controlled improvement proposals.

Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.

Write in a natural, human tone — no AI-speak, no filler, no corporate fluff.

Workflow for creating, testing, enabling, promoting, and removing Custom Tools from Developer Studio.

Structured workflow for creating professional designs — slide decks, documents, landing pages, app mockups, and motion storyboards.

Analyses datasets with professional rigour — statistical summaries, clear narratives, and well-chosen visualisations.

Compile a morning briefing with weather, calendar, and news headlines.

Capture unstructured thoughts and organize them into structured notes saved to memory.

Adversarial visual-layout audit of a Quarto `.qmd` or Beamer `.tex` deck. Flags overflow, font inconsistency, box fatigue, spacing, and alignment issues. Use when user says "visual audit", "check the layout", "does this overflow?", "look for visual issues", "audit the slides", or after reworking a deck's appearance. Does NOT check writing or pedagogy — pair with `/proofread` or `/pedagogy-review`.

Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action for each (draft reply, calendar hold, scaffold a project, snooze). Use when user says "triage my inbox", "check my academic email", "what needs my attention this week", "go through my mail", or when run as a scheduled routine. NEVER auto-sends or auto-accepts anything.