「state」の検索結果

Expert knowledge for Azure Advisor development including best practices, decision making, limits & quotas, security, configuration, and integrations & coding patterns. Use when configuring Advisor alerts/digests, managing rec states, using workbooks, Resource Graph, or RBAC for access, and other Azure Advisor related development tasks. Not for Cost Management (use azure-cost-management), Azure Monitor (use azure-monitor), Azure Policy (use azure-policy), Azure Security (use azure-security).

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

Account suspension prevention and appeal — policy violations, Plan of Action writing, reinstatement process

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

Autonomous cold email campaign launcher. Takes one target company domain, scrapes their website, generates an ICP with Claude, pulls matching leads via Prospeo, enriches emails + company descriptions, personalizes each lead with parallel Claude Code Task sub-agents (A/B/C variants), and uploads as a live Smartlead campaign. Uses local JSON files for state (no database required). Use for automated daily campaign launches after you have an initial `client-profile.yaml` from /icp-onboarding. Triggers on "auto-research", "launch an automated campaign", "daily campaign", "run the research loop".

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

Judge how a memory changes active-task state and whether it refers to an existing task. Use for mem-claw task-lifecycle model calls.

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

Judge whether one stored row states a retired profile position as current.

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

Read one conversation window and return every independently mutable claim it states, one record each, with who or what it is about, whether it happened or stands, and the words that carry its time. Used by the memory extraction model on every conversation window; the engine resolves dates, validates keys, and repairs format.

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

Judge which offered rows one nominated statement retires or replaces.

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

Build a brand's messaging hierarchy — taglines, value propositions, key messages, and proof points for each audience. Use when the user says "brand messaging", "messaging framework", "value proposition", "tagline", "brand tagline", "key messages", "messaging hierarchy", "what should we say about our brand", "brand copy foundation", "messaging architecture", "elevator pitch", "one-liner", "brand statement", or needs consistent language across all communications. Also use when messaging feels inconsistent across channels or teams.

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

Define and sharpen a brand's market positioning — where it sits relative to competitors, what it owns, and how it differentiates. Use when the user says "brand positioning", "positioning statement", "where do we sit in the market", "how are we different", "differentiation strategy", "positioning map", "competitive positioning", "what space do we own", "brand territory", "we're too similar to competitors", "help me position this brand", or wants to find a defensible place in a crowded category.

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

Craft a brand's origin story, founder narrative, and "why we exist" statement. Use when the user says "brand story", "origin story", "founder story", "why we exist", "about us", "our story", "company narrative", "brand narrative", "write our about page", "tell our story", "founding story", "brand history", or wants to articulate the deeper purpose and human story behind the brand. Also use when the About Us page feels generic or corporate and needs a rewrite.

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

Run the fixed 6-step session-opening sequence — pwd, read progress, git log, count remaining features, init.sh, smoke-test last feature — before touching any new work. The orientation ritual that lets fresh-context sessions reconstruct project state in under a minute.

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

Compare two schema states and surface the risky changes. Use before applying migrations or after a model change.

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

Seedance 2.5 prompt director — the omni-reference dialect. Routes the four generation modes (t2v / omni_reference / video_edit / video_extension), writes explicit @Image/@Video/@Audio reference roles with exclusions, stages 30-second videos into end-state beats, and covers video editing, forward/backward extension, first-last-frame and multi-keyframe control, storyboard grids, blockout rendering, and seamless transitions. Use whenever the user asks for a Seedance 2.5 prompt, mentions Seedance 2.5 / Dreamina / Jimeng, wants a clip longer than 15s on Seedance, wants to EDIT or EXTEND an existing video rather than generate a new one, or supplies more than a handful of image/video/audio references. For Seedance 2.0 (4K, `mode=fast`, or a genre hint) use higgsfield-seedance instead.

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

embeddedskills 的薄编排层，用于在当前 workspace 中发现工程、选择 build/flash/debug/observe 后端、串联 .embeddedskills/state.json，并聚合底层 skill 的结果。 当用户明确输入以下命令之一："一键构建烧录"、"自动诊断"、"串起 build -> flash -> debug -> observe" 或显式调用 /workflow 时触发。

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

TypeSafe AI（typesafe.ai）官方文档离线 Wiki，覆盖 Jev System One 模型、Choice/Score/Noul 问题原语、state 结构与置信度、架构 Patterns、Python/JavaScript SDK、HTTP API 参考与 Cookbooks 示例；用于查询 TypeSafe API/SDK 的接入、用法与示例。不用于其他 LLM 厂商 API、千问或百炼系列文档问题。

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

Guides React component implementation, performance optimization, and state management thresholds. Triggered when handling components, pages, or UI logic.

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

Reverse JavaScript-based custom DSL/VM interpreters, non-standard WASM-like runtimes, and risk-control engines. Use when analyzing IIFE or switch-based opcode dispatchers, extracting instruction tables, recovering bytecode semantics, capturing VM state at runtime, or reconstructing execution flow.

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

Mandatory entry point: read this first for any request to make, create, edit, animate, or render a video, animation, or motion graphic, including a promo, explainer, captioned clip, title card, overlay, slideshow or interactive deck, Remotion port, or any HyperFrames HTML composition. Also use it to inspect, diagnose, validate, preview, publish, or batch-render an existing HyperFrames project. Inputs may be a website URL, GitHub PR, Figma design or URL, text or brief, existing footage, or music. It resumes project state, captures intent when applicable, selects and installs the owning workflow, and routes domain capabilities. HyperFrames is the default output framework unless the user explicitly chooses another framework for the deliverable or asks only to record a browser session.

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

Use when the user says m0 handoff, before I compact, end of session, save session state, resume where we left off, or continue in Cursor or Claude Code. Writes or reads a compact_checkpoint so a cold start becomes a continuation.

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

Use when you resume work and the last session ended mid-phase, a .continue-here checkpoint exists, or a PLAN has no SUMMARY. Restores STATE.md context, shows status, and routes to the next command.

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

Import Figma content into a HyperFrames composition — rendered assets, brand tokens, components, storyboard sections → reconstructed motion (frames read as states, not slides) (REST/CLI), connector-assisted motion when available, and shaders from a connector or native export. Use when the user pastes a figma.com link or asks to bring a Figma design, frame, logo, brand, or animation into a video/composition.

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

Use when the user asks to add a phase, feature, or scope to the end of the current milestone roadmap. Adds the next sequential phase directory, updates ROADMAP.md, and tracks the change in STATE.md.

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

Use when a GSD run failed, stalled, or produced the wrong result and the cause is unclear. Reads git history and .planning/ state and phase artifacts to diagnose root cause, then writes a report to .planning/forensics/.

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

Use when a bug, failing test, or unexpected behaviour needs investigation, especially across sessions or context resets. Isolates it in a debugger subagent with persistent .planning/debug state, unlike skills/systematic-debugging.

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