> For the complete documentation index, see [llms.txt](https://docs.superteamde.fun/superteam-germany-guilds/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.superteamde.fun/superteam-germany-guilds/hackathon-hub/team-formation.md). # Team Formation Where to find teammates, validate fit, and build with stronger momentum. Hackathons move faster when you find the right people early. ## Best Places To Start * [Colosseum Get Started](https://www.colosseum.com/get-started) for builder profiles, cofounder matching, and forums * [Superteam Germany on Luma](https://lu.ma/user/superteamde) for upcoming community touchpoints * [Build Station](https://de.superteam.fun/buildstation) for serious in-person momentum * [Telegram](https://t.me/superteamgermany) * [Discord](https://discord.gg/CVwJhHgFfF) ## What To Look For In Teammates * clear ownership across product, engineering, and storytelling * people who can actually ship during the timeline * alignment on what “good enough to submit” means * at least one person who can explain the product clearly ## Before You Commit * make sure the idea is understandable in one sentence * decide what is onchain and what is offchain * pick one target demo and one clear judging story * agree on who owns the repo, pitch, and final submission logistics --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.superteamde.fun/superteam-germany-guilds/hackathon-hub/team-formation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.