> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/tutorials/bitcoin-primer/getting-started-with-stacks/creating-our-project.md). # Creating Our Project In order to create Crowdforge, we're going to take advantage of the Hiro Platform project templates. These are starter templates with a full-stack setup with best practices already implemented. By using these templates, we'll be able to learn best practices from them and get started on the right foot. For the rest of this course, we'll be working from this template, first getting a walkthrough of the template structure itself, getting introduced to the Stacks dev tooling ecosystem along the way. Then we'll add a new feature, following the same practices as the template uses so we can see how to work with it ourselves. For a walkthrough of the templates themselves and the ideas/goals behind their design, be sure to check out the [Hiro Dev n' Tell with Leah](https://www.youtube.com/watch?v=S3fRUUgFxsA), one of the software engineers in charge of building them. {% embed url="" %} --- # 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.stacks.co/tutorials/bitcoin-primer/getting-started-with-stacks/creating-our-project.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.