> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/releases/2022/fall-22-release/asset-configuration-templates.md).
# Asset Configuration Templates
Node Queries significantly reduces the amount of effort required to setup rules for assets. Allows for:
* Searching of in-asset and referenced assets that eliminates the need to explicitly select nodes.
* Centralized location for logic that greatly reducing the number of rules that need to be created.
* Easier maintenance of existing rules.
For full details, take a look at our [Documentation Page](/platform-documentation/project-data/logic/queries/node-queries.md) on Node Queries
Previously, the **same rule** had to be created separately in every Asset you wanted to use it on.
Now using the new **Queries** tab, create searches for nodes which can then be acted upon just like any other reference within **Rules**
Use the **Query** in place of the regular **Set** reference and you are all done.
This simple setup replaces all the duplicate rules on each individual Asset. When adding new assets, it's as simple as following the existing naming convention. No more need to update implicit references on every rule.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://community.threekit.com/releases/2022/fall-22-release/asset-configuration-templates.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.