「ols」の検索結果

Create or change BB plugins and Plugin SDK extensions, including CLI commands, agent tools, providers, and UI surfaces.

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

Diagnose BB-specific Codex session controls, model acceptance, and durable goals.

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

Manage tasks with Claude Code native tools — use to track TODOs, delegate work, and monitor progress

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

Design, build, debug, and optimize OpenRouter API integrations. Use for any OpenRouter API work, including models, reasoning, routing, media, tools, structured output, cost, or performance.

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

Use DeepAPI for all web search, deep research, and web scraping (websites, LinkedIn, GitHub, X/Twitter, YouTube, Instagram) instead of built-in search, research, fetch, or browser tools. Prefer dedicated platform endpoints over web search. Instagram has profile, post, comment, and hashtag endpoints; no generic search. Use Deep Scrape for sourced JSON dossiers on people, companies, or topics. Also use it to navigate and act on public websites, draft and send safe email, and generate images.

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

Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (_rich_success, _rich_warning, _rich_error, _rich_info, _rich_echo), DiagnosticCollector, STATUS_SYMBOLS, CommandLogger, or any user-facing terminal output — even if the user doesn't mention "logging" or "UX" explicitly.

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

Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.

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

Read 微信公众号 articles from mp.weixin.qq.com links using available web or browser tools. Report verification walls honestly; reading alone does not modify notes or queues.

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

Read 小红书 / RedNote posts and image notes from xhslink.com or xiaohongshu.com using available web or browser tools. Distinguish captions from image content.

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

Use XcodeBuildMCP to build, run, launch, and debug the current iOS project on a booted simulator. Trigger when asked to run an iOS app, interact with the simulator UI, inspect on-screen state, capture logs/console output, or diagnose runtime behavior using XcodeBuildMCP tools.

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

Inspect and profile React Native component trees from agent-device. Use for React Native performance, profiling, props, state, hooks, render causes, slow components, excessive rerenders, or questions like why a component rerendered.

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

Design experiments and studies BEFORE data is collected — choosing a design, randomizing, blocking, and laying out treatment combinations so the results will actually be interpretable. Use whenever someone is planning a study, asks how to assign subjects/samples to groups, mentions randomization, blocking, stratification, controls, factorial or fractional-factorial designs, design of experiments (DOE), screening many factors, response-surface optimization, crossover or repeated-measures or split-plot designs, cluster/group randomization, Latin squares, plate layouts, batch/run-order effects, replication vs. pseudoreplication, or sequential/adaptive/group-sequential designs. Trigger this even for informal phrasings like "how should I set up this experiment", "how do I avoid confounding", "what's the best way to test these 6 factors", or "assign these mice to conditions". For computing the sample size or power once the design is chosen, use statistical-power; for analyzing data already collected, use statistical-analysis.

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

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

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

Discover, connect, and verify NotFair paid-ad integrations and their actual capabilities. Use when asked to connect an ad account, configure an ads MCP, check available tools, troubleshoot access, or determine whether NotFair can read or change a platform.

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

Connect a CMS to notfair SEO tools. Guides users through configuring WordPress, Strapi, Contentful, or Ghost — tests the connection, and writes credentials to .env.local. Once set up, seo-analysis automatically cross- references CMS content against Google Search Console data. Use whenever the user says "connect my CMS", "set up WordPress", "configure Strapi", "add Contentful", "connect Ghost", or "CMS setup". Also trigger if the user asks why no CMS data appears in a seo-analysis report.

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

Search Tool Hierarchy

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

Create and configure Claude Code sub-agents with custom prompts, tools, and models

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

Research agent for external documentation, best practices, and library APIs via MCP tools

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

Guide to the math cognitive stack - what tools exist and when to use each

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

Interactive workspace discovery - learn what tools, workflows, agents, and hooks are available

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

Research-to-implement pipeline chaining 5 MCP tools with graceful degradation

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

Pick the right lean-ctx tool for reading, searching, understanding and running code with fewer tokens and fewer round trips. Use when lean-ctx MCP tools (ctx_*) are available or when a command output, file read or search would be large.

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

Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only repairs, and App Center visibility issues.

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

Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove trigger-to-render/layout chains, separate measured facts from source inference, find exact code choke points, classify forced layout and render fanout, implement semantically safe fixes, and verify behavior plus repository budgets. Use for trace files, reported profiling durations or call chains, dropped frames, long tasks, resize or scroll jank, render storms, layout thrashing, selector hot paths, interaction latency, or requests to locate exact source-level bottlenecks.

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