> For the complete documentation index, see [llms.txt](https://docs.jigx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jigx.com/building-apps-with-jigx/jigx-builder-code-editor/tips-tricks-and-shortcuts.md).

# Tips, tricks and shortcuts

Discover shortcuts and tricks that boost efficiency and maximize your output.

## Jigx Builder shortcuts

<table><thead><tr><th width="235.0390625">Shortcuts</th><th width="233.90625">Mac</th><th>Windows</th></tr></thead><tbody><tr><td>Publish all files in Jigx solution</td><td>⌘R⌘R</td><td>Alt+R Alt+R</td></tr><tr><td>Publishing an individual file is useful if multiple developers work on the same solution. You only want to publish your changes. Note index.jigx, is a shared file that people all work on, so the last one updated on the server gets published.</td><td>⌘R⌘F</td><td>Alt+R Alt+F</td></tr><tr><td>Invoke IntelliSense</td><td>Ctrl+space</td><td>Ctrl+space</td></tr><tr><td>Quick Fix</td><td>⌘+.</td><td>Ctrl+.</td></tr><tr><td></td><td>F12 or ⌘+click</td><td>F12 or Ctrl+click</td></tr><tr><td></td><td>shift+F12 F12</td><td>shift+F12 F12</td></tr><tr><td>The swagger parser function</td><td>⌘ + shift + p <code>Generate Jigx Functions</code></td><td>Ctrl + shift + p <code>Generate Jigx Functions</code></td></tr></tbody></table>

## What colors indicate in Jigx Builder

<table><thead><tr><th width="104.65625">Color</th><th>Description</th></tr></thead><tbody><tr><td>white</td><td>The file is issue-free. If connected to a Git repository, the file is committed.</td></tr><tr><td><mark style="color:red;">red</mark></td><td>The file has validation issues/errors/deprecated properties that must be fixed. The number of issues is shown by a red number on the right of the file name in the sidebar.</td></tr><tr><td><mark style="color:yellow;">yellow</mark></td><td>This means the file is connected to a Git repository and is modified; the letter M displays on the right of the file name in the sidebar. YAML is squiggled in yellow to show deprecated properties, hover over the YAML to see the expected property.</td></tr><tr><td><mark style="color:green;">green</mark></td><td>Indicates a new file has been created but not committed to the Git repository yet.</td></tr><tr><td><mark style="color:blue;">blue</mark></td><td>Indicates the active screen on the mobile device that you are debugging in the builder using Jigx Dev Tools.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jigx.com/building-apps-with-jigx/jigx-builder-code-editor/tips-tricks-and-shortcuts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
