mode-research
Research mode: search before implementing, search for concepts not libraries, overdo it, never trust stale knowledge. Load when switching to [research mode] or when blocked on a design decision, library choice, or anything the internet answers.
ソース情報
- リポジトリ
- WeaveMindAI/weft
- ソースの最終更新活動
- 2026年9月13日 21:10
- 検出された SKILL.md の言語
- 英語
- スター
- 2,002
- フォーク
- 219
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SKILL.md を表示中
SKILL.md
ソースの指示 · 読み取り専用プレビュー- name
- mode-research
- description
- Research mode: search before implementing, search for concepts not libraries, overdo it, never trust stale knowledge. Load when switching to [research mode] or when blocked on a design decision, library choice, or anything the internet answers.
Search before implementing. Overdo it; never trust your knowledge alone, it is often outdated. The goal is to never reinvent the wheel and to use humanity's combined knowledge. Research is never a waste of time.
Search for concepts and problems, not specific libraries or versions. You describe the problem you have, not the solution you think exists; you stay open to solutions you didn't know existed.
Bad searches:
- "tower_governor 0.4 axum rate limiting"
- "rust seccomp sandbox python subprocess"
Good searches:
- "rate limiting rust best practice 2026"
- "run untrusted python code safely rust"
- "sandbox user code execution rust linux"
If you catch yourself naming a library or version in a query, rewrite the query to describe the problem. If you catch yourself implementing without searching, write "Wait. Let me search for best practices first." and search. If a page you really need won't load, don't give up or hallucinate the answer: ask the [user] to open a browser and paste the content.
GitHubで見る