4,606 件 ・ 関連度順
概要と使いどころ
Guide users through `pulp upgrade` — discover new CLI releases, interpret migration notes for the hop they're performing, and apply breaking-change fixes (CMake macro renames, API surface changes, config file moves). Handles "upgrade pulp", "what's new", "migrate my project", "show breaking changes", and the `/upgrade` slash command. Pairs with the embedded migration index shipped in the CLI binary.
日本語の概要は準備中です。原文の説明を表示しています。
Baseline, half-leading, and font-face resolution for Label and captured (browser-imported) text — the arithmetic that decides where a glyph lands and how wide the box must be, plus the measure-vs-paint divergences that make text clip or sit low without any test going red.
日本語の概要は準備中です。原文の説明を表示しています。
Pulp in the browser — the WAM v2 and WebCLAP adapters, the wasm runtime, the Skia/WebGL2 browser window host, and the WebGPU (emdawnwebgpu) GPU-audio lane. Covers what does and does not compile to wasm, the worklet-thread constraints (no std::thread, no fetch, no navigator.gpu), the non-realtime tick, memory growth, how to PROVE a GPU lane actually ran rather than silently falling back to CPU, and the silent-failure traps that make a wasm build "work" while producing no audio or no pixels.
日本語の概要は準備中です。原文の説明を表示しています。
Record, compose, publish, serve, and review short desktop validation video proofs for Pulp UX/test-harness work. Use when the user asks to "show me it working", record a validation video, prove a click/interaction, share a local proof link, attach a video to a review issue, or compare an implemented UI against source material. Covers macOS desktop capture, Remotion proof composition, attachment budgets, local/Tailscale serving, and review closure.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
How to write source comments, doc comments, and test names/tags that have lasting value — and what to never write. Consult before adding or editing comments in core/**, examples/**, tools/**, test/**, docs/**, or any shipped source. Handles "write a comment", "is this comment ok", "comment hygiene", and keeping new code from adding the breadcrumbs the cleanup stream removes.
日本語の概要は準備中です。原文の説明を表示しています。
Prove a UI or generation feature actually works before asking a human to look at it. Covers A/B-ing an imported design against its source render, driving controls headlessly so a dead button cannot ship, proving the generator really spawns, and launching the real host (VCV Rack, a DAW). Use before any "take a look" on imported UI, plugin shells, or prompt-to-artifact pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
The measurement surface for ALL Pulp DSP and audio-pipeline work — read it BEFORE writing or gating DSP, not only when something already sounds wrong. Covers the C++ harness (signal generators, metrics, assertions, RenderScenario, contracts), the offline Audio Doctor (magnitude/frequency response, THD/THD+N, phase/group delay), and their Python sibling the Audio Quality Lab (tools/audio/quality-lab — null residual + alignment, LTAS log-spectral distance, spectral flux/centroid, HNR, Theil-Sen drift slope, Kaiser-sinc resampling, license-guarded corpus, regression-net ratchet). TRIGGER on AUTHORING work — "build/design an oscillator/filter/synth/effect", "add a DSP module", "what should the acceptance gate be", "how do I measure aliasing / anti-aliasing / alias floor", "null against a reference", "is this DSP correct", "choose a tolerance", "golden/regression corpus for audio", "measure drift or jitter", "A/B two renders" — AND on DEBUGGING work — "is there sound / no audio / I hear nothing", "does this filter/compressor/synth/delay produce the right signal", "prove the DSP / prove the contract", "measure the frequency response", "what's the THD / is it distorting", "what's the group delay / phase response / measured latency", "magnitude response curve", "render a test tone and assert", "audio regression", "64-frame works but 128 is silent", "sample-rate change pitch-shifted it", "describe what's in this buffer", "audio doctor", "compare before/after a DSP refactor". Reach for this BEFORE hand-rolling any FFT, null test, alias measurement, pitch tracker, or golden-render script — most of it already exists in one of the two lanes. Test/tool layer over HeadlessHost — deterministic, no audio device, no speakers. Off the realtime thread entirely.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and promote events — conferences, trade shows, webinars-as-events, and field marketing that drives pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Split documents for retrieval effectively — fixed, semantic, structural, and hierarchical chunking with overlap tuning. Use when RAG retrieval quality depends on how documents are divided.
日本語の概要は準備中です。原文の説明を表示しています。
Designing backup strategies for PaaS-hosted apps — what to back up, how often, and proving restores work.
日本語の概要は準備中です。原文の説明を表示しています。
Architect persistent, searchable memory for agents — episodic, semantic, and procedural stores with retrieval, consolidation, and forgetting policies. Use when designing how an agent remembers across sessions.
日本語の概要は準備中です。原文の説明を表示しています。
Build streaming AI user interfaces with AI SDK patterns — message rendering, tool-call displays, loading states, and optimistic updates. Use when creating chat UIs that stream model output and show agent activity.
日本語の概要は準備中です。原文の説明を表示しています。
Product-led growth and customer-base growth for B2B SaaS. Use this skill for self-serve funnel work (activation, time-to-value, free trial vs freemium, PQL definition, in-product upgrade moments, sales-assist triggers), for the self-guided interactive product demo that runs in front of the login wall (demo portfolio and flow design, gated vs ungated policy, demo seed data and privacy, keeping a published demo in sync with the shipping product, step-level demo analytics), and for growing revenue from existing customers (adoption, expansion, churn-save, the self-serve cancel flow and failed-payment recovery, renewal marketing, net revenue retention, and champion tracking: watching the people who bought and used you at each customer, confirming a job change from evidence, and running both plays a move fires, the seat they left and the account they joined). Also triggers on: PLG, product-led growth, activation, aha moment, time to value, free trial, freemium, PQL, product qualified lead, onboarding, self-serve, customer marketing, expansion revenue, upsell, cross-sell, churn, retention, NRR, renewal, cancel flow, cancellation flow, save offer, exit survey, pause subscription, dunning, failed payment recovery, involuntary churn, people keep canceling, champion tracking, job change signals, job change alerts, our champion left, our champion changed jobs, customer alumni, former customers who moved to a new company, interactive demo, self-guided demo, product tour, click-through demo, demo automation, demo library, should our demo be gated, ungated demo, demo without a sales call, our demo is out of date, demo shows the old UI, put a demo on our homepage, demo completion rate, demo drop-off, try before you talk to sales.
日本語の概要は準備中です。原文の説明を表示しています。
Sales enablement, technical presales and deal acceleration for B2B SaaS revenue teams. Use this skill when planning outbound campaigns, running discovery calls, building deal strategy, creating battle cards, writing proposals, responding to RFPs, preparing a product demo, scoping a proof of concept or pilot, answering a security questionnaire or the AI annex buyers now attach to it, executing sales sequences, coaching qualification, or deciding what the website's AI chat agent is allowed to say. Also triggers on: outbound, cold outreach, reply handling, reply classification, out-of-office replies, auto-replies counted as replies, our reply rate is inflated, prospect replied remove me, opt-out by reply, is this list ready to send, launch readiness, CRM segment outbound, we emailed a current customer, outbound hit an open opportunity, ownerless leads, prospects engaging our competitors, competitor connections, displacement list, is this personalization creepy, can we mention they visited our site, signal freshness, deal strategy, pipeline, battle card, objection handling, common objections, why do we keep hearing this objection, mine call transcripts for objections, objection register, proposal, RFP, discovery call, MEDDPICC, sales sequence, qualification, sales engineer, solutions engineer, presales, demo plan, demo script, POC, proof of concept, pilot success criteria, technical evaluation, technical win, security questionnaire, vendor security review, SOC 2 questionnaire, AI security questionnaire, AI annex, AI vendor due diligence, the buyer is asking if we train on their data, do you train on customer data, which model do you use, model provider sub-processor, AI subprocessor disclosure, where does inference run, can the customer turn the AI feature off, AI-CAIQ, CSA AI Controls Matrix, ISO 42001, ISO/IEC 42001, NIST AI RMF, EU AI Act Article 50, are we a provider or a deployer, AI feature disclosure, our model vendor changed and nobody told the buyer, technical objection, mutual action plan, MAP, close plan, mutual close plan, buyer enablement, the deal is stalled, deal stalled after the demo, how do I get this deal to close, close date keeps slipping, JOLT, buyer indecision, no-decision loss, website chatbot, chat widget, AI chat agent, AI SDR, inbound AI SDR, conversational marketing, live chat, what should our chatbot be allowed to say, our chatbot quoted the wrong price, the bot promised a discount, do we have to disclose it is AI, EU AI Act chatbot disclosure, chatbot handoff to sales, chat transcript review, prompt injection on our chatbot, Drift, Qualified, Intercom.
日本語の概要は準備中です。原文の説明を表示しています。
Implementation guide for common DSP algorithms. Use when the user asks "implement a lowpass filter", "how do I write a compressor", "reverb algorithm", "FFT convolution", "pitch shifter", or "oscillator with no aliasing". Trigger on phrases like "biquad filter", "state variable filter", "feedback delay network", "phase vocoder", "overlap-add", "PolyBLEP", or any request to implement a specific DSP processing block.
日本語の概要は準備中です。原文の説明を表示しています。
Profiling strategy for audio CPU issues — xruns, spikes, and buffer underruns. Use when the user reports CPU overload, audio glitches under load, or performance regressions. Trigger on phrases like "I'm getting xruns", "my plugin causes CPU spikes", "dropouts under high voice count", "audio thread is too slow", "how do I profile my DSP". References audio-numerics-review for denormal slowdown and audio-dsp-review for lock contention.
日本語の概要は準備中です。原文の説明を表示しています。
Guides implementation of custom Wwise or FMOD DSP plugins from scratch — effect, source, and mixer plugin types. Use when the user wants to create a new Wwise plugin, build an FMOD DSP effect, or implement a custom game audio middleware plugin. Trigger on phrases like "create a Wwise effect plugin", "build an FMOD DSP", "implement custom game audio middleware plugin", "how do I write a Wwise source plugin", or "set up an FMOD DSP description".
日本語の概要は準備中です。原文の説明を表示しています。
Production-grade TypeScript reference for React & Next.js frontend development. Covers type narrowing, component Props, generic hooks, discriminated unions, as const, satisfies, Zod validation, TanStack Query, server/client boundaries, forms, state management, performance, accessibility, debugging, and code review. Use when the user works with TypeScript in React or Next.js: type errors, Props design, generics, API typing, SSR/CSR boundaries, hydration issues, form validation, state management, performance, or code review. Also use for "how should I type this?", "why does this type error happen?", or any architectural decision involving TypeScript in a frontend context.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Unity 6+ UI Toolkit Runtime Data Binding code using MVVM pattern with [CreateProperty], DataBinding, and PropertyPath. Use when creating UI screens, HUDs, menus, inventories, settings panels, or any data-bound UI elements with UI Toolkit. Triggers on requests like "create a health bar", "build the HUD", "make a settings screen", "bind data to UI", "create an inventory UI", "add a pause menu", "show player stats on screen", "build a shop UI", "create a dialogue box", or any task involving runtime UI layout, styling, or data display. Also use when the user mentions UXML, USS, ViewModel, or UI bindings. Only activates when ProjectConfig.yaml -> ui_system is "UIToolkit" or "Mixed". Requires Unity 6.0+.
日本語の概要は準備中です。原文の説明を表示しています。
Use when diagnosing structural maintainability problems in existing frontend code before deciding how to refactor it, especially when evidence, false-positive checks, and candidate transformations are needed without editing business code.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Energy Engineer working on building and industrial energy efficiency — running an ASHRAE Level 1/2/3 energy audit, calculating envelope heat loss/gain with the degree-day method, comparing HVAC equipment on SEER/EER/IEER/COP rather than nameplate alone, designing an IPMVP measurement and verification (M&V) plan, or ranking energy conservation measures (ECMs) by savings-to-investment ratio for a capital plan. Distinct from a wind-energy-engineer or solar/PV engineer (own generation-asset design and yield) and from an electrical-engineer (owns utility-scale power delivery and protection) — this role owns the demand side: how much energy a building or process actually needs, and which retrofit reduces that number with numbers that hold up after the fact.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Economist — estimating a demand elasticity or causal treatment effect from observational or experimental data, building a cost-benefit or welfare analysis for a policy or pricing decision, forecasting a macro or market aggregate under stated assumptions, or stress-testing whether a "the data shows X" claim survives a confounding-variable check.
日本語の概要は準備中です。原文の説明を表示しています。