「defi」の検索結果

Für Definitionen Glossar AGB: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.

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

Build and query Kusto graphs from natural language. Covers transient graphs (make-graph), persistent graph models/snapshots, pattern matching (graph-match), shortest paths, connected components, and graph-to-table export. Generates the edges-first thinking: define edges, define node lookups, union, make-graph. WHEN: make-graph, graph-match, graph-shortest-paths, graph-to-table, graph-mark-components, persistent graph, graph model, graph snapshot, build a graph from data, find paths between nodes, pattern matching in graph, connected components, transient graph, Kusto graph, KQL graph.

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

Performance, load, and reliability (SLO/SRE) planning for production readiness. Use when defining service level objectives, load characterization, capacity, latency budgets, stress/soak/spike test plans, false-positive baselines, and reliability targets. USE FOR: SLO/SLA definition, load testing plan, performance budget, capacity planning, reliability/SRE backlog, latency targets, error-budget policy. DO NOT USE FOR: executing load tests (use Azure Load Testing tooling), security threat modeling, RAI assessment, privacy/compliance planning, or authoring/restating PRD requirements (cite the PRD's existing NFR/FR ids instead).

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

Octane bindings for TanStack DB. useLiveQuery hook with dependency arrays (8 overloads: query function, config object, pre-created collection, disabled state via returning undefined/null). useLiveSuspenseQuery for Octane Suspense with Error Boundaries (data always defined). useLiveInfiniteQuery for cursor-based pagination (pageSize, fetchNextPage, hasNextPage, isFetchingNextPage). usePacedMutations for debounced Octane state updates. Return shape: data, state, collection, status, isLoading, isReady, isError. Import from @octanejs/tanstack-db (re-exports all of @tanstack/db).

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

Define a creator's brand foundation — niche, audience, positioning, content pillars, voice/tone, and bio — so every post is consistent and on-brand. Use when asked to define a creator brand, find a niche, set content pillars, write a voice guide, craft a bio, or build a brand kit for a personal brand or channel. Produces a reusable one-page brand kit that other content skills can read so output sounds like you, every time.

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

Start a cross-team project with the collaboration contract that prevents the classic collisions — who decides what, how work flows between teams, the communication channels and cadence, and what done means — agreed before the first collision instead of during it. Use when asked kick off this cross-team project right, our two teams keep colliding, define how we'll work with the other team, or set up the partnership before we start. Produces the one-page contract: decision rights, interfaces, cadence, and the done-definition.

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

Write a CI/CD pipeline playbook for a service or team. Use when asked to document a CI/CD pipeline, write a deployment process, define release gates, document build and test stages, or create a deployment guide. Produces a structured playbook covering pipeline stages, environment definitions, deployment gates, rollback procedures, and on-call responsibilities.

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

Specify the tracing, metrics, and alerting for an AI agent or LLM feature in production. Use when asked what to log for an LLM app, design agent tracing or spans, define quality and cost monitors, or answer 'how do we know if the agent is misbehaving?'. Produces an observability spec with a trace schema, metric definitions with owners and alert thresholds, sampling and retention policy, and a privacy note for logged content.

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

Design an evaluation plan for an LLM or AI feature before shipping it. Use when asked how to evaluate a prompt/model/agent, set up an eval harness, define quality metrics for an AI feature, or build a regression gate. Produces an eval plan — task definition, datasets, metrics & rubrics, baselines, automated + human evals, a pass bar, and a regression gate.

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

Help users identify their most high-value customers by defining a hyper-specific ICP that maximizes product-market fit and acquisition efficiency.

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

INVOKE THIS SKILL when building, testing, or deploying Managed Deep Agents in LangSmith. Walks a user through their first agent end to end — interviewing them about what they want to build, mapping it onto what MDA can actually do, then scaffolding and deploying it. Covers the file-based project layout; define_deep_agent / defineDeepAgent; instructions, skills, memory, identity, tools, MCP servers, connections, middleware, sandboxes, schedules, channels, and evals; the mda CLI; GitHub deployments; and Context Hub.

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

Research competitors, analyze their messaging, and generate a positioning document with category definition, differentiation claims, value propositions, and proof points. Chains web research, competitor site analysis, and review mining to produce a positioning doc ready for website copy and sales deck use. Use when a product marketing team needs to define or refresh positioning ahead of a launch, rebrand, or competitive shift.

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

Tracks ctDNA across serial liquid-biopsy timepoints for molecular residual disease (MRD) and treatment-response monitoring, treating MRD as a binary integrated detection call across the patient's full variant set (with a defined LoD95 and per-sample specificity) rather than a per-timepoint VAF threshold, and handling undetectable samples as left-censored at the per-sample limit of detection rather than true zeros. Covers tumor-informed bespoke vs tumor-naive design, landmark vs surveillance sampling, molecular-response definitions and their non-standardization, censoring-aware clearance kinetics, and the multiple-testing structure of repeated surveillance. Use when monitoring ctDNA during therapy, calling molecular relapse before imaging, or estimating clearance half-life from serial samples.

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

Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test. Produces a complete positioning document, positioning statement, competitive alternatives map, and market category analysis. Use when the user wants to define or refine their market positioning, find their unique position, differentiate from competitors, craft a positioning statement, choose a market category, or figure out "how should we position this product." Triggers for "positioning", "how to position", "market position", "differentiation strategy", "positioning statement", "competitive positioning", "category strategy", "where do we fit in the market", "how are we different", "unique value proposition", or any request to define, sharpen, or rethink positioning. Works standalone — no prior startup-design or startup-competitors session needed, but leverages their output if available.

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

Define and generate the manual-first evidence pack for high-risk work. Covers 6 high-risk class definitions and the 5-artifact schema required before finalizing, pushing, or handing off.

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

Turn a vague task into a testable definition of done and generate an executable goal-test script for it, optionally with a bounded retry loop around a headless agent. Use when the user wants to run an agent in a loop, asks how to know when an agent task is finished, or says a goal like "improve X" needs to become checkable. Do NOT use for building eval suites over many cases — that is evals-bootstrap.

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

Set up or update a project in the vault: the four-stage folder pipeline, a project-scoped CLAUDE.md with one goal, and links to the concept pages it depends on. Use this skill when the user starts something new they will work on over time, says "create a project", "set up a folder for X", or asks to define the goal and structure of ongoing work. Do NOT use for one-off tasks, for wiki pages about a topic, or for scoping an existing project down to work in it.

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

Patterns for individual long-form content pieces. Case studies, whitepapers, research reports, definitive guides, manifestos, ebooks, long-form tutorials. The structural disciplines that distinguish publication-quality long-form from bloggy-long padding or academic bloat. Different from pillar-content-architecture (which covers hub structure); this skill covers individual deep-dive pieces. Triggers on long-form content, case study writing, whitepaper, research report, definitive guide, ebook, manifesto, long-form tutorial, deep-dive article, anchor piece, foundational article, structural archetypes. Also triggers when a piece is over 3,000 words and the team is unsure how to structure it, when a long-form draft feels padded or saggy, or when a flagship asset needs the depth to actually earn the length.

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

Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples. Use this skill whenever the user wants to define how a brand sounds, write a voice and tone document, audit existing copy for voice consistency, train a team or AI assistant on brand voice, or refine the personality of brand writing. Triggers on brand voice, voice and tone, tone of voice, writing voice, brand personality, copy voice, voice document, voice guidelines, how should we write, voice training, voice audit. Also triggers when the user has copy that 'feels off' and the underlying issue is voice, even if not stated explicitly. On a voice consistency check, this skill owns defining and documenting the voice system; use `editorial-qa` when a specific draft needs checking against an existing system before it publishes.

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

Write the code for a CopilotKit Channels agent with the Channels SDK (@copilotkit/channels) — a platform-agnostic engine that puts one AG-UI agent into Slack, Microsoft Teams, Discord, Telegram, and WhatsApp with native interactive UI. It's the engine behind OpenTag, the open-source alternative to Claude in Slack. Use this whenever the user wants to create, scaffold, or extend a Channels agent; wire an agent into Slack/Teams/Discord; add a tool, slash command, button, select, modal, or human-in-the-loop confirmation to a chat agent; or asks about createChannel, defineChannelTool, defineChannelComponent, thread.runAgent, awaitChoice, or the channels-ui JSX components. Trigger even when the user says "Slack bot", "Discord bot", or "chat agent" without naming the SDK, as long as the context is CopilotKit / Channels. The Channels API is new and easy to get wrong from memory — always ground code in this skill.

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

Track DeFi protocol metrics including TVL, yields, and liquidations

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

Product analytics for instrumenting products, defining metrics, and building retention funnels. Use when designing a metric tree, instrumenting a feature, auditing instrumentation, defining a North Star, or building an analytics roadmap.

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

Commercial policy: the governance framework defining what terms sales can offer and what triggers approval. Use when authoring a policy charter, defining discount/payment/liability rules, auditing deals, or generating a regional policy.

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

Approval cascade definition and tracking for multi-stakeholder document workflows. Internal review sequences, client approval workflows, regulatory review, overdue chasing with escalation logic, version control coordination, and cross-jurisdiction document dependencies. Use when defining who reviews a document and in what order, tracking where a document is stuck in the approval chain, chasing an overdue reviewer, preventing reviewers working on superseded drafts, or mapping dependencies between documents across jurisdictions. Trigger on: 'who needs to approve this', 'document approval', 'review sequence', 'stuck in review', 'overdue approval', 'who has the document', 'version control', 'wrong version', 'document dependency', 'NL SPA waiting on German opinion', 'approval cascade', 'review chain', 'document circulation', 'chasing the partner', 'client approval process', 'where is the document'.

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