Research

Use when checking in with Jesse about projects and life - I ask questions, he answers, I capture and update Linear/knowledge base

This skill should be used when the user asks about "feedback loops", "iterate on requirements", "continuous documentation", "refine requirements", "update requirements", "requirements changed", "stakeholder review", "validate requirements", "incorporate feedback", "gather feedback", "requirements review meeting", "backlog refinement feedback", "user research findings", "sprint retrospective feedback", "help me gather feedback", "run a feedback session", "get input on my vision", "get input on my epics", "get input on my stories", "collect user feedback", "document feedback from meeting", "review requirements with stakeholders", or when they need guidance on collecting and incorporating feedback throughout the requirements lifecycle.

[Dev] Extracts and organizes best practices for a given topic into a minimal tree structure (max depth 3, max 5 children per node). Use during task planning when writing subtasks in Docs/{name}_Task.md - output is added under each subtask as a concise reference guide. Pure reasoning task with strict formatting rules: keywords/noun phrases only, no prose. (project)

Surface implicit assumptions to verify them against observable code artifacts before building on unverified claims. Use when: (1) claims about code behavior are made without checking what the implementation actually does, (2) planned changes depend on properties not yet verified against tests, types, or runtime behavior, (3) reasoning is based on how software typically works rather than how this specific codebase demonstrably works, (4) assertions about system properties reference expected patterns rather than observed artifacts.

Answer policy questions with strict citations. Refuses to answer without sources.

Choose words for register, connotation, and precision. Use when: (1) asked to adjust formality or vocabulary, (2) text contains words like "delve" or "leverage", (3) writing for technical or general audience, (4) translating between casual and formal language, (5) text uses abstract terms without concrete reference.

Comprehensive guide for programming Reachy Mini robot using Python SDK v1.2.6. Use when working with Reachy Mini robot control, motion programming, sensor access, audio/video processing, or building AI applications. Covers movement control (head, antennas, body), camera/microphone access, motion recording/playback, coordinate systems, and Hugging Face integration. Essential for robotics development, AI experimentation, and interactive applications.

Write technical articles for Zenn in Oikon's distinctive writing style. This skill should be used when creating articles about AI tools, development workflows, tool integrations, updates/new features, or technical reports. The skill provides detailed writing guidelines, article structure patterns, and reference materials based on Oikon's existing articles.

Researches existing libraries before implementation. Required before writing any new functionality. Prevents reinventing the wheel by finding and evaluating existing packages.

Automatic persistent memory for Claude Code sessions. Activates on preference statements ("I prefer", "I always", "I like"), corrections ("no, don't", "actually"), identity statements ("my name is", "I work at"), project decisions, or when the system detects memory-related context. Works invisibly in the background.

This skill should be used when the GM needs to handle Daggerheart combat, including action roll resolution, Hope/Fear token economy, spotlight flow, damage tracking, reaction rolls, and managing combat encounters. Provides action outcome tables, encounter tracking templates, and condition references.

Creates publication-quality scientific plots. Use when making plots, figures, or visualizations. Applies tueplots TMLR styling, LaTeX rendering, no titles.

Use when developing or documenting trading strategies - guides edge hypothesis formation, validates statistical significance, documents strategy rules systematically (entry, exit, risk management). Activates when user says "research this strategy", "document my approach", "test this idea", mentions "trading strategy", "edge", or uses /trading:research command.

Complete adapter lifecycle assistant for LimaCharlie. Supports External Adapters (cloud-managed), Cloud Sensors (SaaS/cloud integrations), and On-prem USP adapters. Dynamically researches adapter types from local docs and GitHub usp-adapters repo. Creates, validates, deploys, and troubleshoots adapter configurations. Handles parsing rules (Grok, regex), field mappings, credential setup, and multi-adapter configs. Use when setting up new data sources (Okta, S3, Azure Event Hub, syslog, webhook, etc.), troubleshooting ingestion issues, or managing adapter deployments.

Editor for non-fiction texts. The audience is business analysts and senior managers.

Write publication-ready LaTeX research papers with citation integrity.Use this skill when:- Writing a research manuscript from notes/results/figures- Creating LaTeX documents for Nature, Science, IEEE, ACM, APS, ACS, Elsevier journals- Ensuring citation keys match bibliography entries- Building and packaging papers for submissionKey features:- Template-pluggable system (8+ publisher templates)- Citation integrity gate (prevents invented bib keys)- Asset audit (catches missing figures)- Build automation via latexmk- Submission packaging (flattening, zip)

Navigate between concrete details and abstract principles to find the thinking altitude where problems become solvable. Use when: (1) asked to zoom in on specifics, zoom out to big picture, or move between abstraction levels, (2) stuck in implementation details without seeing the pattern or floating in abstractions without actionable steps, (3) discussion needs grounding in concrete examples or needs elevation to identify transferable patterns, (4) explaining concepts to audiences at different expertise levels who need different altitudes to understand.

Execute implementation plans using strict TDD workflow with quality gates. Fifth phase of research-discussion-specification-plan-implement-review workflow. Use when: (1) Implementing a plan from docs/workflow/planning/{topic}.md, (2) User says 'implement', 'build', or 'code this' after planning, (3) Ad hoc coding that should follow TDD and quality standards, (4) Bug fixes or features benefiting from structured implementation. Writes tests first, implements to pass, commits frequently, stops for user approval between phases.

Automatically use Perplexity search for personalized context enrichment. Use when facing unfamiliar technologies, decision points, learning questions, or preference-dependent choices.

List, search, and reference prior reasoning sessions to build on previous work Use when: (1) asked to reference or build on prior reasoning sessions, (2) At the start of `/reason` or `/reason-session` to check for relevant prior work, (3) When the user mentions something they worked on before, (4) When you need context about past decisions in this repository, (5) Before starting work that might duplicate prior reasoning, (6) When synthesizing insights across multiple reasoning sessions