「session」の検索結果

Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, API key permissions, webhooks, OAuth). Use when planning, building, modifying, testing, or reviewing any Stripe integration, including choosing a development environment, accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.

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

Writes turn-level tests for a LiveKit agent in the user's normal test suite: pytest (Python) or Vitest (Node.js). Use when the user asks to "write tests for my agent", "add a test for this tool", "test the handoff", "pin this bug", "why does my agent test fail", or after building or changing agent behavior that needs regression coverage. Covers the SDK's test session harness, assertions on messages, tool calls and handoffs, LLM judging of a reply against an intent, mocking tools, multi-turn tests, and judging whole conversations with the built-in judges. For interactive poking use debugging-livekit-agents. For grading whole conversations at scale use running-livekit-simulations.

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

Deploys and operates a LiveKit agent in production: shipping a version to LiveKit Cloud and rolling it back, secrets and configuration, the worker process model and prewarming, safe async inside worker processes, provider timeouts and degradation, graceful shutdown, SDK upgrades, and observability. Use when the user says "deploy my agent", "roll back the deployment", "tail the agent logs", "the first call after a restart is slow", "attached to a different loop / event loop is closed", "prewarm the VAD", "shut down without dropping calls", "upgrade livekit-agents safely", "correlate logs by session", or is changing an agent codebase that is already live. Not for designing the agent (building-livekit-agents) or reproducing one bad conversation locally (debugging-livekit-agents).

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

Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.

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

Launch and control the MATLAB Radar Designer app programmatically via MCP. Use when designing radar systems, configuring parameters, comparing radar types, analyzing performance metrics, or managing radar design sessions.

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

AI-optimized browser automation CLI with context-efficient snapshots. Use for long autonomous sessions, self-verifying workflows, video recording, and cloud browser testing (Browserbase).

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

Discover and load all relevant context for the current task. Lists feature group nested files with full paths, loads process/context/ files by domain routing. Called at the start of every agent session.

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

Generate kickoff artifacts for a multi-phase program: umbrella plan, Program Goal Charter, session-goal block, per-phase plan stubs, and the 7-step per-phase inner loop reference.

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

Use on passages a search just returned (memory, vault, session history, wiki, web) before reading them in. Jev ranks them, drops the irrelevant, and flags prompt injection hidden in the text.

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

CloudBase CLI (tcb, 云开发CLI, Tencent CloudBase命令行) resource management skill. Use when deploying cloud functions, CloudRun, storage, NoSQL/MySQL, static hosting, permissions, CORS/domains via tcb; for CI/CD and batch ops; when the user prefers CLI; or as the first-session fallback when CloudBase MCP tools are not loaded yet (after install/config, before IDE restart). Also covers tcb login and site switching (国内站/国际站 via --intl or config isIntl), environment lifecycle (env create/modify/renew/delete/apikey/login/domain), tcb config and cloudbaserc.json sync, log search (logs search, CLS), metric monitoring (monitor), data model and PostgreSQL migrations (db model, db pg migration), sandbox/agent/integration management — do not default to tcb deploy.

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

Use when the user wants to develop, run, preview, save, deploy, or roll back a CloudBase Web app in this conversation as a Lovable/Codex-Sites-like vibe- coding session — i.e. any request that maps to "spin up a React+Vite project, see it live in the browser, iterate, save versions, deploy". Activate ONLY for browser-rendered Web projects based on the CloudBase official React (or Vue) + Vite template. Do NOT activate for: WeChat/Alipay mini-program, React Native / Flutter / Electron, pure cloud functions / CloudRun backends, or Next.js / Nuxt / Astro / Remix / SvelteKit (those frameworks are explicitly out of scope).

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

Publish a redacted local coding session to an authenticated read-only Beam catalog.

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

Audit an agent's harness against the four rings: containment, guides, sensors, permissions. Use when the user asks whether their agent setup is safe, wants a review of sandboxing / permissions / hooks / AGENTS.md guardrails, or asks what a bad session could break. Read-only: reports the blast radius and a hardening list, changes nothing. Do NOT use for context layout (context-audit) or cost routing (gate-check).

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

Restore a prior business-state snapshot saved by /money-save, so you can continue from exactly where the last session left off. Loads the most recent snapshot for the current project (auto-detected from the working directory), or a specific one by index. Use when starting a new Claude Code conversation and the user wants to continue prior work. Triggered by: 'continue from last time', 'where did we leave off', 'pick up from before', 'resume', '接着上次', '续上', '之前的结论', '上次诊断到哪了'.

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

Save the current business state to disk so future Claude Code sessions can pick up where you left off. Captures confirmed conclusions, ruled-out directions, open hypotheses, and the next recommended skill. Use when the user has just reached a conclusion in /money-discover, /money-strategy, /money-diagnose, or any pipeline phase, and wants to lock the state in. Also triggered by: 'save this', 'checkpoint', 'remember this', 'lock it in', '保存', '存档', '记下来', '这个结论留着'.

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

Codify a successful workflow from the current conversation into a permanent project-local skill. After you discover (e.g.) a cold-email sequence that converts, an ad-creative format that beats baseline, or a content-pipeline cadence that compounds — /money-skillify writes it as a SKILL.md under the project's local skills directory so future sessions can re-invoke it without re-discovery. Use when the user says: 'this worked, save it', 'codify this', 'turn this into a skill', '把这个固化下来', '存成 skill'.

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

Generate a CCAM reliability report from session outcomes, hook events, alerts, tool failures, and data freshness. Use for health reviews, incident follow-up, hook-delivery audits, or reliability trend summaries.

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

Produce a scoped CCAM cost and token report by model, provider, source, and session. Use for spend reviews, model-mix analysis, unpriced usage detection, or export-friendly cost summaries.

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

Scan recent Claude Code activity for errors and failure signals across all sessions using Agent Monitor data — APIError events and PreToolUse→PostToolUse gaps (tools that started but never completed) — then group failures by tool and model and rank them by frequency. Use when checking for errors or asking "what's failing right now".

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

Launch and supervise Claude Code or Codex through the CCAM Run API. Use when the user wants to start a monitored agent, select a model, approval policy, sandbox, or working directory, send a follow-up, inspect live output, resume a native session, or stop a dashboard-launched run.

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

Inspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions. Use when finding a prior launched task, checking whether a run is still attached, reviewing start/end status, or deciding whether to resume, view, or relaunch work.

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

Summarize a sprint's worth of Claude Code activity — sessions grouped by project (cwd), per-model cost breakdown, token efficiency (cache hit rate, compaction baselines), subagent effectiveness from workflow API, velocity metrics (turn_count, turn_duration_ms), and tool diversity across the sprint.

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

Audit hook delivery health from Agent Monitor data — balance PreToolUse vs PostToolUse (a gap means tools that started but never reported back), detect missing Stop/SubagentStop terminators (sessions/subagents that never closed), and check for stale ingestion (no recent events). Use when hooks look unreliable or events seem to be dropping.

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

Define and check simple service-level objectives for Claude Code from Agent Monitor data — session completion rate, tool success rate (PostToolUse/PreToolUse), and error rate (APIError/total) — then compare each to its target and report the error budget remaining. Use when reporting reliability or when someone asks "are we meeting our SLOs?".

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