> 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/programs-and-events/dev-guild.md). # Dev Guild Builder-focused sessions, technical exchange, and developer support inside Superteam Germany. Dev Guild is the builder-first side of Superteam Germany. It exists to help developers go from “I want to build on Solana” to actually shipping things with the right support, people, and resource stack around them. The format is a developer-heavy livestream and podcast-style series that runs live on YouTube and X. We regularly invite protocols, builders, and ecosystem teams to go deep on their stack and show how to build with it in practice. ## What You Can Expect * technical sessions and workshops * practical discussion around tools, infra, and implementation choices * support from other builders in the community * a place to ask questions and find collaborators ## Best For * developers learning Solana * hackathon teams that need support * builders evaluating starter kits and tooling * people looking for technical peers in Germany ## Where To Follow * [Event Calendar on Luma](https://lu.ma/user/superteamde) * [YouTube](https://www.youtube.com/@SuperteamDE) * [X / Twitter](https://x.com/SuperteamDE) * [Telegram](https://t.me/superteamgermany) * [Website](https://de.superteam.fun/) For previous guild notes, resource lists, and older session archives, use the [Developer Guild archive](/superteam-germany-guilds/archive/archive.md). --- # 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/programs-and-events/dev-guild.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.