# Anatomy of a Full-Stack Stacks App

Let's take a look at the code that we just pulled down from the Hiro Platform template we set up for Crowdforge.

One of the best, and underrated, ways to learn code and learn a new technology is to read well-written code. That's one of the reasons why the platform templates are so great. They are an excellent starting point for you as a developer to work from so you can build your project on a solid foundation.

Let's go through and dig into the architecture of this app so we can see how it's put together and familiarize ourselves with how Stacks apps are architected.

{% embed url="<https://www.youtube.com/watch?index=1&list=PLap8Z_BpFFPrsux49eOzCHS75RnaaOPCb&pp=iAQB&v=Vw8YaIdC_cE>" %}


---

# Agent Instructions: 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:

```
GET https://docs.stacks.co/tutorials/bitcoin-primer/getting-started-with-stacks/anatomy-of-a-full-stack-stacks-app.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
