docs/user-guide/project_tools/usage-build-shot-core.md

@@ -24,8 +24,16 @@ To match Assets File to the casting breakdown on the Kitsu server, we need to ta
     - **Collecton**  is set to the Asset's parent collection.
     - Run the **Set Kitsu Asset** operator to send the current filepath and selected collection to the Kitsu Server. 
 
-You should now see the filepath and collection under the Asset's Metadata on the Kitsu Server.
 
+![Set Kitsu Asset](/media/pipeline-overview/shot-production/kitsu_set_asset.jpg)
+
+If you are using the Asset Pipeline, the latest publish file will be prompted to confirm using the latest Publish as the Asset target. 
+
+![Publish Asset Pipeline with Set Kitsu Asset](/media/pipeline-overview/shot-production/kitsu_asset_with_asset_pipeline.jpg)
+
+You should now see the filepath and collection under the Asset's Metadata on the Kitsu.
+
+![Kitsu Asset Metadata](/media/pipeline-overview/shot-production/kitsu_asset_metadata.jpg)
 ## Building your First Shot
 Before building your first shot, you will need to customize your production's Shot Builder hooks. Inside your production’s `assets/scripts/shot-builder` directory the Shot Builder hook file should be stored, based on the [example](https://projects.blender.org/studio/blender-studio-pipeline/src/branch/main/scripts-blender/addons/blender_kitsu/shot_builder/hook_examples) included in the Add-On. This file can be automatically created at the correct directory using an operator in the **Blender Kitsu** Add-On preferences. Hooks are used to extend the functionality of the shot builder, and can be customized on a per project basis.