π FORGE Tagline: Stronger Than Yesterday. Identity: A premium AI-powered fitnessβ¦
- User
π FORGE
Tagline: Stronger Than Yesterday.
Identity: A premium AI-powered fitness platform that feels like your personal fitness headquartersβnot just another gym app.
Core Philosophy:
People come for the interface. They stay because FORGE becomes their fitness partner.
π¨ Overall Design Language Theme Matte black throughout the application. Minimal, premium, elegant. Spacious layouts with generous whitespace. High-quality typography (Inter). Subtle blue accent only for important actions. No flashy colors or gaming aesthetics. Every screen should feel calm and focused. π Landing Page (The Signature Experience)
This is what makes FORGE different.
Instead of a normal scrolling website, users experience a cinematic 3D journey.
Core Concept
The user isn't scrolling down a webpage.
They are descending into THE FORGE.
The website feels like exploring a premium environment.
Centerpiece
A tall Forge Pillar stands at the center.
Characteristics:
Matte forged steel Clean geometric design Minimal No unnecessary decorations Represents discipline, strength, and consistency
Everything in the landing page revolves around this pillar.
Camera Movement
This is your biggest idea.
Instead of moving vertically, the camera:
Orbits around the Forge Pillar. Slowly descends. Slightly rotates while moving down. Smoothly zooms during transitions. Reveals each section naturally.
Think of it as floating through a futuristic museum.
No jerky movements.
No sudden transitions.
Everything should feel smooth and premium.
Landing Page Sections
The journey unfolds like this:
Hero Section Train Fuel Recover Progress Coach Live Dashboard Preview Final Call-to-Action
Each section appears naturally as the camera orbits.
Hero Section
Large FORGE logo.
Tagline:
Stronger Than Yesterday.
Short mission statement.
Primary button:
Start Your Journey
π Daily Briefing Dashboard
This is the heart of FORGE.
Every morning starts here.
Priority:
Recovery Score Begin Today's Mission Daily Forge Score Nutrition Summary Workout Progress AI Insight Quick Actions
Users should understand their entire day in less than five seconds.
The dashboard is customizable.
πͺ Train Module
Purpose:
Execute today's workout.
Features:
Today's workout Exercise library Workout history Personal records Progressive overload Rest timer Workout completion summary π½ Fuel Module
Purpose:
Nutrition management made simple.
Features:
Manual meal logging AI meal scanner Calories Protein Carbs Fats Water intake Daily nutrition summary
The AI estimates nutrition rather than pretending to be perfectly accurate.
π΄ Recover Module
Purpose:
Help users recover smarter.
Features:
Recovery Score Sleep logging Hydration Stretch reminders Recovery history
Recovery Score is the most important metric on the dashboard.
π Progress Module
Purpose:
Show meaningful long-term progress.
Features:
Weight graph Strength graph Progress photos Weekly reports Monthly reports Lifetime Consistency Score
Users should clearly see improvement over time.
π€ AI Coach
This is the soul of FORGE.
Not a chatbot.
A fitness coach.
Personality Professional Friendly Calm Knowledgeable Respectful Behavior
The coach:
Answers all fitness-related questions. Uses the user's history only when relevant. Asks contextual follow-up questions. Never interrupts with unsolicited advice. Gives honest feedback. Explains the reasoning behind recommendations.
Example:
User:
"Why am I not improving?"
Coach:
"Looking at your last three weeks, I noticed you've missed two lower-body sessions and your average protein intake has been below your target. Those factors could be be contributing. Here's what I'd recommend..."
The coach should feel like talking to an experienced trainer.
π§ AI Memory
The coach remembers:
Goals Workout history Nutrition history Recovery trends Previous conversations
It should never invent information or make assumptions.
π Forge Score
Two scores:
Daily Forge Score
How well the user executed today's plan.
Lifetime Consistency Score
Measures long-term discipline.
π Honest Reviews
FORGE should never fake motivation.
Instead of saying:
"Great job!"
when the user skipped workouts...
It should say:
"Your sleep has improved this week, but your workout consistency dropped. Prioritizing two more sessions this week will help you get back on track."
Supportive.
Truthful.
Actionable.
π± Navigation Desktop
Left sidebar:
Home Train Fuel Progress Coach Profile Mobile
Bottom navigation:
Home Train Fuel Coach Profile π¬ Animations
Everything should feel premium.
Hover:
Slight elevation Gentle scaling
Cards:
Fade + Lift
Buttons:
Smooth scale
Page transitions:
Fade Slide
Landing page:
GSAP-powered orbit camera
No flashy effects.
π Responsive Design
Desktop-first.
Fully responsive on:
Tablet Mobile
No features removedβonly layouts change.
π― User Experience Goals
Within 5 seconds:
"This looks premium."
Within 30 seconds:
"I want to try this."
After one week:
"I actually enjoy opening this app every day."
After one month:
"I don't want to switch to another fitness app."
π« What FORGE Is NOT Not an AI showcase. Not a cluttered fitness tracker. Not a social media app. Not overloaded with features. Not filled with fake motivational quotes. β What Makes FORGE Different The Orbit Landing Experience β A cinematic journey around the Forge Pillar. Premium Matte Black Design β Minimal, timeless, and elegant. A Coach, Not a Chatbot β Context-aware, honest, and conversational. Daily Command Center β Everything important is visible in seconds. Invisible AI β Intelligence powers the experience without becoming the focus. Retention by Experience β Users return because the app is genuinely useful and enjoyable.
Assistant
I'll build FORGE - a premium AI fitness platform with the signature orbit landing experience. Let me start by exploring the project structure.
Now I have a clear picture. Let me install GSAP for the orbit camera animation and the Inter font, then build the full experience.
Now let me build the core data, types, and shared components.
Now let me build the iconic 3D Orbit Landing Page with GSAP. This is the signature experience.
The lint errors are expected since the section files don't exist yet. Let me build all the landing section components.
All sections are created. Let me fix the unused
progressvariable and then build the in-app modules.The unused
progresswarning is on the inner component. Let me check the line and fix it:Now let me build the in-app shell and modules. This is the actual dashboard application.
Now the module screens β Home dashboard, Train, Fuel, Recover, Progress, Coach, Profile.
Now the main app shell that ties everything together, and the main App component.
I notice I placed the imports in the middle of AppShell.tsx. Let me fix that.
Now let me build the project to check for errors.
Build succeeded on the first try. Let me verify the project structure and check a few important details, then refine a few areas to make the experience truly premium.
I notice the body has
overflow: hiddenset during landing, which will prevent scrolling the orbit experience. Let me reconsider β actually, the orbit experience needs scrolling to drive the GSAP animation. The body should be scrollable but the inner container drives the experience. Let me fix that and also improve a few things:- Fix the body overflow during landing (must allow scrolling for the orbit)
- The landing container has height 800vh so body needs to scroll
- Make sure the nav doesn't get cut off
Let me also enhance the orbit experience to make it more cinematic.
Now let me also enable a smooth, premium intro animation on the landing page, and improve the orbit camera a bit. Let me also make sure ScrollTrigger refreshes correctly when the landing mounts.
Let me clean those up:
Now let me improve the visual experience of the orbit landing. I want to make sure the descent and rotation feel truly cinematic. Let me also fix a subtle issue β the orbit descent is too much and the pillar is too tall, which may push content too far down. Let me check.
I think a descent of 3200px is good, and the zoom is good. Let me make the orbit experience even more refined by adding subtle camera adjustments. Let me also think about the side positions of the content β the orbit should reveal content as we descend.
Let me also test the build to make sure everything is still good.
Build is clean. Now let me also make a few quality improvements:
- The landing reveal animations use
scrubwhich means they animate based on scroll. This works. - Let me make sure the right side of the orbit camera view has the pillar visible but not overlapping content.
Let me make a key improvement β the camera should also shift horizontally as it orbits so the pillar doesn't sit dead-center the entire time, and content on either side reveals naturally.
Actually, looking back at the design intent: "Orbits around the Forge Pillar. Slowly descends. Slightly rotates while moving down. Smoothly zooms during transitions. Reveals each section naturally."
The current implementation does this. The pillar is centered and we rotate around it. Sections appear on alternating sides (left/right/center). This is the right concept.
Let me also make the orbit experience more dynamic by adding a slight horizontal drift. Actually, let me first verify everything works by inspecting the final result, and add a few polish touches:
Let me also add a horizontal sway to the orbit camera for a more cinematic feel β as it rotates around the pillar, the camera should shift left/right slightly. This is the kind of polish that makes the experience feel premium.
Now let me also improve the camera framing so the pillar is more clearly the centerpiece. I want to add a slight perspective rotation so the user feels they're really looking at the pillar from different angles. Let me update the perspective parent.
Wait, I need to check the structure after my edit. Let me re-read.
Good. Now let me build to check.
Builds clean. Let me think about what else could elevate this experience:
- The hero text should fade in on initial load β currently it might just appear. Let me add a cinematic intro.
- The pillar should be more visually striking β the etched wordmark is too subtle, and we could add stronger highlights.
- The dashboard should have richer interaction β it has some good elements.
Let me also add a cinematic intro on the landing.
Now let me wrap the hero text and pillar in the new animation classes:
Now let me also enhance the ForgePillar to be a bit more striking β better gradients, more visible "FORGE" etch, and a subtle base shadow.
Now let me build and check.
Builds clean. Now let me think about potential UX issues:
-
The "Back to landing" button takes you back to a scroll position of 0 β the orbit experience would be jarring to re-enter. Let me add scroll-to-top on exit/enter.
-
The landing uses 800vh height with sections that are 100vh each (8 sections). That's tight. Let me check the math: 800vh / 8 = 100vh per section β perfect for 8 sections.
-
The reveal animation uses
scrub: 1which means it animates over scroll range. Good. -
Let me also verify the dashboard and other in-app modules look great.
Let me also add scroll-to-top on the app transitions for cleaner navigation:
Now let me also think about one more important thing: the orbit camera animation depends on
position: fixedfor the 3D scene and a tall scrollable container. This should work. But let me ensure the body itself can scroll to drive it. Since the container is 800vh, the body should scroll naturally. Good.Let me build to confirm:
Excellent! Now let me verify the final structure looks right. Let me also do one final touch β the dashboard. Looking at the Home screen, the recovery and forge score cards are in the right place. The home is the daily command center.
Let me make one last refinement β the Coach screen conversation starts with 3 messages, which might feel a bit dense. Let me trim to 2:
Let me also do a final build to confirm everything is good:
Build is clean. Let me also verify the final project structure:
I notice there are two
cn.tsfiles (inlib/andutils/). Let me clean that up by removing the unused one:Final build is clean. FORGE is complete.
What I built
π Landing Page β The Signature Experience
A cinematic 3D orbit landing page powered by GSAP ScrollTrigger:
- The Forge Pillar β a tall matte forged-steel column at center, with etched "FORGE" wordmark, glowing accent rings, and animated highlight that travels up/down
- Camera orbit β as you scroll, the pillar rotates ~1.1 full turns, the camera descends 3200px, slowly zooms, and gently sways horizontally for a museum-like feel
- 8 reveal sections β Hero, Train, Fuel, Recover, Progress, Coach, Daily, CTA β each fading in as the camera passes
- Ambient details β descending progress %, status bar, side progress dots, vignette gradient
- Cinematic intro β hero text and pillar fade in on initial load
π In-App Experience (matte black throughout)
- Daily Briefing (Home) β Recovery Score, Begin Mission, Daily Forge Score, Lifetime Consistency, Nutrition, AI Insight, Quick Actions
- Train β Today's workout with interactive check-offs, rest timer banner, sets/reps/load/RPE rows, personal records
- Fuel β Macros dashboard, Log Meal / AI Scan / Water tabs, daily summary
- Recover β Recovery Score hero, sleep stages, hydration, soreness, 7-day trend chart
- Progress β Strength chart (3 lifts), body weight, progress photos (silhouette previews), weekly/monthly reports
- Coach β Full chat interface with memory sidebar, contextual responses that reference the user's actual history (bench plateau, protein deficit, sleep dip), and a thinking indicator
- Profile β Body metrics, goals with progress bars, preferences
π¨ Design Language
- Inter typography with tabular numerals
- Matte black (#050505) throughout
- Subtle blue (#3b82f6) accent reserved for important actions
- Honest reviews β coach says "protein dropped to 152g against 190g target" instead of fake motivation
- Responsive β desktop sidebar, mobile bottom nav
- Smooth animations β page transitions, hover elevations, fade-in cards
Every screen feels calm, focused, and premium. The coach is a coach, not a chatbot.
Files built:
index.html,src/index.css,src/main.tsx,src/lib/data.ts,src/lib/cn.ts,src/components/landing/OrbitLanding.tsx,src/components/landing/ForgePillar.tsx,src/components/landing/LandingSection.tsx,src/components/landing/Nav.tsx,src/components/landing/sections/Hero.tsx,src/components/landing/sections/Train.tsx,src/components/landing/sections/Fuel.tsx,src/components/landing/sections/Recover.tsx,src/components/landing/sections/Progress.tsx,src/components/landing/sections/Coach.tsx,src/components/landing/sections/Dashboard.tsx,src/components/landing/sections/CTA.tsx,src/components/app/Sidebar.tsx,src/components/app/MobileNav.tsx,src/components/app/TopBar.tsx,src/components/app/screens/Home.tsx,src/components/app/screens/Train.tsx,src/components/app/screens/Fuel.tsx,src/components/app/screens/Recover.tsx,src/components/app/screens/Progress.tsx,src/components/app/screens/Coach.tsx,src/components/app/screens/Profile.tsx,src/components/app/AppShell.tsx,src/App.tsx
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.