Research

Investigate a question against official docs, specs, or first-party APIs and write cited Markdown if asked. Use for external/library facts. Skip why *this repo* chose an approach (/why), and academic literature/theses (academic).

kuker24 72090aa 1.0 KB Updated

File contents

Investigate against primary sources first: official docs, source code, specs, first-party APIs. Follow every claim back to the source that owns it.

Use a subagent if this session supports one; otherwise research inline. Do not require a background agent.

Current library or framework docs: MCP context7 when repo evidence is not enough. Broader web: WebSearch / WebFetch. Foreign exa only if already connected.

If the user asked for a note, write one Markdown file in the repo (match existing convention). Cite each claim. If they only wanted an answer, do not create a file.

This is not /why. Repo history, PRs, and local design rationale stay on /why. Scholarly papers, literature surveys, and academic peer review route to academic.

kuker24/OpenCodeBestFriend/tree/main/skills/research commit 72090aa673

Frequently asked questions

npx skillmds@latest add kuker24/research