danielraffel

Pulp musical/media time primitives, immutable compiled tempo maps, monotonic transport beats, exact sample anchors, corrected inverse conversion, and shared transport quantization arithmetic.

Import designs from Figma, Stitch, v0, Pencil, React Native, or Claude Design into Pulp web-compat JS with automated visual validation. Claude Design imports also scaffold a pulp::view::EditorBridge handler file. Versioned parser, format, and compatibility-schema detection lives behind `--detect-only` and `--report-new-format`.

Pick the right Pulp Stream for a given I/O task, wire async callbacks correctly without deadlocking the worker, and avoid the backpressure / cancellation footguns in `pulp::runtime::AsyncStream`.

Editor lifecycle and multi-view attach for Pulp plugins — when to override Processor::create_view(), the open → notify_attached → resize → close protocol, release_view() ownership rules, and secondary-view roles.

Load, run, and test VST3 / AU / CLAP / LV2 plugins from Pulp code. Use when working on `core/host/` (scanner, plugin_slot, signal_graph), when adding a new format backend, when wiring a plugin into a SignalGraph, or when writing an integration test that needs a real plug-in binary.

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.

Local and cloud CI for Pulp — validate branches, create PRs, merge on green. Handles "push to main", "ship this", "run CI", "check PR", and "list PRs".

iOS platform development for Pulp — iPhone/iPad AUv3 app extensions, iOS Simulator builds, UIKit window host, CoreAudio IO audio, touch & Apple Pencil input, XcodeBuildMCP automation. Covers configure, build, deploy to simulator/device, and the gotchas discovered during iOS bringup.

Optional ARA support for Pulp, including developer-supplied ARA SDK setup, CMake enablement, adapter companion APIs, validation, and ARA-aware plugin implementation guidance.

Local and cloud CI for Pulp — validate branches, create PRs, merge on green. Handles "push to main", "ship this", "run CI", "check PR", and "list PRs".

Checklist and decision tree for adding, modifying, or removing CLI commands. Keeps CLI source, slash commands, docs, and skills in sync.

Real-DAW (REAPER) functional smoke for reload/editor/format-adapter changes — opt-in, scoped, headless-safe, zero-pollution

Sign, notarize, package, and distribute Pulp plugins and apps across macOS, Windows, and Android

Stand up a fast, cached, isolated, disposable macOS CI lane on Tart — layered golden VM images, ephemeral per-job GitHub Actions runners, host-mounted caches, and a reusable per-repo vm-image manifest. Use when setting up VM-based CI for Pulp or generalizing it to another repo, building/refreshing golden images, wiring ephemeral runners, or debugging the VM lane.

Build or iterate on a Pulp WebView UI using the native WebView bridge, embedded assets, directory-backed dev resources, and focused WebView validation.

Keep a plugin/demo repo's screenshots in sync with its UX. When editor / UI / design-token code changes in an opted-in repo (one carrying .pulp/screenshots.toml), re-capture and refresh every place each shot is consumed — README images, web-demo Open Graph (og.png) images, and gallery thumbnails — consistently across the WAM and WCLAP demo sites. Two capture routes: native headless (render_to_png / pulp-screenshot, Skia) for README / native-editor shots, and live-web headless Chrome (playwright-core) for WAM/WCLAP demo OG + gallery images. Backfills demos missing OG images. This is a PORTING / consistency tool — it re-shoots a repo's OWN UI, it never clones another product's art.

This skill should be used when the user asks about "JUCE-Plugin-Starter", "starter template", "init plugin project", "plugin template", "juce project setup", ".env configuration", "plugin codes", "bundle ID", "generate_and_open_xcode", mentions placeholder replacement, discusses creating new JUCE plugin projects from a template, or asks about VST3 MIDI generator configuration, cross-DAW MIDI effect setup, IS_SYNTH/IS_MIDI_EFFECT settings, or Ableton Live VST3 MIDI routing. Provides knowledge about the JUCE-Plugin-Starter template conventions, build system, configuration, and VST3 MIDI generator patterns.

Ask Claude directly via bridge mode by default (`claude -p`), with optional deterministic prompt-package generation when explicitly requested.

Knowledge for designing and applying Visage theme tokens and JUCE LookAndFeel colors. Use when the user asks about colors, theming, palettes, styling, branding, dark mode, light mode, ARGB hex format, color schemes, or the theme-designer tool. Covers the JSON theme schema, C++ codegen, Palette API, OverrideId scoping, and the design workflow.

Guide for integrating the Visage GPU-accelerated UI framework with JUCE audio plugins on macOS and iOS/iPadOS. Covers Metal view embedding, event bridging, focus management, keyboard handling in DAW hosts, popups/modals/dropdowns, memory management, destruction ordering, native standalone appearance, required Visage patches, iOS touch event handling, safe area insets, and comprehensive Visage API reference (Canvas, Frame, Widget, Theme, Dimension, PostEffect, Event system). Patterns derived from production plugin development. Use this skill whenever building or debugging JUCE+Visage plugin UI, even if the user doesn't explicitly mention "Visage" — trigger on mentions of Metal rendering in JUCE, GPU UI in audio plugins, embedded MTKView, or bridge layers between JUCE and a GPU framework.

This skill should be used when the user asks to "improve performance", "optimize query", "use prompt repetition", "repeat my prompt", mentions "Google Research prompt paper", or discusses non-reasoning vs reasoning tasks. Provides research-backed guidance on when and how to apply prompt repetition for performance gains.

Cross-platform CI coordination with Shipyard — validates, ships, manages queue, and runs cloud workflows

Shipyard operations guardrails. Use when working in /Users/danielraffel/Code/shipyard, /Users/danielraffel/Code/shipyard-rust, or /Users/danielraffel/Code/shipyard-macos-gui on parity checks, drift checks, sandbox validation, live Tailscale/GitHub webhook validation, release signing, GUI validation, Pulp/consumer pin cutover, or any go/no-go migration work.

Adversarially review external plans and advance third-party GitHub pull requests through a normal maintainer cycle with exact-head evidence, isolated execution, concise contributor feedback, explicit ownership, and a human merge gate. Use when accepting or implementing a collaborator's plan; triaging, testing, reviewing, re-reviewing, unblocking, or preparing a third-party or fork PR; resolving a lingering or unclear review; or deciding whether the contributor or maintainer should perform follow-up work.

Post-release docs sync — regenerate CHANGELOG.md from git tags, install the post-tag GitHub Actions hook, and diagnose drift. Use when a release just landed and the CHANGELOG didn't update, when a project wants to adopt shipyard-managed release notes, or when CI flags "CHANGELOG.md out of date".

Set up a generic curl/PowerShell installer with checksum verification, README verification instructions, release-workflow checksum publishing, artifact attestations, and signed source refs. Use when a user says they want to make a project easy to install, add a curl | sh installer, harden an install.sh/install.ps1 flow, publish SHA256SUMS, verify release assets before extraction, use GitHub Release asset digests, add GitHub artifact attestations, configure Verified commits/tags, configure unattended file-backed SSH signing keys with 1Password backup, configure 1Password-agent signing, back signing keys up to 1Password, or capture a Deno/Helm/Syft-style installer verification pattern. Also use this when the repo has both an installer and downloadable GitHub Release artifacts such as .pkg, .dmg, .zip, .tar.gz, .exe, .msi, .deb, .rpm, .AppImage, .apk, or .aab; this skill covers both the installer path and release artifacts.

Set up verification for GitHub Release artifacts without adding a curl installer. Use when a repo publishes downloadable packages, examples, plugins, apps, archives, installers, or binaries such as .pkg, .dmg, .zip, .tar.gz, .deb, .rpm, .AppImage, .exe, .msi, .apk, .aab, or future iOS/mobile artifacts, and Codex should add SHA256SUMS, GitHub artifact attestations, immutable-release verification, release asset digest checks, signed source refs, and concise README verification instructions. Use this only when there is no install.sh/install.ps1 or installer path to create or harden; if the repo has both an installer and downloadable release artifacts, use setup-verified-installer instead.

After opening a pull request, stamp it with provenance so it can be traced back to this agent/session/machine/terminal-tab. Run this whenever you open a PR (gh pr create, a merge orchestrator, etc.) so the human can later find the exact session that produced the PR and resume it.

Bring Magenta RealTime 2 into a Pulp project and build/validate the MRT2 example plugins (cross-format, Apple Silicon). Handles the Metal Toolchain + MLX-26 prerequisites, headless weights, and `pulp add magenta-realtime-2`.