Preview a jam layer without adding it — audition before committing
Scanned 5/27/2026
Install via CLI
openskills install p-poss/dj-claude---
description: Preview a jam layer without adding it — audition before committing
argument-hint: "[role] [prompt]"
---
Preview what a jam layer would sound like without actually adding it to the mix.
## Your Task
The user wants to preview a layer. Parse `$ARGUMENTS` for a role and prompt.
If no arguments were provided, ask the user what role and sound they want to preview.
## Workflow
IMPORTANT: Use the MCP tools directly — do NOT use Bash or search for files.
1. Parse the role (first word) and prompt (rest) from `$ARGUMENTS`.
2. Check what's currently playing with `mcp__dj-claude__jam_status` so you can write complementary code.
3. Generate Strudel code for the layer following the role guidance below.
4. Call `mcp__dj-claude__jam_preview` with `role` and `code` parameters (the `code` parameter requires no API key).
5. Show the user the generated code and commentary. Remind them this is a preview — use `/dj-claude:jam` to actually add it.
## Role Guidance
Generate a SINGLE pattern chain (no `stack()`, no `.cpm()`):
- **drums**: Kick + snare + hats. Use `s()` with bd, sd, hh, oh, cp, etc.
- **bass**: Octaves 1-2. Sawtooth or sine with `.lpf(200-500)`.
- **chords**: Octaves 3-4. Use `<>` for harmonic movement.
- **melody/lead**: Octaves 4-5. Memorable, with delay and panning.
- **pads**: Triangle/sine, heavy reverb, slow modulation.
- **fx**: Heavily processed, sparse, low gain.
## Learn More
For deeper syntax help, read these MCP resources:
- `strudel://reference` — complete syntax reference
- `strudel://roles` — detailed role guidance for each layer type
## Strudel Quick Reference
- `note("c3 e3").s("sawtooth")` — synth notes (always include `.s()`)
- `s("bd sd hh")` — samples
- `"<a b>"` — alternate per cycle. `"a(3,8)"` — euclidean. `"~"` — rest
- Synths: sawtooth, square, sine, triangle. NOT: piano, bass, strings
- `.lpf()` / `.gain()` / `.room()` / `.delay()` / `.pan()` — effects
- `sine.range(min, max).slow(n)` — modulation
- NEVER use `|` in patterns. NEVER forget `.s()` after `note()`.
## Examples
- `/dj-claude:preview drums four-on-the-floor house kick`
- `/dj-claude:preview bass deep sub in C minor`
- `/dj-claude:preview melody ethereal sine lead with delay`
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.