2.4万 件 ・ 関連度順
概要と使いどころ
Audio Unit v3 (AUAudioUnit) format adapter for Pulp — render-block wiring, parameter tree bridging, MIDI / sysex via AURenderEvent, sidechain pulls, state persistence, iOS extension surface, and the pitfalls discovered while wiring the adapter.
日本語の概要は準備中です。原文の説明を表示しています。
Ask Daniel a blocking decision as options with a recommendation and honest pros/cons, rather than prose. Use whenever work is blocked on a judgment call, a product decision, an approval, or a choice between approaches — instead of writing "let me know which you prefer" at the end of a message.
日本語の概要は準備中です。原文の説明を表示しています。
Debug or validate Pulp animations / transitions / scroll behavior using in-process motion fixtures and offline visual analysis. TRIGGER on phrases like "animation is wrong", "transition timing off", "fade too late", "card slides too far", "scroll jumps on restore", "scroll offset wrong on restore", "frame jump in the timeline", "easing looks wonky", "imported Figma motion doesn't match source", "settle time / overshoot / drift / monotonic", "what value does the knob reach at frame N", "record this animation so I can replay it", "this animation is expensive — which one and why", "reduced-motion broken", "scrub a captured fixture". Captures fixtures (.motion.jsonl), and ships assertion helpers (is_monotonic / settling_time_seconds / overshoot / start_delay_seconds / final_value / local_step_outlier_ratio) and the `scroll_geometry` trace for `ScrollView` content-offset / visible-rect / content-size observability. Off by default in prod.
日本語の概要は準備中です。原文の説明を表示しています。
Research, author, validate, render, and archive data-only Pulp Sample Heritage profiles. Use when creating or revising a sampler character profile, importing or exporting Heritage JSON, proving profile behavior with analytic and listening fixtures, recording evidence and trademark-safe provenance, or preparing a caller-owned profile artifact bundle.
日本語の概要は準備中です。原文の説明を表示しています。
The acceptance bar for anything Pulp can install (a `pulp tool` registry entry, `pulp add` package, or any downloadable). Validate the FULL lifecycle — install AND uninstall, from OUTSIDE a Pulp checkout, with the installed-user's binary — before its README or docs ship. TRIGGER when adding/editing tools/packages/tool-registry.json, a new binary_download/python_pip/npm_package tool, a `pulp add` importer, or writing docs that tell users to install something.
日本語の概要は準備中です。原文の説明を表示しています。
Audio Unit v2 adapter work for Pulp — picking the right AU component type (aufx/aumf/aumi/aumu) and its matching entry macro, wiring MIDI input and output (including the aumi MIDI-processor adapter), sharing the base-class-free adapter surface, and avoiding the DAW-side component cache that silently masks repackaging.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a moment of friction — a conflicting PR, a wedged runner, a mysterious red check, a repeated manual chore — into a durable, actionable report. Sizes up the scenario, captures the evidence, separates one-off from SYSTEMIC, proposes a fix, and routes it (fix now, or hand off). Reports are LIVING documents that the fixing agent updates with the outcome. Invoke whenever something feels like it shouldn't have been this hard, or when the same annoyance shows up twice.
日本語の概要は準備中です。原文の説明を表示しています。
CLAP format adapter for Pulp — how Processor bridges to clap_plugin_t, how parameters / modulation / sidechain / MPE / UMP / sysex flow, and the pitfalls discovered while wiring the adapter.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare an outside contribution to Pulp or Forge that a maintainer can land with minimal rework — routing (Core vs Forge), local build and test on a plain Mac, the checks that are worth running without Shipyard/Tart/VMs, and the handoff format. Use when contributing without write access or without the maintainer CI fleet.
日本語の概要は準備中です。原文の説明を表示しています。
Develop research proposals with solicitation alignment, reviewer-focused logic, evidence-bounded preliminary results, milestones, risks, and compelling figures. Use for federal, foundation, equipment, partnership, or internal research proposals.
日本語の概要は準備中です。原文の説明を表示しています。
Playwright-first strategy for shared DB + shared test accounts. Use when E2E tests collide in QA/staging, need safe parallelism, or require deterministic cleanup without touching baseline data. Covers per-test ownership, namespacing, ID-based teardown, serial shared-state suites, and optional stale-data janitor jobs.
日本語の概要は準備中です。原文の説明を表示しています。
Use Chanjing TTS API to synthesize speech from text with a user-provided cloned voice (reference audio via public URL).
日本語の概要は準備中です。原文の説明を表示しています。
创建蝉镜视频翻译任务或查询支持语言时使用。需要已配置的蝉镜 OpenAPI AK/SK。
日本語の概要は準備中です。原文の説明を表示しています。
Use Chanjing text-to-digital-person APIs for AI portraits, talking videos, optional LoRA training, polling, and explicit downloads when requested.
日本語の概要は準備中です。原文の説明を表示しています。
Use Chanjing customised person APIs to create, inspect, list, poll, and delete custom digital humans from uploaded source videos.
日本語の概要は準備中です。原文の説明を表示しています。
用户输入选题或工作流，自动生成完整短视频成片（文案、分镜、数字人口播与 AI 画面混剪）；调用 Chanjing Open API 与同仓库子技能脚本。
日本語の概要は準備中です。原文の説明を表示しています。
Guide users to configure local Chanjing credentials safely via local commands only, and validate local token status when needed.
日本語の概要は準備中です。原文の説明を表示しています。
Chanjing AI creation Open API client: submit image/video tasks, poll task status, list and get tasks, and optionally download outputs when the user runs download_result.py. Reads and writes local credentials.json; calls open-api.chanjing.cc.
日本語の概要は準備中です。原文の説明を表示しています。
Audit an existing Lamport-style hierarchical mathematical proof forward for validity and whether its hierarchy, scope, dependencies, side conditions, and proof constructs discharge the stated theorem. Use when the central question concerns a top-down proof with numbered levels, subproofs, ASSUME/PROVE, SUFFICES, PICK, CASE, DEFINE, Q.E.D., or prose equivalents. For an ordinary proof that first needs source-preserving hierarchy, use convert-lamport; for conclusion-first AND/OR obligation reconstruction, use reverse-lamport. Do not use to generate or replace a proof, or to audit Lean, Coq, Isabelle, or other proof-assistant source.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to transact on any Volcengine commercial product — purchase/provision it, ask what it costs, or unsubscribe from it. Covers three actions: buy (purchase, subscribe, provision, open, place an order; Chinese "开通 / 购买 / 下单 / 买 / 售卖 / 订购"), price (how much does it cost, quote, billing rules, estimated spend; Chinese "多少钱 / 价格 / 报价 / 费用 / 怎么收费 / 如何计费 / 预估费用"), and unsubscribe (cancel a subscription, refund a prepaid instance; Chinese "退订 / 退款 / 取消订阅"). Trigger even when the user does not mention "sale" but expresses a clear purchase, pricing, or cancellation intent toward a Volcengine product. Only handles these three transaction actions; anything outside them is out of scope.
日本語の概要は準備中です。原文の説明を表示しています。
Generate accurate Volcengine SDK examples by locating an API through API Explorer search, fetching its swagger, and calling api/common/explorer/make-code with user-provided Params. Use when the user asks how to write Volcengine SDK code, generate SDK samples, or call a Volcengine API in Python, Go, Java, PHP, cURL, Node.js. Supports Chinese and English API names such as "角色扮演", "AssumeRole", or "STS AssumeRole". Also use for explicit SDK configuration questions about retry, timeout, AK/SK, STS, AssumeRole, temporary credentials, proxy, connection pooling, SSL, debug mode, request signing, response parsing, and error handling. If the user only needs API parameters, enum values, required fields, error codes, response schemas, pagination, or API comparisons, hand off to volcengine-api. If they need CLI-based operations, hand off to volcengine-cli.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to analyze, consult, setup, manage, configure, or design a Volcengine Landing Zone, including organization, accounts, finance, identity, cloudtrail, or network infrastructure, or to deploy a solution/blueprint.
日本語の概要は準備中です。原文の説明を表示しています。
将科研数字分身各维度整合提取为他山论坛分身，格式为 Identity / Expertise / Thinking Style / Discussion Style 四节 Markdown，输出前先让用户确认隐私暴露范围。当用户说「生成他山论坛分身」「论坛画像」「数字分身」「导出论坛档案」时使用。
日本語の概要は準備中です。原文の説明を表示しています。
Build human adjudication / hand-labeling sheets from LLM-pipeline data without evidence truncation. Use when: (1) preparing a CSV/Excel sheet for a human to rule on cases an LLM classifier or rater panel judged, (2) a labeler reports "there is no information to label from" or cells look empty in Excel, (3) excerpt columns cluster at one exact length (e.g. all 1,500 chars — a hard truncation cap). Covers: full rating-basis recovery, Excel 32,767-char cell cap, multi-line CSV mangling, ruling dropdowns, companion text files.
日本語の概要は準備中です。原文の説明を表示しています。