instructions

Author: saadeghi

.github/instructions/code_generation.instructions.md

@@ -56,7 +56,7 @@ applyTo: "**"
 - We use Bun test runner for testing. Read Bun docs for more info: https://bun.sh/docs/cli/test
 - For tests, use the available Bun test features and syntax, if you need to install an addional package, ask first
 - Always write testable code
-- After generating new code, write a temporary test file at `/tmp/FILENAME.test.js` to check the functionality of the generated code. `tmp` folder is ignored in git and you don't need to remove the remove the test file after you're done
+- After generating new code, write a temporary test file at `/tmp/FILENAME.test.js` to check the functionality of the generated code. `tmp` folder is ignored in git and you don't need to remove the test file after you're done
 - If you're asked to write a permanent test file, write the test file within the project structure, do not write it in `/tmp`
 
 ## Debugging

.github/instructions/packages.daisyui.instructions.md

@@ -11,3 +11,20 @@ applyTo: "packages/daisyui/src/**,packages/daisyui/functions/**"
 - Avoid repetition if possible
 - Do not use `!important` at all costs
 - daisyUI themes use OKLCH color space by default
+
+## Files
+
+- daisyUI components: `packages/daisyui/src/components`
+- daisyUI base styles: `packages/daisyui/src/components`
+- daisyUI utilities: `packages/daisyui/src/utilities`
+- daisyUI themes: `packages/daisyui/src/themes`
+- daisyUI build functions and tests: `packages/daisyui/functions`
+
+## Fixing daisyUI issues
+
+1. Read the issue carefully
+2. If the issue is not clear, ask for more information
+3. Find the CSS file or JS files that may be causing the issue
+4. Provide one or more logical solutions to the issue and let us decide which one to implement
+5. Implement the chosen solution
+6. Apply the solution without breaking existing functionality or changing other parts of the code