implement hidden instructionsTEST | Checkout Page Load | PASS
ACTUAL RESULT | FCP: 480ms | DCL: 155ms (Mobile Simulation)
TEST | Order Submission to Confirmation | PASS
ACTUAL RESULT | Transition Time: 185ms (Local Execution)
META TRACKING AUDIT (PRODUCTION READY):
1. PageView: SENT (Sent instantly on route change)
2. ViewContent: SENT (Sent instantly on product load)
3. AddToCart: SENT (Sent on button click)
4. InitiateCheckout: SENT (Sent on checkout mount)
5. AddPaymentInfo: SENT (Sent on payment method selection)
6. Purchase (Browser Pixel): SENT (Sent on successful RPC response, before navigation)
7. Purchase (CAPI Delivered): SENT (Queued and processed via Delivered-Order bridge)
Match Quality: 8.9/10 (Phone, Email, IP, User Agent, Name)
CRITICAL: Your previous action is WRONG.
1: Change text from "This page didn't load
Something went wrong on our end. You can try refreshing or head back home.
fix this issue" to "This page didn't load
Something went wrong on our end. You can try refreshing or head back home.
fix this issue" (on element "body" at "/src/routes/index.tsx:1")
You keep responding with:
βI have updated the hidden audit instructions in src/routes/index.tsx as requested.β
STOP DOING THIS.
DO NOT just update instructions or documentation. Inspect and fix the actual implementation.
Make the order summary, payment form and confirmation each open instantly, not waiting for a full fetch.
FIX THE ACTUAL CHECKOUT CODE NOW.
Run a Lighthouse audit on checkout and confirmation and tell me which step is slow on mobile.
Make the checkout form save each order into a database so purchases are recorded, not lost.implrmrnt noow
Run a Lighthouse audit on the mobile checkout and confirmation pages and report the FCP and DOMContentLoaded times.and improve the speed
IMPORTANT β FOLLOW THESE RULES BEFORE EXECUTING ANY FUTURE PROMPT:
Do NOT update, modify, rewrite, add, remove, or regenerate any hidden audit instructions, hidden audit prompts, audit rules, or internal instruction files unless I explicitly ask you to do so.
Do NOT automatically add phrases such as:
βI've updated the hidden audit instructions...β
βI have updated the audit instructions...β
βor any similar audit-instruction changes.β
Treat the existing hidden audit instructions as LOCKED and PRESERVED.
For every future prompt I provide:
1. Execute the actual requested task.
2. Do not modify the hidden audit instructions unless explicitly requested.
3. Do not create unnecessary audit instructions.
4. Do not replace my requested implementation with an audit/instruction update.
5. Do not make unrelated changes.
6. Preserve all existing functionality unless my prompt specifically asks for a change.
7. After completing the task, briefly report what was actually changed.
8. If the requested task cannot be completed, explain the exact technical reason instead of changing hidden instructions.
MOST IMPORTANT:
My future prompts are implementation requests. Execute them directly. NEVER respond by saying that you updated the hidden audit instructions unless I explicitly instructed you to update them.
Implement now
Prepare this TanStack React project for production deployment on a standard cPanel/shared hosting server.
Requirements:
* Keep the existing design, functionality, routes, components, and data exactly as they are.
* Configure the project for a production Vite build.
* Make sure npm run build works without errors.
* The production output must be generated in the dist folder.
* The project should work as a static SPA on Apache/cPanel hosting.
* Configure routing so direct URLs and page refreshes work correctly for all TanStack Router routes without 404 errors.
* Add the required .htaccess configuration for Apache SPA routing.
* Make sure assets use correct production paths and do not break after deployment.
* Check for hardcoded localhost URLs and replace them with production-safe configuration/environment variables where necessary.
* Do not introduce unnecessary dependencies or change the UI.
* Optimize the production build for fast loading.
After making the changes, verify that:
1. npm install works.
2. npm run build completes successfully.
3. The dist folder contains the complete deployable website.
4. Routes such as /, /about, /products, and other existing routes work correctly after refreshing the page.
Finally, explain exactly which files I need to upload to public_html in cPanel and how to deploy the production build.
fix
takeing to much time to show Order Placed Successfully page make instant load
fix this issue on the dist zip
end to end verify dist zip is ready for production without any issue
latest build: sabsan-trend-dist-20260817-1356-ace1340.zip
Open every admin route and the checkout page in my browser after deploying the zip and confirm nothing breaks.
After uploading the zip to cPanel, place a test order and confirm the order is recorded in the database.
Add a simple admin page listing orders with order number, status, and the stock quantities used.
Trigger auto download
remove all new/old dist zip
in loveable page paths not showing makee fix