Hi All, Interesting exchange with Claude just now:
Me: ❯ Do you already know Faust well enough to write it, or should we make a Claude Code "skill" for more Faust expertise? Claude Opus 4.6 [Thinking]: ⏺ I know Faust reasonably well from training -- the composition operators, standard libraries, how compute() loops are structured in generated C++, etc. But I'd be more reliable with a skill, for two reasons: 1. Subtle semantics -- The interaction between ~ feedback, <: split fan-out rules, and partial application can trip me up on non-trivial programs. Having the primer in context would catch those. 2. Project-specific Faust→C++ patterns -- Your faust_cpp/ directory has a specific style: JGFaustLib.h utilities, hand-optimized biquads, the way mydsp::compute() structure maps to native classes. A skill could load both the language primer and your project conventions so translations stay consistent with what's already in faust_cpp/. My recommendation: make a skill. It would be lightweight -- just load FAUST_PRIMER.md plus a project-conventions section drawn from faust/JGFaustLib.h and an existing example like JGCabinet. Then any time you ask me to write Faust, /faust would put the right context in the window. [I attach my FAUST_PRIMER.md, ~12.8kB, written by Claude from my teaching tutorial, but note that it is NOT COMPLETE! It's just what I regularly use. A better primer would condense the Faust Quick Reference manual. (Claude, Codex, or Gemini would all do a good job on that).] Cheers, Julius P.S. I've written ~0 code in 2026, but I've managed a LOT -- AI has taken my job, but only I know what it is.
FAUST_PRIMER.md
Description: Binary data
_______________________________________________ Faudiostream-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
