「research」の検索結果

[Workflow] Use when activating the Visual Diagram workflow for create visual excalidraw diagrams from codebase investigation or web research.

日本語の概要は準備中です。原文の説明を表示しています。

[Workflow] Use when activating the Big Feature workflow for large or ambiguous research-driven feature work.

日本語の概要は準備中です。原文の説明を表示しています。

[Research] Use when you need to analyze market landscape: competitors, sizing (TAM/SAM/SOM), trends, SWOT, customer segments.

日本語の概要は準備中です。原文の説明を表示しています。

[Planning] Use when you need to start a new project from scratch with full waterfall inception — idea, research, domain modeling, tech stack, and implementation plan.

日本語の概要は準備中です。原文の説明を表示しています。

[Research] Use when you need to review knowledge artifacts for completeness, citation quality, confidence accuracy, and template compliance.

日本語の概要は準備中です。原文の説明を表示しています。

[Quality] Use when you need to research and configure code quality tooling for any tech stack — linters, formatters, static analysis, pre-commit hooks, and CI gates.

日本語の概要は準備中です。原文の説明を表示しています。

Analyzes a dataset of companies or profiles to identify market patterns. Use when the user provides a larger dataset and wants segments, dominant categories, gaps, and emerging patterns.

日本語の概要は準備中です。原文の説明を表示しています。

Designs an end-to-end process for finding, extracting, enriching, qualifying, and exporting leads. Use when the user wants a repeatable lead workflow plan rather than a single source plan.

日本語の概要は準備中です。原文の説明を表示しています。

Compares a group of companies by products, positioning, market focus, and differentiators. Use when the user provides several company records and wants a structured competitive comparison.

日本語の概要は準備中です。原文の説明を表示しています。

统一 arXiv CLI 技能。通过 `arxiv <subcommand>` 完成搜索、初始化、阅读、复现、实验、部署与贡献全流程。

日本語の概要は準備中です。原文の説明を表示しています。

Use when creating Product Hunt launch carousel images for developer tools, AI tools, open-source projects, GitHub launches, or technical products. Research comparable launches, inspect the project, extract verified proof points, then generate 4-5 launch-ready images with consistent branding, product surfaces, readable copy, and source-grounded claims.

日本語の概要は準備中です。原文の説明を表示しています。

Produce an up-to-date, state-of-the-art recommendation using domain expertise and brief web research. Use only when explicitly invoked.

日本語の概要は準備中です。原文の説明を表示しています。

中文拆书与读书笔记助手。当用户要"拆书""读书笔记""这本书讲什么""帮我读这本书""做读书卡片""写书评""整理一本书的框架"时使用。重点是把书变成能用的东西，不是复述目录。

日本語の概要は準備中です。原文の説明を表示しています。

Research-grounded typography for any text-bearing surface — web, PDF, email, documents. GENERATIVE: apply correct line length, font sizing, contrast, dark mode, mobile, and Japanese rules from the start when building any UI, page, layout, or document. REVIEW: audit existing CSS/HTML/templates for typography violations. Use this skill whenever you are writing CSS that touches font-size, line-height, max-width, color, or font-family. Use it when building any frontend component, page, or layout — even if the user doesn't mention typography. Use it when reviewing any rendered output for readability. Use it when generating PDFs, emails, or any formatted document. If text will be read by a human, this skill applies.

日本語の概要は準備中です。原文の説明を表示しています。

Discover ordinary public webpages with LLM-optimized Tavily search results. Use when no specific URL is known and the user needs a quick public-web lookup, articles, recent news, sources, or domain-filtered results. This is the default Tavily leaf for simple public-web discovery. Do not use when the user already supplied the target URL (use tavily-extract), wants URLs under one known site (tavily-map), wants many pages' content (tavily-crawl), needs a full cited synthesis (tavily-research), or needs named platforms, login state, platform-native content, or cross-platform collection (Agent Reach).

日本語の概要は準備中です。原文の説明を表示しています。

Use Lingzao creator-content tools for Xiaohongshu/XHS, Douyin, and WeChat official-account public content. Lingzao supports XHS SEO, Xiaohongshu account analysis, benchmark account discovery, viral note breakdown, keyword research, one-stop content packages from keyword/link/image/inspiration material, title and cover optimization, hand-drawn route-map cards, city food maps, travel itinerary maps, life checklist maps, workflow manual maps, creator content workflow, note search, creator search, profile lookup, recent posts, deep profile copy/subtitle analysis, note/article detail, post comments, article stats, related articles, short-video copy extraction, and prompt-based creator image generation.

日本語の概要は準備中です。原文の説明を表示しています。

中国药品权威数据库查询 — NMPA(国家药监局) + CDE(药品审评中心) + DrugBank(英文名/ATC) + PubChem(化学结构) 多源融合,提供(通用名 ↔ 商品名 ↔ 英文名 ↔ 适应症 ↔ NMPA 批文号 ↔ 上市日期)精确映射。Make sure to use this skill whenever the user mentions 药品名 / 通用名 / 商品名 / NMPA / 国药准字 / 药监局 / CDE / drug brand name / generic name / drug registry / pharmaceutical lookup / drug verification / 药物核验 / 商品名对应 / drug cross-check / drug authority lookup. 在任何 medical / market-sizing / clinical / disease-research 报告生成阶段,**所有药品提及必须先调 lookup_drug() 验证**,严禁 LLM 凭训练记忆拼凑通用名↔商品名↔英文名对应关系。LLM 训练截止后药企会更换商品名、新药持续上市,记忆完全不可信。Iron Law:lookup 返回 None → 调用方必须 raise UnverifiedDrugError,不允许 fallback 到记忆。免费公开数据源,跨平台:Claude Code / Codex / Gemini CLI 三端均可 auto-trigger,实现仅依赖 httpx + beautifulsoup4 标准生态,不绑定任何厂商 SDK。

日本語の概要は準備中です。原文の説明を表示しています。

Build production-ready Tavily integrations with best practices baked in. Reference documentation for developers using coding assistants (Claude Code, Cursor, etc.) to implement web search, content extraction, crawling, and research in agentic workflows, RAG systems, or autonomous agents.

日本語の概要は準備中です。原文の説明を表示しています。

Add a new competitor to the AI Visibility Tool Directory — researches the tool, generates data, takes a screenshot, and inserts into the codebase

日本語の概要は準備中です。原文の説明を表示しています。

SOP for locating, auditing, and importing production-tested reference patterns and peer-reviewed literature. Trigger when: - Designing or implementing non-trivial algorithms, system protocols, design patterns, or major library integrations. - Prompt contains: prior art, reference implementation, research patterns, standard implementation, arXiv, RFC.

日本語の概要は準備中です。原文の説明を表示しています。

When a bug or regression is reported, the FIRST step — before fixing — is to research how and when it was introduced (git archaeology), then record that finding on the tracking issue/PR. Use the moment a bug, error, broken build, or "this used to work" is reported, before writing a fix. Produces a first-bad-commit (or "not a code regression") note you paste onto the issue.

日本語の概要は準備中です。原文の説明を表示しています。

Bounded improvement loop: one artifact, fixed eval score, keep an edit only if strictly better. Use for AR_DESIGN/AR_FUNCTION/AR_ACCEPTANCE stages or standalone bounded iteration.

日本語の概要は準備中です。原文の説明を表示しています。

Drives the Phase 4-5 dev pipeline state machine with sub-agent reviews and bounded autoresearch gates. Use when running /pipeline or executing an approved plan.

日本語の概要は準備中です。原文の説明を表示しています。

AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.

日本語の概要は準備中です。原文の説明を表示しています。