Bridge
The audit is correct. We need to bridge the gap between Prompt 2 (Backend) and Prompt 3 (UI).
Fix the project using these steps:
1. Reconnect the Frontend to the Real API: In `page.tsx`, replace the mock timer and mock data with a real `fetch` call to `/api/analyze`.
2. Use the real API response to render the dashboard.
3. Clean up the `NormalizedProfile` type to strictly match the contract from Prompt 1.
4. Update UI status messages and Next.js image config to prevent runtime errors.
Final goal: When I enter a username and hit submit, I want real data from GitHub to go through the analyzer and display on the dashboard. No more mock data.when to use it
Community prompt sourced from the open-source GitHub repo SuleymanToklu/LLM-Comparison-Benchmarking (no explicit license). A "Bridge" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
SuleymanToklu/LLM-Comparison-Benchmarking · no explicit license
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions