> For the complete documentation index, see [llms.txt](https://smily.gitbook.io/smily-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://smily.gitbook.io/smily-docs/community.md). # Community Smily is built around its players. The community is where rooms get filled, rivalries are made, and the brand lives. There is no global messenger inside the app by design, which keeps the product dark and focused, so the community gathers on the channels below. ## Where to find us * **Website:** [smily.bet](https://smily.bet/) * **X:** [@SmilyBet](https://x.com/SmilyBet) ## Founding players Early access is opening through a founding whitelist with a limited number of seats. Founding players get in before the public and the spot comes with an edge revealed to the ones who make it. There are three ways in: be among the first to finish the application, get hand-picked on the quality of your read, or rank among the top inviters who push Smily hardest and bring real people to the table. Details and the application live on [smily.bet](https://smily.bet/). ## How the community grows the game * **Home Games.** Any player can spin up a private room and challenge their audience or run recurring rooms for a community. This is the viral engine of the product. * **Seasons.** Recurring competitive cycles with leaderboards and prestige give the community something to climb and something to defend. * **The rail.** Spectators can watch rooms, which adds atmosphere and pulls more players to the table. ## What we ask of the community Read well, play straight, and bring the people who would actually enjoy the table. The game is fair because the structure makes it fair, and the community is strongest when it is real. Quality of engagement is what builds a player base that lasts. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://smily.gitbook.io/smily-docs/community.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.