Coding & Dev Tools

Use to find duplicate or repeated support conversations and produce a reviewable merge plan. Trigger for "find duplicate tickets", "customers contacting us twice about the same thing", deduplicating a helpdesk, cleaning up ticket volume, or measuring how much of your contact volume is the same issue submitted more than once.

Use to design overnight and follow-the-sun support — coverage models, handoff quality and measuring what is lost between shifts. Trigger for "after-hours coverage", "follow the sun", overnight support design, night shift vs defer async, handoff packet, shift handover quality, global coverage gaps, or when customers reopen tickets after every handoff.

Use to measure which help articles actually resolve contacts versus merely being read, including contact-after-view and assisted resolution. Trigger for "are our help articles working", article view counts misleading, deflection measurement, contact after reading an article, self-service success metrics, KB ROI, or stopping AI agents from optimising for page views.

Use to build and maintain a reusable bank of QA criteria as observable decision rules shared across scorecards. Trigger for "criterion library", "standardise our QA criteria", "write better rubric items", "was professional is too vague", versioning criteria across teams, or turning adjectives into pass/fail decision rules with examples.

Fast vector similarity search at billion scale.

Stock quotes, history, search, compare, crypto via Yahoo.

Design motivation systems using Autonomy, Mastery, and Purpose (AMP) for products and teams. Use when the user mentions "intrinsic motivation", "gamification isnt working", "team incentives", "autonomy", "mastery", "purpose-driven", "employee engagement", or "reward systems". Also trigger when designing onboarding progression systems, fixing broken gamification, or building team structures that sustain high performance. Covers why carrot-and-stick fails and how to build progress systems. For habit-forming product loops, see hooked-ux. For retention behavior design, see improve-retention.

Scans modified files for debug leftovers before shipping. Catches console.log, debugger, test URLs, and commented-out code.

Track Apple devices and AirTags via FindMy.app on macOS using AppleScript and screen capture.

Send and receive iMessages/SMS via the imsg CLI on macOS.

Manage Apple Notes via the memo CLI on macOS (create, view, search, edit).

Manage Apple Reminders via remindctl CLI (list, add, complete, delete).

Provides expert guidance on PyTorch Fully Sharded Data Parallel (FSDP) training, covering parameter sharding, mixed precision, CPU offloading, and FSDP2.

Debug Node.js via --inspect + Chrome DevTools Protocol CLI.

MaxFuse parameter tuning when protein panel size changes (26 → 59+ markers)

Preventing Jupyter cell hangs with explicit CuPy GPU memory cleanup

Use when tuning RL reward function weights, fixing reward hacking, or addressing P&L gradient issues

Fix F821 undefined name errors for optional dependencies using TYPE_CHECKING

Fixes common PyTorch bugs including percentile calculations, LayerNorm for Conv1d, and buffer edge cases in reinforcement learning and neural network code.

Exclude ALL dotted symbols from yfinance sector lookups and training. Trigger when: (1) yfinance errors on warrants/units/class shares, (2) training notebook fails on excluded symbol types, (3) adding new symbol exclusion patterns.

Broker position reconciliation pattern for live trading systems

Normalize long-form CODEX cycle folders to short form before notebooks run. Trigger: cyc001_reg001_*, hard-coded cyc paths breaking, staged CODEX raw data failing in Notebooks 1/2.

Review and apply GitHub Copilot suggestions on pull requests. Trigger when reviewing PRs with Copilot suggestions.

Derive selection thresholds from market data instead of hardcoding. Trigger when: (1) reviewing hardcoded parameters, (2) volume/price thresholds seem arbitrary, (3) selection returns too many/few candidates.

Dependency Safety Guards

Use when implementing risk-adjusted rewards, discussing Sharpe ratio in RL training, or tuning reward components for risk awareness

Symbol Database Selection Pattern

Populate symbol database with crypto symbols before training. Trigger when: (1) live trader fails with 'CRYPTO VIOLATION', (2) no crypto models in models/rl_symbols/, (3) db.get_candidates(asset_types=['crypto']) returns 0, (4) starting fresh training without crypto.

Design game levels, maps, and environments including layout, pacing, encounters, puzzles, and spatial flow. Use when planning or building individual levels, zones, or game spaces. Also trigger for "level layout", "map design", "zone design", "encounter design", "game world layout", or "dungeon design".

Query gnomAD for population allele frequencies, constraint metrics, and loss-of-function intolerance. Use when interpreting variants, filtering common alleles, or prioritizing genes in rare disease workflows.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downloads, remove duplicates, or restructure projects.

Scholar Evaluation

Synthesize personas and jobs-to-be-done from evidence with confidence levels. Use when: (1) audience segmentation, (2) messaging alignment, (3) feature prioritization inputs. NOT for: stereotype-based profiling.

Write business proposals, RFP responses, statements of work, grant applications, and project pitches. Use when creating persuasive documents that secure funding, contracts, or approval. Also trigger for 'business proposal', 'RFP response', 'statement of work', 'SOW', 'grant proposal', 'project pitch', 'bid document', or 'proposal template'.

Design interaction flows, states, and microinteractions for usability and feedback clarity. Use when: (1) defining flows, (2) state/error handling, (3) reducing cognitive load. NOT for: final code implementation.