'synthesis' 검색 결과

Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Multi-step autonomous research methodology for deep investigation tasks with structured synthesis

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deep cross-domain synthesis engine for the vault. Triggers on "synthesize X", "what do I know about X", "connect ideas about X", "cross-domain analysis of X", "map everything in the vault about X". Searches comprehensively, surfaces non-obvious patterns and tensions, then challenges the user to generate original thought. The vault should surprise you — if synthesis only confirms what you already think, it failed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks for a weekly synthesis, a weekly report, or a "what you need to know this week" digest from team reports. Not for the underlying reports or ad-hoc summaries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

コンペ戦略の横断synthesis を実行する。competition-strategist agent を起動し、daily_reports/* と全 SESSION_NOTES.md / claudeSummary.md / submit/SUBMISSIONS.md / KAGGLE_DIRECTION.md を一括ロードして「次の一手」を出力する。週1回や局面の変わり目で使う。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Search academic papers and conduct literature reviews using OpenAlex API (free, no key needed). Use when the user needs to find scholarly papers by topic/author/DOI, explore citation chains, get structured paper metadata (title, authors, abstract, citations, DOI, open access URL), fetch full text of open access papers, or conduct automated literature reviews with theme identification and synthesis. Triggers on requests involving academic search, paper lookup, citation analysis, literature review, research synthesis, or scholarly reference gathering.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Systematic literature review methodology for social science research. Use when conducting systematic reviews, research synthesis, meta-analyses, scoping reviews, or comprehensive literature searches across economics, political science, sociology, education, public health, and development. Produces structured notebook cells with search strategy, evidence table, thematic synthesis, and gap analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert-level stellar physics covering stellar structure and evolution, nucleosynthesis, stellar atmospheres, variable stars, binary systems, and stellar populations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert-level organic chemistry knowledge. Use when working with organic reactions, mechanisms, functional groups, stereochemistry, synthesis planning, spectroscopy, or named reactions. Also use when the user mentions 'organic reaction', 'mechanism', 'functional group', 'stereochemistry', 'synthesis', 'NMR', 'IR spectroscopy', 'SN1', 'SN2', 'elimination', 'addition', 'aromatic', 'carbonyl', or 'named reaction'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Research] Use when a workflow step or the user asks for synthesis of existing evidence into a cited research report.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds DRAFT user personas from the research notes, interview summaries, survey free text and support themes the user provides: for each persona the goals, pains, jobs to be done, context of use, quotes exactly as supplied with their participant codes, and the evidence count behind every attribute, with names, demographics and any detail no participant stated left UNKNOWN rather than invented. Use when the user asks to "build personas from these interviews", "who are our users based on this research", "draft user personas", "turn these research notes into personas" or "update our personas with the new interviews". Do not use for theming a batch of customer feedback into counts, use customer-feedback-theme-synthesis instead; for exit interviews, use exit-interview-synthesis; for the requirements those personas imply, use product-requirements-draft. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 7 modes: full research, quick brief, paper review, lit-review, fact-check, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question formulation, Socratic mentoring, methodology design, systematic literature search, source verification, cross-source synthesis, risk of bias assessment, meta-analysis, APA 7.0 report compilation, editorial review, devil's advocate challenges, ethics review, and post-research literature monitoring. Triggers on: research, deep research, literature review, systematic review, meta-analysis, PRISMA, evidence synthesis, fact-check, guide my research, help me think through, 研究, 深度研究, 文獻回顧, 文獻探討, 系統性回顧, 後設分析, 事實查核, 引導我的研究, 幫我釐清, 幫我想想, 我不確定要研究什麼, 研究方向, 研究主題.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

複数の AI / 人間レビュー結果 (review-self / review-external / findings-pool) を統合し、実在性・重大度・対応優先度・merge 可否を検証する。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with Aws Cdk Deep — aWS CDK application and stack management. Covers stack synthesis, CloudFormation template inspection, diff analysis, deployment orchestration, context values, asset management, and construct library usage. Use when managing CDK apps, debugging synthesis errors, reviewing stack diffs, or analyzing deployed CloudFormation resources.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AiZynthFinder retrosynthetic route planning (CASP) from AstraZeneca Molecular AI. Monte Carlo tree search guided by a template-based neural expansion policy recursively disconnects a target SMILES until precursors are found in a purchasable stock. Covers config.yml (v4 format), aizynthcli batch screening, the AiZynthFinder/AiZynthExpander Python API, one-step disconnections, custom stocks via smiles2stock, scorers, Retro*/breadth-first/DFPN search alternatives, and reading output.json.gz / trees.json. Use for synthesis route planning, synthesizability screening, and building-block/precursor search. For reaction barriers use neb-irc-activation-energy; for 2D reaction scheme drawing use rdkit-chemdraw-cdxml.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Performs retrosynthetic planning using AiZynthFinder (MCTS, template-based), Chemformer (template-free transformer), ASKCOS, and emerging RetroSynFormer with explicit handling of route scoring, building-block availability (eMolecules, Enamine, Mcule), forward prediction validation (Molecular Transformer), and disconnection-aware multi-objective search (MO-MCTS). Use when assessing synthetic feasibility of generated or selected molecules, planning multi-step syntheses, building synthesis-aware design pipelines, or screening libraries for retro-route feasibility.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Performs retrosynthetic planning using AiZynthFinder (MCTS, template-based), Chemformer (template-free transformer), ASKCOS, and emerging RetroSynFormer with explicit handling of route scoring, building-block availability (eMolecules, Enamine, Mcule), forward prediction validation (Molecular Transformer), and disconnection-aware multi-objective search (MO-MCTS). Use when assessing synthetic feasibility of generated or selected molecules, planning multi-step syntheses, building synthesis-aware design pipelines, or screening libraries for retro-route feasibility.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Performs retrosynthetic planning using AiZynthFinder (MCTS, template-based), Chemformer (template-free transformer), ASKCOS, and emerging RetroSynFormer with explicit handling of route scoring, building-block availability (eMolecules, Enamine, Mcule), forward prediction validation (Molecular Transformer), and disconnection-aware multi-objective search (MO-MCTS). Use when assessing synthetic feasibility of generated or selected molecules, planning multi-step syntheses, building synthesis-aware design pipelines, or screening libraries for retro-route feasibility.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Answer a question from the structured wiki before searching the web — "query the wiki", "what do we know about", synthesis request, cross-project research. Returns cited synthesis with wikilinks and counter-arguments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Research synthesis from sources — "summarize these URLs or papers", "research this topic with these sources", "create a podcast about", "audio overview", "mind map", "quiz from these sources", "flashcards", "deep research on". Wraps Google NotebookLM via notebooklm-py.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

현재 대화와 코드베이스에 대한 이해를 바탕으로 명세서를 작성해 프로젝트 이슈 관리 시스템에 게시합니다. 사용자 요구, 구현과 테스트 방침, 제외 범위를 정리합니다.

• 기능 논의를 명세서로 정리
• 합의한 요구 사항을 이슈로 게시
• 구현과 테스트 방침 문서화

학술 및 기술 문헌을 검색하고 선정 기준에 따라 비교·종합합니다. 검색 이력과 제외 이유를 기록하고 근거의 강도와 인용을 확인하여 문헌 검토로 정리합니다.

• 연구 주제의 전체 흐름 파악
• 검색 절차를 기록한 문헌 검토 작성
• 상충하는 연구 결과와 미해결 과제 정리