> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/tutorials/more/disabling-locksmith-for-certain-theme-files.md).

# Disabling Locksmith for certain theme files

How to tell Locksmith to completely ignore specific files in your theme

Locksmith does its work by adding its code to your theme's files. Sometimes you may want to keep Locksmith from modifying a file in particular, whether it's for a customization, or some other reason.

To support this, Locksmith has a "Liquid assets to ignore" option. Configure it like so:

1. From within the Locksmith application, click "Settings".
2. Scroll to the bottom of the screen to the "Advanced" section.
3. For each Liquid asset you'd like to have Locksmith ignore, add its filename to the "Liquid asset blacklist" box.

That will look like this:

![](https://277214568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUeGWHuijBPr8Og1Gta%2Fuploads%2FW4szboNyTl0dOYdLrDIK%2FScreen%20Shot%202022-08-02%20at%207.25.25%20PM.png?alt=media\&token=76d53a95-ec88-4a1b-b023-11985ccffa40)

{% hint style="info" %}
**Note**: Use full file names. (e.g. "sections/collection-list.liquid" or "templates/gift\_card.liquid"), and enter them **one per line**.
{% endhint %}

**Please note:** If you need to use the ignore list because Locksmith is causing unexpected problems with your theme, please let us know! Feel free to use the ignore list for any purpose, but do get in touch at <team@uselocksmith.com> if there's a bug we can help resolve. :)


---

# 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://www.locksmith.guide/tutorials/more/disabling-locksmith-for-certain-theme-files.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.