# Screen and navigation scan {% hint style="danger" %} **Update 24 October 2024:** This is now part of the Buzzy Figma plugin's 'Automarkup' feature. {% endhint %} ## Run the scan The first time you run the Buzzy plugin on a Figma design, it will prompt you to scan for screens and actions. The scan will determine which frames in the Figma page are screens, their type, and also mark up any navigation settings. If you have more than one Figma prototype ‘Flow’ defined, Buzzy will ask you to select one. ## Tweak and apply When the scan runs, you can choose to ignore screens, or change their types (for instance, a basic screen or an overlay). Click ‘Apply’ and voila, the core skeleton of your app is already marked up with Buzzy. ## Watch a video demonstration {% embed url="" %} {% hint style="info" %} **Note** we currently only run the scan the first time you run the plugin on a Figma design. Generally once people start marking up their Figma design for production with Buzzy, they’ll no longer update their Figma prototype settings to reflect any changes - meaning if we run the scan again, it’s likely to be outdated or run into conflicts. {% 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://docs.buzzy.buzz/archive/archive-stuff/screen-and-navigation-scan.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.