「threshold」の検索結果

Price and volume tracker for [REPLACE: TOKEN_SYMBOL] with anomaly alerts above [REPLACE: ALERT_THRESHOLD_PCT]% movement

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

Step 5 of the PaperOrchestra pipeline (arXiv:2604.05018). Iteratively refine drafts/paper.tex by simulating peer review and applying targeted revisions, with strict accept/revert halt rules, deterministic 0-100 decision bands (Accept/Minor/Major/Reject) that drive a target-met early stop, and a Devil's Advocate concession-threshold guard that blocks acceptance on unresolved critical findings. Maintains a worklog and snapshots each iteration so revert is real, not symbolic. TRIGGER when the orchestrator delegates Step 5 or when the user asks to "refine the draft", "iterate on the paper", or "run peer review on this paper".

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

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

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

Type-specific validation checklists, six quality characteristics, and quality gate thresholds for documentation assessment

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

Use when the user needs to work backward from a revenue goal to the numbers that produce it — required leads, max CPA and CPL, funnel conversion thresholds, and the budget that has to be spent, with three scenarios and currency handling for US, EU, SEA, and LATAM. Trigger on 'reverse KPI', 'how much budget do I need', 'what CPA can I afford', 'work backward from revenue', 'how many leads to hit target', 'break-even ROAS'. Also use when the user names a revenue target and asks whether it is realistic. Not for — splitting an existing budget across channels and months, see `61-budget-planning-global`; a full paid media plan, see `54-media-plan-global`; the period plan, see `00-marketing-plan-global`.

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

Weekdays. Checks every project in the inventory from the outside, records one dated observation per project, then reads the production log surfaces since its own cursor and groups every error into a fingerprint so a hundred sightings are one incident. It appends the health ledgers, writes the health digest, and cards the incidents that clear the threshold. It changes nothing, deploys nothing, and never rotates a key.

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

Weekly on a Wednesday, light browser lane. Turns the questions that keep coming back into the answer that only has to be written once. It reads the ticket ledger over the recurrence window, finds every theme that crossed its threshold, checks the member's own help center and the existing macros for an answer that already covers it, and writes a reusable macro and a help article draft for every theme that has neither. It publishes only where you released the channel an article, never edits a live help center page, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

Weekly, browser only when a source refuses to be fetched. Counts unpublished calendar entries per property by folding the published ledger against the calendar, and where every property is above its runway threshold it records the counts and exits, which is the normal run. Where a property is low it researches the next block from rank evidence, the topic map, and live result sets, refuses any keyword already targeted, and appends fully specified entries after the last existing block. It is the only writer of the calendar and it never modifies, reorders, or renumbers an existing entry.

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

Phase 2 of the prd-taskmaster pipeline: spec generation and task parsing. Loads a template (comprehensive|minimal), fills it with DISCOVER-phase constraints and answers, validates the spec (placeholders_found, grade thresholds), parses the PRD into tasks via task-master, runs TaskMaster's native complexity analysis, and expands every task into verifiable subtasks. Autonomous-safe. Declares GENERATE complete so HANDOFF can follow.

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

Captures, masks, compares, and updates screenshot baselines for web and mobile suites, with per-region thresholds and a reviewed-diff rule for every baseline change. Use when a screenshot assertion fails, a baseline needs updating, or visual checks are being added; not for deciding what to verify.

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

Define the delivery metrics contract for agent-assisted SDLC — DORA four plus per-stage indicators derived from artifact and git history, and the control bands that turn metric drift into a routed intake. Use when reporting cycle time, plan adherence, or defining response thresholds.

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

Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.

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

Iterative skill tuning via execute-evaluate-improve feedback loop. Uses maestro delegate Claude to execute skill, Agy to evaluate quality, and Agent to apply improvements. Iterates until quality threshold or max iterations. Triggers on "skill iter tune", "iterative skill tuning", "tune skill".

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

单字段多条件阈值检验工具。读取被检验表和阈值表，将指定字段的属性项值与阈值表中定义的多条件门限进行比对， 检查是否在门限范围内，不允许超出门限值（包括上限和下限）。不满足条件的数据会标记质控标识并输出异常数据。 当用户提到单字段阈值检验、多条件阈值检验、单字段多条件检查等需求时使用此skill。 即使用户没有说出"单字段多条件"，只要任务涉及根据多个条件进行单字段阈值校验，就应该使用此skill。

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

批量阈值检验工具。读取被检验表和阈值表，将数据列的值与阈值表中定义的上下限进行比对， 识别并标记超出允许范围（包括上限和下限）或为空值的数据点，最后输出为相同格式的文件。 当用户提到批量阈值检验、阈值表校验、多字段阈值检查、范围校验等需求时使用此skill。 即使用户没有明确说出"批量阈值"，只要任务涉及根据阈值表进行多字段范围校验，就应该使用此skill。

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

数值数据阈值检验工具。读取结构化数据文件（CSV、TSV、Excel等），检查数值字段是否在指定的门限范围内，不允许超出门限值之外，最后输出为同格式的文件。当用户需要对数据进行阈值检验、数值范围检查、数据质量控制等操作时使用此skill。

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

批量阈值检验-输入框工具。读取被检验表，将数据列的值与输入阈值条件中定义的上下限进行比对， 识别并标记超出允许范围（包括上限和下限）或为空值的数据点，最后输出为相同格式的文件。 当用户提到批量阈值检验、输入框阈值检验、多字段阈值检查、范围校验等需求时使用此skill。 即使用户没有明确说出"批量阈值输入框"，只要任务涉及根据输入的阈值条件进行批量范围校验，就应该使用此skill。

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

50+ named UX rules with numeric thresholds, 30+ UI styles catalog, industry anti-patterns, pre-delivery checklist

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

Load testing with k6/Artillery, response time thresholds, memory leak detection, N+1 query detection, and CI integration.

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

k6 script templates, load profiles, response time thresholds, SLO validation, and performance testing strategies.

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

Add, repair, or review Playwright visual regression tests for browser-facing .NET apps, including screenshot baselines, Pixelmatch thresholds, deterministic rendering, and GitHub Actions artifacts. USE FOR: toHaveScreenshot, page.screenshot visual checks, Pixelmatch/pngjs comparison scripts, visual baseline updates, screenshot diff triage, or CI workflows for UI regression screenshots. DO NOT USE FOR: pure unit tests, accessibility audits, browser-debugging sessions, or frontend linting.

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

Routes heterogeneous queries to the appropriate index, tool, or answering engine before retrieval. Use when one endpoint serves multiple handlers, such as summary, vector retrieval, text-to-SQL, or tools, and query types require different paths. Covers LLM, semantic, and rule-based routers, confidence thresholds, fallbacks, and framework mappings. Do not use when one handler serves all queries or branching is fixed.

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

Build a held-out eval set, run it on every prompt/model change, and block regressions in CI. An LM change is a code change — gate it with a test suite (eval set + metric + threshold). Cross-framework SOP not surfaced by any single base skill.

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

Turns a product or startup idea into a ranked list of riskiest assumptions, the cheapest test for each, pass/kill thresholds, and a go/pivot/kill readout, before anyone builds. Use when someone says "validate my idea", "is this worth building", "what's the riskiest assumption", "design an MVP", "fake door", "smoke test", "will people pay", "pre-sell", "customer discovery plan" or "should we build this". Draws on 82 Lenny's Podcast guests incl. Mike Maples Jr., Eric Ries and Jake Knapp.

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