# Getting Started

JulesTools is a collection of independent Unity Editor tools. Each tool is distributed as a separate package and can be installed individually based on your project requirements. There are no shared dependencies between tools unless explicitly noted.

***

<details>

<summary>Render pipeline compatibility</summary>

The Built-in Render Pipeline is Unity's default render pipeline. It is a general-purpose render pipeline that has limited options for customization. The Universal Render Pipeline (URP) is a Scriptable Render Pipeline that is quick and easy to customize, and lets you create optimized graphics across a wide range of platforms. The High Definition Render Pipeline (HDRP) is a Scriptable Render Pipeline that lets you create cutting-edge, high-fidelity graphics on high-end platform

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th></tr></thead><tbody><tr><td><h4>Built-in</h4></td><td><i class="fa-octagon-check">:octagon-check:</i> <strong>Compatible</strong></td><td></td><td></td></tr><tr><td><h4>URP</h4></td><td><i class="fa-octagon-check">:octagon-check:</i> <strong>Compatible</strong></td><td></td><td></td></tr><tr><td><h4>HDRP</h4></td><td><i class="fa-octagon-check">:octagon-check:</i> <strong>Compatible</strong></td><td></td><td></td></tr></tbody></table>

</details>

<details>

<summary>Unity Asset Quality</summary>

Before submitting an asset to the Asset Store, publishers must ensure:

<i class="fa-octagon-check">:octagon-check:</i>  Content submitted is professionally designed and constructed. All assets are suitable for use in a development pipeline.

<i class="fa-octagon-check">:octagon-check:</i>  Packages do not throw any generic errors after setup is complete. Any errors present in the product are only those that are from caught and handled exceptions.

<i class="fa-octagon-check">:octagon-check:</i>  Submissions are no more than 6GB in size.

<i class="fa-octagon-check">:octagon-check:</i>  Submissions do not have functionality implemented to track or collect a user’s data.

<i class="fa-octagon-check">:octagon-check:</i>  The asset will be tested on the most recent publicly available version of Unity and is required to meet all of our standards in that version of Unity or whichever version(s) the content is explicitly stated to be intended for.

<i class="fa-octagon-check">:octagon-check:</i>  You can read the full Asset Store submission guidelines [here](https://assetstore.unity.com/publishing/submission-guidelines)

</details>

***

#### Available Tools

Each tool is documented with a consistent structure: Overview, Installation, Quick Start, Workflow, Technical Notes, Limitations, and FAQ.

{% content-ref url="/pages/i73g4LZQanoLj7XtSO18" %}
[Project Organizer](/julestools-docs/documentation/tools/project-organizer.md)
{% endcontent-ref %}

{% content-ref url="/pages/AD9lDCmpddI5WAY92HgG" %}
[Code Harvest](/julestools-docs/documentation/tools/code-harvest.md)
{% endcontent-ref %}

{% content-ref url="/pages/scPRmf2UHNygzfDCY7Iu" %}
[Smart Localization Lite](/julestools-docs/documentation/tools/smart-localization-lite.md)
{% endcontent-ref %}

{% content-ref url="/pages/ULmoXhthX9AEP6aH6ZSe" %}
[Smart Localization Suite](/julestools-docs/documentation/tools/smart-localization-suite.md)
{% endcontent-ref %}

{% content-ref url="/pages/lWdZgI2P4YIODQ7uazsl" %}
[Animation Path Visualizer](/julestools-docs/documentation/tools/animation-path-visualizer.md)
{% endcontent-ref %}

{% content-ref url="/pages/VS8K7lC8h5wpDPC5YvZi" %}
[Class Diagram Generator](/julestools-docs/documentation/tools/class-diagram-generator.md)
{% endcontent-ref %}

***


---

# 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://julestools.gitbook.io/julestools-docs/documentation/readme.md?ask=<question>
```

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.