> For the complete documentation index, see [llms.txt](https://support.skylum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.skylum.com/luminar-for-web/how-to-use-luminar-for-web/editing-tools/develop.md).
# Develop
Discover Luminar for Desktop's core editing tools to handle basic yet powerful adjustments with ease and efficiency.
The **Develop** section gives you precise control over the essential elements of your photo, from light and detail to color and tonal balance. Here you’ll find four tools: Light, Details, Color, and Curves.
Develop is where you make the fundamental tonal and color corrections that shape the photograph. Use it when the image is too bright or dark, highlights need to be recovered, shadows need more detail, or the color balance doesn’t match the scene you remember.
Start with the largest problem first. If the entire photo is too dark, correct the overall exposure before trying to fix individual areas. If the color looks off, adjust the white balance before adding creative color effects.
---
# 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://support.skylum.com/luminar-for-web/how-to-use-luminar-for-web/editing-tools/develop.md?ask=&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.
