Cultural Prompts

Build a complete, production-quality single-page music website inspired by the attached reference image. Working title: QUARTER ROOM Tamil title: குவாட்டர் ரூம் Tagline: தமிழ் குடிகாரர்களின் அதிகாரப்பூர்வ ரேடியோ The product is a cinematic Tamil music player for drinking songs, soup songs, breakup songs and late-night Tamil melodies. It should feel like entering a living Tamil street scene, not like browsing another Spotify playlist directory. Technical foundation If the repository already has a working frontend, preserve its stack and adapt it. Otherwise, use Next.js App Router, TypeScript and Tailwind CSS. Keep it as a single-page website. No authentication, database, dashboard, backend or payments. Build clean, reusable components without overengineering. Make the page fully functional, responsive and deployment-ready. Do not stop after producing a rough scaffold. Run the project, inspect the result and fix visual, responsive and console issues. Main experience The entire browser viewport should be a cinematic illustrated Tamil street at evening. The composition should resemble the reference: Full-screen atmospheric illustrated background. A small red Tamil bar/shop at the centre. Chennai or Tamil Nadu street architecture. Banana leaves, electric wires, plastic chairs, parked scooter, tea-shop details and warm street lights. A few friends sitting together outside the shop. Deep blue evening sky contrasting with warm red and orange buildings. Subtle grain, texture and imperfect hand-painted details. The interface should feel embedded into the scene. Do not make it look like a standard SaaS landing page. No white cards, feature grids, pricing sections, testimonials or conventional hero layout. Do not copy the reference artwork directly. Create an original Tamil environment using local SVG/vector artwork, CSS layers and gradients. Do not depend on random remote stock images. If a background asset is required, create a polished local SVG illustration and store it inside /public. The page should occupy exactly the viewport on desktop with no unnecessary scrolling. Header Place a minimal transparent header over the illustration. Top left: Live local time in 12-hour format. Update automatically every minute. Small Tamil Nadu/Chennai location label beneath it. Top centre or slightly right: A small pulsing green dot. Text: “LIVE” Do not show a fake listener count. Top right: Spotify icon and label. YouTube Music icon and label. Clicking either changes the active music provider. Clearly indicate the selected provider. Keep the styling minimal and integrated with the scene. Central identity Place the Tamil title prominently on the building: குவாட்டர் ரூம் Under it, display: தமிழ் குடிகாரர்களின் அதிகாரப்பூர்வ ரேடியோ The Tamil typography must be large, confident and readable. Use a Tamil-compatible font such as Noto Sans Tamil. Pair it with a clean sans-serif font for English text. Ensure font loading does not break the page if the external font fails. The title should feel painted or mounted onto the building, not floating randomly in the viewport. Music stations Create five curated mood stations: கடை திறந்தாச்சு Description: “Full TASMAC energy” Mood: energetic red and orange street scene. அவள நினைச்சா Description: “Love failure. Full volume.” Mood: darker red with subtle rain and lonely lighting. மணி 2:17 AM Description: “Everyone suddenly became silent.” Mood: deep blue terrace or empty late-night street. அவன் நினைச்சா Description: “Soup songs are not just for the boys.” Mood: purple and warm bedroom or bus-window lighting. பழைய சரக்கு Description: “Ilaiyaraaja, Rahman and old wounds.” Mood: dim amber 80s/90s bar atmosphere. Add a small “Change mood” button near the music player. Clicking it should open an elegant station selector above the player. Each station card should show: Tamil station name. Short English description. A distinct colour. A simple illustrated icon. Active station indicator. When the station changes: Crossfade the background colours and environmental overlays. Update the station title. Load the corresponding provider playlist. Keep transitions smooth and restrained. Do not reload the page. On mobile, the station selector can become a bottom sheet. Playlist configuration Keep every playlist URL and ID inside one easy-to-edit configuration file such as: src/data/stations.ts Each station should support: id nameTamil nameEnglish description accentColor backgroundVariant spotifyPlaylistUrl spotifyPlaylistId youtubePlaylistUrl youtubePlaylistId Use these public playlists initially: கடை திறந்தாச்சு Spotify: https://open.spotify.com/playlist/1AcwNZ0zLSPtIOea0uwxaJ YouTube playlist ID: PLxQpegrlImYt1j0PXBEl1-BO3n57kbTDC அவள நினைச்சா Spotify: https://open.spotify.com/playlist/2Yra1CyIYaJ2YNz49yjh4i YouTube playlist ID: PL5Zj_jk7tf5oCbRDVI2noHRi3l4JyL07h மணி 2:17 AM Spotify: https://open.spotify.com/playlist/1uLtum4DGySTEG4LpyCkEW அவன் நினைச்சா Spotify: https://open.spotify.com/playlist/47jt1RZSwPR2WRQpz8VG39 பழைய சரக்கு Create a clearly marked configuration placeholder so the playlist can be inserted later. Never scatter playlist URLs across components. Music player Place one floating player at the bottom centre, matching the composition of the reference. The player should look like a long translucent pill with: Dark warm glass background. Soft blur. Thin highlight border. Subtle shadow. Rounded ends. Album artwork on the left. Song title. Artist name. Current station name. Previous button. Large central play/pause button. Next button. Progress bar. Current time and total duration. Provider indicator. “Open in Spotify” or “Open in YouTube Music” link. The player should be approximately 620–720px wide on desktop and nearly full-width on mobile. Do not build decorative controls that pretend to work. Spotify playback Use Spotify’s official embed or iframe API. Load the active station playlist. Connect play and pause actions where officially supported. Display the official embedded player in a compact, visually integrated form. Do not illegally hide mandatory Spotify branding. Do not request a Spotify client secret. If browser or Spotify restrictions prevent a custom control from working, disable that control and rely on the official Spotify embed. Always include an “Open in Spotify” fallback. YouTube playback Use the official YouTube IFrame Player API. Embed playlists using: https://www.youtube.com/embed?listType=playlist&list=PLAYLIST_ID Connect play, pause, previous, next and progress updates. Use playsinline=1. Do not autoplay with sound before user interaction. Add an “Open in YouTube Music” link using the corresponding playlist URL. Handle unavailable, private or region-blocked videos gracefully. Initial interaction Because browsers block autoplay, show a tasteful first-entry overlay: Title: ஒரு mood தேர்ந்தெடு. Buttons: கடை திறந்தாச்சு அவள நினைச்சா மணி 2:17 AM அவன் நினைச்சா பழைய சரக்கு After the user chooses a mood: Close the overlay. Set that station as active. Begin playback only through the user’s click. Remember the selected mood and provider in localStorage. Track information When the provider exposes metadata, show: Track title. Artist. Artwork or video thumbnail. Current playback position. Duration. While metadata is loading, use an elegant skeleton state. If metadata cannot be retrieved, show the station name and provider without inventing track information. Animation and atmosphere Add restrained ambient animation: Slight movement in banana leaves. Gentle light flicker. Occasional passing shadow. Slow grain movement. Small smoke or steam effect near the shop. Subtle rain only for the heartbreak station. Very slow background parallax based on pointer movement. Player entrance animation after mood selection. Animations must remain subtle and should never distract from playback. Respect prefers-reduced-motion. Responsive behaviour Desktop: Full illustration visible. Tamil title centred on the building. Player at bottom centre. Header aligned to the viewport edges. Mood selector expands above the player. Tablet: Preserve the full cinematic composition. Slightly reduce title and player width. Mobile: Use 100dvh. Reframe the illustration vertically instead of merely shrinking it. Keep title readable. Header must not overlap. Player becomes a compact bottom player. Station selector opens as a bottom sheet. Keep touch targets at least 44px. Avoid horizontal scrolling. Account for iPhone safe areas. Visual standards Use dark red, burnt orange, faded coral, midnight blue, dusty green and warm cream. Avoid neon gradients, generic glassmorphism and overly clean corporate styling. Use glass effects only for the player and small controls. Add subtle paper, film-grain and paint texture. Maintain strong text contrast. Keep every text element deliberately positioned. No words should appear randomly around the screen. Avoid oversized empty areas. All alignment should follow a consistent visual grid. The experience should look intentional at 1440px, 1024px, 768px, 430px and 375px widths. Accessibility and quality Use semantic HTML. Add accessible labels to every control. Support keyboard play/pause using the spacebar when focus is not inside an interactive element. Add visible focus states. Ensure the station selector can be navigated by keyboard. Escape should close overlays. Avoid hydration errors. Avoid console warnings. Lazy-load provider embeds where possible. Do not expose API keys. Add error and empty states. Add a small responsible drinking line in the bottom corner: “Drink responsibly. இசை மட்டும் unlimited.” Metadata Page title: Quarter Room | Tamil Soup Radio Description: Tamil drinking songs, soup songs and late-night heartbreak playlists in one cinematic radio experience. Create a simple matching favicon using the Tamil letter “கு” or a quarter-glass silhouette. Final acceptance criteria The work is complete only when: The page feels visually close in quality and atmosphere to the supplied reference. It is an original Tamil street illustration. A user can select a mood. Spotify playlists load correctly. YouTube playlists load correctly where IDs are provided. Provider switching works. Player controls work wherever supported by the official APIs. Playback restrictions are handled honestly. The selected station persists after refresh. The page works on desktop and mobile. There are no broken controls, random text placements, layout overflows or console errors. The site looks like a finished cultural music experience, not a template. Build the complete implementation now. Do not return only a plan. After implementation, run the application, test every interaction and refine the visual alignment until it is polished.