「constants」の検索結果

Identifies cryptographic algorithms embedded in a binary by scanning for well-known constants and tables (AES S-box, SHA-256/MD5 init constants, ChaCha sigma, CRC32 table, base64 alphabet). Activates for requests to identify crypto in a binary, find AES/SHA constants, or detect which encryption algorithm a sample uses.

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

有馬記念分析システムのアーキテクチャ/レイヤー境界レビュー。docs/ARCHITECTURE.md のレイヤー構成（commands / domain / repositories / models / features / constants / database / utils / types）に対し、レイヤーディレクトリの意味と配置、参照系(queries)と更新系(aggregates)の分離、DB 接続の注入可能性とテスト容易性、リッチドメインモデルの維持（commands 肥大・ドメイン貧血症）、重み・閾値の constants 単一定義、ファイル配置と命名語彙の一致、不要な抽象化、種別分岐のポリモーフィズム化、生成引数の凝集（5個以上は分割シグナル）を検証。純粋性・依存方向の逆流・DB 接続の生成箇所は lint が error で担保するため扱わない。Use when user says 'アーキテクチャレビュー', 'レイヤー境界チェック', 'review architecture', or '依存方向の確認'.

Create or update a constants file in the Constants folder in Sources of a spark-ios-component-XXX and add or update unit tests.

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

Query physics databases — NIST CODATA constants, NIST Chemistry WebBook, Materials Project, Particle Data Group (PDG), OEIS sequences. Always use these instead of hardcoding physical constants.

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

Contributing to the Twenty codebase itself (twentyhq/twenty server internals), not for building apps on top of Twenty. Define types, entities, and central constant registrations for syncable entities in Twenty's workspace migration system. Use when creating new syncable entities, defining TypeORM entities, flat entity types, or registering in central constants (ALL_ENTITY_PROPERTIES_CONFIGURATION_BY_METADATA_NAME, ALL_ONE_TO_MANY_METADATA_RELATIONS, ALL_MANY_TO_ONE_METADATA_FOREIGN_KEY, ALL_MANY_TO_ONE_METADATA_RELATIONS).

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

Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.

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

Defining and extracting kernel constants for syzkaller syzlang descriptions

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

Add a new deterministic scoring check in src/scoring/checks/ that evaluates config quality. Follows the Check[] return pattern, uses point constants from src/scoring/constants.ts, and integrates via filterChecksForTarget() in src/scoring/index.ts. Use when user says 'add scoring check', 'new check', 'modify scoring criteria', or works in src/scoring/checks/. Do NOT use for display changes or refactoring scoring logic.

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

Fix silent failures in Fastly Compute@Edge when using send_async for fire-and-forget requests. Use when: (1) Background tasks (migrations, webhooks, notifications) triggered from Compute never complete, (2) send_async PendingRequest is immediately dropped, (3) Fire-and-forget pattern works locally but fails in production, (4) An async trigger "logs as triggered" but the target service never receives the request (especially after renaming backend constants — the URL hostname is cosmetic, the backend name determines routing, so a global rename can silently reroute calls to the wrong service). Also covers silent backend-not-found errors when FALLBACK_BACKENDS or other backend constants reference names not configured in the Fastly dashboard.

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

Returns the frozen gate constants — question, header, option labels and descriptions, digest field-list, and preview content — for every catalog gate. Invoked by the team lead fresh on arrival at each gate and on pulse re-emissions, in the same turn as the render. The transport contract, three renders, partition rule, and authoring rubric live in swarm:workflow-rules.

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

有馬記念分析システム（Bun + TypeScript CLI）のコード品質・コードスタイルレビュー。機械検証の通過（bun run c / bun run lint / bun test）、非推奨 API の使用、死にコード・消し残し、マジックナンバーと固定語彙の constants 集約、コメントの why 品質（足し算側）、既定値・フォールバックの規律、非同期とエラーハンドリング（握り潰し catch・await 漏れ）、関数構成とファイル構成（メイン関数先頭・400行）、制御フロー（条件連鎖・ガード節の羅列）、コレクション操作（reduce・entries・長チェーン）、否定条件 + else、オーケストレーションの平坦化、型安全（any・as）、import の一貫性、CLI 出力（console）の置き場所を検証。Use when user says 'コードレビュー', 'review code', '規約チェック', 'スタイルチェック', or '死にコード確認'.

Tracks physical units and propagates measurement uncertainty in scientific calculations using pint and uncertainties. Use for unit conversion and dimensional checking, GUM uncertainty budgets, Type A and Type B evaluation, coverage factors and expanded uncertainty, Monte Carlo propagation, significant-figure and plus-minus reporting, error propagation through curve fits, CODATA constants, auditing Python code for stripped units or broken uncertainty propagation, and order-of-magnitude plausibility checks using dimensionless groups (Reynolds, Peclet, Damkohler, Knudsen, Biot, Womersley), characteristic scales such as diffusion time or Debye length, and observed magnitude ranges. Trigger on "is this number physically reasonable", "sanity check these units", "what regime is this flow in", or a result that looks off by orders of magnitude.

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

Scaffold the co-located feature structure in frontend/src. Use when creating a new page, feature, view (tab), or component folder, when a feature needs a shell with tabs, or when moving existing code out of src/container into src/pages. Generates the full folder tree (components/hooks/store/types/utils/constants/__tests__/README) and registers the page's routes with one command.

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

Use when adding user-facing text to Handsontable, creating new language constants, updating translation files, or working with RTL layouts and internationalization

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

Client-side request-signing and anti-bot token reversal for bug bounty — when a request carries a sign/sig/hmac/token/nonce/timestamp/X-Sensor header that Burp Repeater cannot replay, recover the signer just enough to reproduce the request outside the client. Packet-first staging (capture real request → prove replay works → only reverse if replay fails) across the locate→recover→runtime→validation→replay spine. Covers tracing backward from the signature field (writer→builder→entry→source), isolating user-mutable sign inputs (timestamp/nonce/deviceId/body) vs constants (secret key), hooking fetch/XHR in DevTools, JS deobfuscation basics (webpack/wasm/JSVMP), and the bounty payoff: reach the protected API to then hunt IDOR/auth/business-logic. Use when Burp/mitmproxy replay of a signed or anti-bot-gated request fails and you suspect a client-computed field is blocking you.

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

Design account-aware Alchemy throttling, bounded retries, and admission control from observed throughput rather than stale plan constants. Use when preventing or handling rate limits. Trigger with "Alchemy rate limit", "Alchemy throughput", or "fix Alchemy 429s".

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

Restore function symbols by analyzing code patterns, strings, constants, and cross-references

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

Generate correct MATLAB code using the Symbolic Math Toolbox. Use when the user asks for symbolic computations, analytical solutions, symbolic differentiation/integration, equation solving, or converting symbolic results to numeric MATLAB functions. Also use when converting differential equations to transfer functions or state-space form, extracting PDE coefficients (pdeCoefficients), symbolic-to-C code generation (matlabFunction + codegen), symbolic matrix variables (symmatrix), physical units and constants (symunit, newUnit), or rewriting/combining algebraic expressions (rewrite, combine).

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

Main app analytics tracking patterns (AnalyticsEvent enum, AnalyticsTrackerWrapper, KEY_*/VALUE_* constants). Use when writing, editing, exploring, debugging, or reviewing analytics tracking in the store management app. NOT for POS (WooPos*) code — use the `pos-analytics` skill instead.

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

Think and work like an expert Mathematical Analyst. Use when a task calls for Mathematical Analyst judgment. Reasons from function-space topology, convergence modes, and constant-dependent inequalities (Hölder, Sobolev, Gronwall) through compactness theorems (Rellich-Kondrachov, Banach-Alaoglu), Calderon-Zygmund and Schauder estimates, and Lax-Milgram while treating limit-integral swaps without dominated convergence, boundary-degenerating constants, weak-versus-classical regularity gaps, and concentration-compactness loss as first-class failure modes.

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

Think and work like an expert Enzymologist. Use when a task calls for Enzymologist judgment. Reasons from catalytic mechanism, kcat/Km, elementary rate constants, and active-site [E]t through Michaelis-Menten and global fitting in KinTek Explorer, stopped-flow/quench-flow, SPR/BLI/ITC, and STRENDA/EnzymeML reporting while treating substrate inhibition, morpheein equilibria, coupled-assay artifacts, and colloidal-aggregator inhibitor hits as first-class failure modes.

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

Prepare a meeting-ready estate and tax brief for a household — opens with what was discussed and actioned since the last meeting (Wealthbox/Redtail/Salesforce), pulls the estate plan from Wealth.com (structure, key documents and whether each is signed, balance sheet) plus the prior-year tax look-back and that year's tax constants, and cross-checks it against how accounts are titled and beneficiaried at the custodian and portfolio platforms (Schwab, Orion/Addepar, iCapital) — surfacing unfunded trusts, titling mismatches, and beneficiary gaps as a prioritized flags list. The only write is creating advisor-approved follow-up tasks in the CRM (optional, approved first). Never drafts trust language, gives legal advice, retitles an account, or changes a beneficiary. Triggers on "estate brief", "estate meeting brief", "estate and tax brief", "estate plan review for [client]", "check [client]'s trust funding", "are [client]'s beneficiaries up to date", or "does [client]'s estate plan match their accounts".

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

Use when preparing a PlainTab release or bumping the PlainTab version, triggered by phrases like "更新版本", "bump version", "upgrade to vX.Y.Z", "发布新版本". Updates manifest.json, runtime UI/version constants, localized changelogs, store listings, release notes, validation notes, and current project docs.

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

Refactoring code: variable naming, function extraction, magic number constants, dead code removal. Does not change behavior. Not for bugs/security (Judge), tests (Radar), or features (Builder).

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