> For the complete documentation index, see [llms.txt](https://docs.signcod.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.signcod.com/introduction.md). # Introduction The Official **Sign** Documentation This guide provides all the necessary steps to install [**Sign**](https://siincods.com/) **products** on your PC with the best possible setup. We've included everything you need to ensure a seamless experience and address any issues you might encounter during the process. ### **Important: Setup Video** To make it even easier, we've created a detailed tutorial video. Click on the link below to watch it:\ [Watch the setup video](https://youtu.be/EZz0FTJBxAM) *** Follow the steps mentioned in this guide or in the video to ensure everything runs smoothly. If you encounter any issues, feel free to open a ticket on our [Discord server](https://discord.gg/siin). --- # 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.signcod.com/introduction.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.