Run decision-grade, multi-perspective research using Boardroom STORM (an adaptation of Stanford's STORM method). Use when the user wants a rigorous research report, market map, investment/diligence memo, competitive analysis, board memo, product strategy, or long-form thesis on an ambiguous topic where smart people would disagree — anything where a shallow consensus answer is costly. Triggers: "run Boardroom STORM", "STORM research", "research X thoroughly", "build a diligence/thesis/board memo", "map this market". Do NOT use for single factual lookups answerable with one or two web searches.
Produce single-file HTML artifacts instead of markdown when content has visual, spatial, or interactive shape — comparisons, diagrams, timelines, animation sandboxes, clickable flows. Use before writing a long markdown response whose content would skim better as a "document you'd actually read".
Triage CodeRabbit PR review comments — verify each finding against the current code, apply valid fixes, and post reasoned replies to skipped comments via the `gh` CLI. Use when the user asks to "handle CodeRabbit comments", "address the CodeRabbit review", "answer CodeRabbit on the PR", or pastes CodeRabbit feedback and wants it triaged.
Map historical events onto thriller structure. Choose the right POV (observer OR protagonist — context-dependent), define the ending first (John Irving rule), validate the procedural engine (five-test check), select an act structure (Harris ticking-clock OR Garrett business-building), map events to thriller beats, and compress dead zones. This is pre-writing architecture — does NOT include drafting or revision.
Build and maintain a structured novel bible (character profiles, world entries, voice rules, continuity tracking) optimized for AI-assisted scene drafting. Use when starting a new book or series, when prose output lacks voice consistency or character distinctiveness, when continuity errors appear across scenes, or when you need to define what context gets loaded during drafting sessions.
Plan and structure civilization-builder, progression, and institutional-building fiction. Use when plotting novels where the engine is BUILDING rather than INVESTIGATING — technology uplift, kingdom building, institutional development. Covers 8-beat builder structure, series architecture, craft-sequence pacing, ticking clocks, and power-creep prevention.
Craft techniques for writing transmigration/isekai/time-travel fiction where a modern protagonist deploys knowledge in a historical setting. Covers knowledge deployment pacing (Padway Ladder, Anderson Correction, Eclipse Gambit), dual-knowledge systems and bidirectional exchange, fish-out-of-water orientation, arrival mechanisms, teach/learn ratio as quality predictor, and failure mode avoidance. Use when drafting or revising scenes involving modern knowledge in a pre-modern world, designing knowledge-deployment arcs, handling the collision between modern and historical expertise, or auditing transmigration fiction for common failure modes.
Write cross-cultural, fish-out-of-water, and diasporic fiction scenes. Use when writing scenes where a protagonist navigates an unfamiliar culture — cultural mistakes, language gaps, learning sequences, teaching across conceptual gaps, orientation pacing. Covers 9 scene types, 3 orientation models, 6 language-gap techniques, diasporic protagonist craft, and worldbuilding through action.