# Shared Files & Assets
This page explains **what is included when files are shared**, **what is shared separate**, and **why things are structured this way**.
The goal is to make sure you always know **what you get**, **what you don’t**, and **how everything fits together** when following examples from this documentation.
***
### The main idea
Whenever I share an example, I try to give you **everything you need to explore, understand, and reuse it** — without hiding dependencies or requiring additional setup where it’s not necessary.
At the same time, some elements are intentionally kept **separate**, either because they cannot be embedded or because separating them makes things clearer and more flexible.
***
### **.f3z** files — the core of shared examples
An **.f3z file** acts like a **self-contained package** and can include:
* **3D geometry** of the part to be milled
* **Additional helper geometry**, such as subplates, screws, or other fixtures
* **Tools** used in the CAM project (document tools)
* **CAM setups and operations inlcuding toolpaths**
When you open a shared **.f3z**, you already have a **complete, working CAM project** that you can inspect, simulate, and learn from.
{% hint style="info" %}
The only part that may not be included automatically is the **machine file used for machine simulation**.\
If the machine is not linked automatically, it can be re-linked manually.\
Installing the shared machine files provided in this documentation **before** opening .f3z CAM examples increases the chance that Fusion can link the correct machine automatically.
{% endhint %}
***
### Why machine simulation is shared separately
Machine simulation definitions are **not embedded in .f3z files** in Autodesk Fusion.
Because of this, machine models and simulation setups must be provided as **separate downloads**.
This separation follows the **intended workflow in Fusion** and allows machine definitions to be reused across multiple projects.
***
### Tools inside files vs tool libraries
There are two ways tools appear in shared examples.
Tools used in CAM setups are stored as **document tools** inside the .f3z file.\
This is **how Fusion is intended to work**, and it ensures that:
* nothing breaks when you open the file
* feeds, speeds, and tool geometry are preserved
* examples remain fully self-contained
You can always **inspect and run the example** without importing any external tool library.
***
### Tool libraries
In addition to document tools, a **separate tool library** is provided.\
I will continue to **expand and refine this library over time** as more examples are added.
This library:
* contains **selected and tested tools**
* **grows gradually** alongside the documentation
The purpose of this library is **convenience, not dependency**.
{% hint style="info" %}
Think of this library as a **tool drawer**:\
a growing collection of tools that saves you the effort of **creating and configuring tools manually** in your own tool library.
The tools in this library are **tested on the Snapmaker Artisan** and are the **same tools I use in my own projects**.
Tool definitions include things like **geometry, RPM, and feeds**, which tend to be **consistent and reusable** — even across different CAM strategies and materials.
{% endhint %}
---
# 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://miwicnc.gitbook.io/miwicnc/software-and-cam-setup/shared-files-and-assets.md?ask=
```
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.