Looking for a technical cofounder for GameForge AI — working prototype
Hey everyone 👋
I'm 17 and I'm building GameForge AI, an AI-powered tool that lets people describe a game in natural language and generates a playable game from that description.
I already have a working prototype, so this is beyond the idea stage. The current project uses React, TypeScript, Vite, Supabase, and a custom Canvas game engine.
The prototype can already generate playable games, but it's still early. The biggest opportunity now is making the system much more flexible — more game possibilities, better customization, better generation, and eventually a much more powerful game creation experience.
Who I'm looking for
I'm looking for a technical cofounder, not a freelancer.
Ideally, someone who:
- enjoys building products from scratch
- is comfortable with React/TypeScript and/or game development
- has experience with Canvas, game engines, or interactive applications
- understands backend/database development
- is interested in AI + games
- likes experimenting and shipping quickly
- has strong opinions and is willing to challenge my ideas
- wants to potentially build a company together
I'm not looking for someone who just wants a list of coding tasks.
I'd like a partner who can look at the product, understand the vision, tell me what they think is wrong or missing, suggest better technical/product approaches, and help decide what we should build next.
You also don't need to know Lovable. It was used during development, but the underlying project is a normal React/TypeScript codebase with a custom Canvas engine and Supabase.
I'm handling the product direction and development right now. The project is still very early, and I don't have everything figured out — I'm looking for someone who wants to figure it out and build it together.
If you're interested in AI, games, and building a startup from an early working prototype, I'd love to hear from you.
If this sounds interesting, leave a comment below telling me a little about yourself and something you've built. If there's a good fit, we can continue the conversation from there.
The cofounder decision framework is interesting: you've proved generation works, so the team question becomes how to measure what actually constrains the next step. The difference between "users want more flexibility" and "users are hitting walls we can measure" determines hiring speed. Your technical partner will need to help you distinguish between feature requests and actual blocking failures. That precision drives prioritization.
You already have the harder proof that generation can produce something playable. I’d be curious whether the next requests from users are actually being blocked by the current generation limits, or whether “more flexibility” is mainly the assumption driving what you build next.