# Rule Books

<figure><img src="https://2684022488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOFDKnFMEMmJjoclGx9Hr%2Fuploads%2ForDKHGlDUuMroBddgffi%2Fimage.png?alt=media&#x26;token=81f4b1c8-31e6-4ef7-94d4-9d2100c2ce6d" alt=""><figcaption></figcaption></figure>

Rule Books are how you teach Stakpak agents to follow your way of doing things. Think of them as smart, markdown based SOPs (standard operating procedures), whether it’s how to deploy to production, upgrade infrastructure, or tag resources correctly. \
\
Stakpak uses Rule Books to make decisions that align with your team’s standards, not just generic best practices.

There are two types of rule books:

* **Official Rule Books**\
  They are created by the Stakpak team, and they cover common workflows like Dockerization, infrastructure software upgrades, and cloud deployments. They follow industry best practices and are ready to use out of the box.
  * [dockerization](rule-books/dockerization "mention")
  * [infrastructure-cost-estimation](rule-books/infrastructure-cost-estimation "mention")
  * [infrastructure-software-upgrades](rule-books/infrastructure-software-upgrades "mention")
  * [simple-deployment-on-vm](rule-books/simple-deployment-on-vm "mention")
* **Your Rule Books**\
  Your custom Rule Books define how _your_ team works. From deployment procedures to incident response, Stakpak will follow them step-by-step, just like a teammate would

{% hint style="info" %}
**Note:**

* You can view and create your rule books at [stakpak.dev](https://stakpak.dev/)
* You can disable the official rule books by opening your terminal and writing stakpak `--disable-official-rulebooks`&#x20;
{% endhint %}

Now, let's take a look at the Official Rule Books in more detail

