「functions」の検索結果

Reverse engineers binaries with Binary Ninja using its analysis stack and Python API to enumerate functions, navigate IL levels (LLIL/MLIL/HLIL), and automate annotation and extraction. Activates for requests to reverse a binary with Binary Ninja, script the Binary Ninja API, or work with its intermediate languages.

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

Automates radare2/rizin analysis through r2pipe to script function enumeration, string and import extraction, and cross-reference queries across samples programmatically. Activates for requests to automate radare2 with r2pipe, script rizin analysis, or batch-extract functions and xrefs from binaries.

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

Reviews audio DSP and audio processing code for realtime safety violations. Use whenever the user asks to review, audit, or check audio processing code — including plugin process callbacks, audio engine render functions, DSP implementations, or any code that runs on the audio thread. Trigger on phrases like "review my processBlock", "check this DSP code", "is this safe for the audio thread?", "review my JUCE plugin", or when you see an audio callback and spot potential realtime violations. Flag issues proactively even when the user hasn't explicitly asked for a review.

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

Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.

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

保持行为的前端重构主要涉及函数类重构，已经选定或正在评估对应手法，需要查询该 family 的操作步骤、风险与 JavaScript/TypeScript/React/Vue 适配时。

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

Use when behavior-preserving frontend refactoring focuses on function structure, naming, parameters, shared context, or phase boundaries, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.

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

Bump the manifold3d pin, add FFI + safe wrappers for new upstream C API functions, bump versions, open a PR

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

Use when a task needs the judgment of an Electromechanical Equipment Assembler — verifying shaft/coupling alignment directly rather than trusting an initial functional test that only confirms the device runs, applying fastener torque to spec with a calibrated tool rather than by feel, routing wire to account for the equipment's full range of motion rather than its static assembled position, or distinguishing electrical from mechanical root cause when a device malfunctions.

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

Manage Volcengine's AI-native BaaS platform (Supabase edition / AIDAP / 火山引擎 AI 原生 BaaS 平台 Supabase 版) — a Volcengine-operated distribution that differs from official Supabase. Use when the user asks to create, inspect, or manage Volcengine Supabase or AIDAP resources — workspaces, branches, computes, SQL queries, schema changes, Auth, Realtime, Edge Functions, Storage buckets, frontend static-site hosting (Pages), API keys, connection info, or TypeScript type generation — or when a Volcengine deployment selects AIDAP as its database provider. Also trigger on Chinese prompts mentioning "火山引擎 Supabase" or "火山 Supabase". Operations run through the byted-supabase-cli command-line tool (installed via `npm i -g @byted-supabase/cli`; this is NOT the official `supabase` CLI). Do NOT use it for general database discussions, non-Supabase services (RDS MySQL, Redis), or pure client-side coding unrelated to Supabase backend management.

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

Deploy and manage serverless applications on Volcengine veFaaS. Use when the user wants to deploy web apps, manage functions (pull code, upload and deploy), configure environment variables, inspect veFaaS projects, troubleshoot vefaas CLI/auth/framework issues, or work with veFaaS services.

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

Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.

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

Write readable, maintainable code: naming, small functions, clear control flow, and honest abstractions. Use when writing new code, refactoring, or reviewing for readability.

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

Performs static analysis of binary code using radare2 and Ghidra — function enumeration, cross-reference tracing, decompilation, and control flow graphs without executing the binary. Use when disassembling or decompiling code, mapping functions, tracing data flow, or building hypotheses before dynamic verification.

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

Configure a CDN with optimized caching, SSL/TLS, security headers, and cache invalidation — auto-detects hosting provider and app type, generates CloudFront, Cloudflare, or Vercel config with per-content-type cache rules, edge functions, and compression. Use when deploying a static site, SPA, SSR app, or adding a CDN layer to an existing API.

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

Scope a milestone to a fixed time window with variable scope. Use when the user says "scope this milestone", "what fits in the sprint", "cut scope for the release", "define the MVP for this milestone", "we need to ship by [date] what do we cut", "shape the work to fit the cycle", or needs to make hard scope decisions under a time constraint - even if they don't explicitly say "milestone scoping". Based on "Shape Up" by Ryan Singer (appetite, shaping, betting table) and "The Art of Project Management" by Scott Berkun (milestones as forcing functions, scope as a variable).

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

Navigate a new leadership role using Michael Watkins' First 90 Days 30/60/90 framework. Use when someone says "I just started a new role", "I'm starting as a new manager", "I joined a new company as a leader", "I was just promoted", "how do I onboard as a leader", "what should I do in my first 30 days", "I inherited a team", "I need a 90 day plan", or "I'm new to this team". Also trigger when someone describes feeling overwhelmed in a new leadership role, unsure where to start, or tempted to make changes too quickly before they've listened. Applies to first-time managers, leaders joining new companies, and leaders moving into new functions or teams within the same company.

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

Assess team health using Patrick Lencioni's Five Dysfunctions of a Team model. Use when a leader says "my team feels off", "we have trust issues", "people aren't speaking up in meetings", "accountability is a problem", "we keep missing commitments", "the team is siloed", "we're not working well together", or "I want to do a team health check". Also trigger when someone describes symptoms like passive agreement in meetings, blame culture, missed deadlines without escalation, or people optimizing for their own metrics over team goals.

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

FALLBACK ONLY — do not invoke unless you have already ruled out (1) a native API (Gmail API, GitHub API, Slack API …), (2) a CLI (git, gh, aws, npm, curl …), (3) direct file editing, and (4) existing browser automation (Playwright, Puppeteer). Only when all four are unavailable or have already failed should you use this skill. It gives AI agents a cursor and a keyboard on a real desktop — the last mile when the only remaining surface is a GUI. Concretely: use it when an earlier attempt via API, CLI, or direct file edit has failed and the user says things like "open X", "click Send", "type this in Word", "read what is on my screen", "do this in Outlook", "drive the Figma UI", "control my desktop", "automate this workflow", "fill out this form", or "copy text between apps". Works on Windows, macOS, and Linux with any LLM that can call functions (Claude, GPT, Gemini, Llama, Kimi, Ollama) over MCP — stdio for editor hosts (Claude Code, Cursor, Windsurf, Zed) or HTTP for daemons and dashboards.

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

Use this skill when writing, debugging, or optimizing SAQL queries in CRM Analytics — covering pipeline syntax, aggregation, windowing functions (rank, dense_rank, moving_average), cogroup joins, rollup subtotals, piggyback queries, and REST API execution. NOT for SOQL GROUP BY aggregates in Apex — use apex/apex-aggregate-queries. NOT for dashboard JSON steps and bindings — use admin/analytics-dashboard-json.

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

Compound fields (Name, Address, Geolocation): SOQL access rules, DML semantics, component access in Apex/LWC, reporting column behavior, formula field restrictions. NOT for creating a new custom field — use admin/custom-field-creation. NOT for formula syntax and functions — use admin/formula-fields. Trigger keywords: BillingAddress, MailingAddress, ShippingAddress, StateCode, CountryCode, GeocodeAccuracy, Location field type, displayLocationInDecimal, __Latitude__s, __Longitude__s, DISTANCE, GEOLOCATION, Custom Address Fields, AddressSettings, System.Address, System.Location, Person Account name.

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

Expert in complex functions, contour integration, residue theory, and conformal mappings

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

Use the Skmtc CLI to scaffold projects, install or clone generators from JSR, configure schema sources and enrichments, and produce code artifacts from an OpenAPI v3 or GraphQL SDL schema. Teaches the workspace mental model (`<root>/.skmtc/<project>/`, client.json, bundle, manifest) and the agent contract (strict text / strict JSON modes, exit codes, recipe errors, `agent-context` + `doctor`); the command surface itself is discovered from the binary — `skmtc --help`, `skmtc <cmd> -h` — rather than carried in this skill. Use this skill when the user asks to "run skmtc", "generate code from an OpenAPI schema", "install a skmtc generator", "scaffold a skmtc project", "watch a skmtc project", "configure enrichments", "publish a stack", "deploy to skmtc-hub" (the command is `publish`; there is no `deploy`), "skmtc in CI", or invokes any CLI subcommand. For *authoring* a generator package (Projections, Snippets, transform functions), defer to `skmtc-generator`. When something is broken (no output, wrong output, error messages, a failed bundle build), verify before proposing a fix: read the manifest and the parse issues, and reproduce the failure first.

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

Ward the codebase — an ad-hoc test-gap audit that reveals unguarded code (untested functions, uncovered edge cases, missing error-handling and integration tests) and conjures ready-to-paste test skeletons as protective wards against regression, surfaced inline in the session. Scoped to your current diff by default, or to a path/area you name. Use before merging risky changes or when you suspect thin coverage. Replaces the old always-on `testgaps` daemon worker (alias: /test-gaps).

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

Run before starting an implementation task — scout + gather assemble relevant files, functions, tests, and notes into a brief.

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