Debugging

The popup window opens correctly, but closing it does not work:
- Clicking outside the popup does nothing
- The "Cancel" button sometimes works, sometimes does not

Only fix how the popup closes:
- Clicking the area behind the popup should close it
- The "Cancel" button should always close it
- Pressing the Escape key should close it

Do not change how it looks or any other parts of the page.

This list is showing the same items twice, and sometimes
it does not update when I add a new item.

First, explain in simple terms what might be causing:
- Why items appear twice
- Why new items do not show up

Then suggest a small change to fix both problems,
and only make that change.

This page feels slow when loading a lot of information.

Check for things that might be making it slow:
- The page refreshing when it does not need to
- Loading the same information more than once
- Loading too much information when the page first opens

Explain what is making it slow, then suggest specific ways to make it faster.
Do not change how it looks, just focus on making it work better.

@pages/profile.jsx fix the submit button behavior. Check what happens when clicked and when form is submitted.

On the "Save" button in the profile form, clicking it does nothing:
- The button is visible and I can click it
- Nothing happens when I click
- No error message appears
- The information does not save

Do not change how the form looks or how it is styled.

@pages/tasks.jsx check whether the save function is being called and whether data is being sent correctly.

When I update a task and click "Save", the changes show up temporarily
but disappear after I refresh the page. The information is not being saved
to where it is stored.

Check:
- Whether the save function is being called
- Whether the information is being sent to where it is stored correctly
- Whether the response is being handled properly

Focus only on making sure information saves. Do not change how it looks.

@pages/dashboard.jsx check whether the user list is set up correctly and whether data is being loaded properly.

The user list does not show up on the dashboard page.
The page loads, but the list area is empty even though there are users
stored in the system.

Check:
- Whether the list is set up and used correctly
- Whether the information is being loaded properly
- Whether there are any errors preventing it from showing

Do not change other parts of the dashboard.

The [TABLE_NAME] table has RLS enabled but queries return empty results. Create RLS policies that allow authenticated users to read all rows and insert, update, or delete only their own rows (where user_id matches auth.uid()). Explain each policy you create.

Supabase calls are failing with JWT token errors. Make sure the Supabase client uses SUPABASE_URL and SUPABASE_ANON_KEY from environment variables. Add automatic auth session refresh so expired tokens get renewed. If the session expires, redirect the user to the login page instead of showing a broken state.

Social login is failing with a redirect URL mismatch. Update the auth callback handler to use the correct redirect URL. For development, use http://localhost:[PORT]/auth/callback. Remind me to add this URL to the Supabase dashboard under Authentication > URL Configuration > Redirect URLs. Handle the auth callback properly by extracting the session from the URL hash.

Stripe webhooks are not reaching the app after checkout. Verify the webhook endpoint is correctly set up at /api/webhooks/stripe. Check that the endpoint parses the raw request body (not JSON-parsed) for signature verification. For local testing, remind me to use the Stripe CLI with `stripe listen --forward-to localhost:[PORT]/api/webhooks/stripe`. Log incoming webhook events for debugging.

After Stripe checkout, users are not redirected back to the app. Update the success_url and cancel_url in the checkout session creation to use absolute URLs. Include the session_id query parameter so the success page can retrieve the session details.

Email sending is failing because the sender is not verified. Update the "from" address to use a verified domain. For development with Resend, use "onboarding@resend.dev" as the sender. Remind me to verify my custom domain in the [Resend/SendGrid] dashboard by adding the required DNS records (SPF, DKIM, DMARC). Add error handling that logs the specific failure reason.

Email sending is failing. Make sure API calls happen on the server, not the client. For development, use "onboarding@resend.dev" as the sender. Add error handling that logs the specific failure reason.

AI API calls are hitting rate limits. Add these safeguards:
- Debounce user-triggered AI calls so rapid clicks do not send multiple requests
- Add a loading state that disables the button while a request is in progress
- Implement exponential backoff retry (wait 1s, then 2s, then 4s) on 429 errors
- Show a user-friendly message: "AI is busy, please try again in a moment"
- Cache recent AI responses to avoid duplicate requests for the same input

AI calls are failing because the input exceeds the token limit. Fix this by:
- Truncating the input text to a maximum of [MAX_CHARS] characters before sending
- Show a warning if the user's input is too long: "Content is too long for AI processing. Only the first [MAX_CHARS] characters will be used."
- If summarizing long content, split it into chunks, summarize each chunk, then combine the summaries
- Use a model with a larger context window if available (e.g., gpt-4o instead of gpt-3.5-turbo)

The AI feature hangs with a loading spinner and never returns a result. Set a 30-second timeout on the API call. If it times out, show "AI is taking too long to respond. Please try again." Add a Cancel button that aborts the request. Log the full error details for debugging.

The deployment build is failing. Make sure all dependencies are listed in package.json. Fix any TypeScript errors or ESLint warnings that would cause a production build to fail. Verify all imported files and modules use correct case-sensitive paths.

The deployed app is missing environment variables, causing features to break. Create a .env.example file listing every environment variable the project needs, with placeholder values and comments. Include: SUPABASE_URL, SUPABASE_ANON_KEY, STRIPE_SECRET_KEY, STRIPE_PUBLISHABLE_KEY, [EMAIL_API_KEY], and any others found in the codebase. Add a startup validation check that logs which required variables are missing.