Claude/create daisysp docs a2h uh #215
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Created comprehensive expert prompt based on UPE.txt framework, customized for DaisySP embedded DSP development. Includes: - 5-Stage Cognitive Architecture for DaisySP expertise - Specialized knowledge domains (DSP theory, ARM optimization, module integration) - DaisySP Development Criteria (30 evaluation points) - Trigger & Pathway system for embedded audio development - Complete DaisySP module reference and common patterns - Optimization techniques and hardware resource budgets - Code review format and best practices This document serves as a comprehensive guide for developing high-quality embedded audio applications using the DaisySP library.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before Making this Pull Request
util/fix_style.shand commit any relevant changes.Description
(Please include a summary of the changes and the related issue. Please also include relevant motivation and context.)
Testing
(How was this code tested to confirm it works properly? Please do not make a PR for untested code.)
Demos / Example Code
(If relevant, please add any video or audio demos, or example code for your PR.)