> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/tips-and-tricks/best-practices.md).

# Best Practices

***

### How can I get the most out of Maker?

* Start with **clear, concise prompts**—describe exactly what you want (elements, layout, behavior).
* **Iterate quickly**: refine your prompt based on the AI’s response.

***

### How do I optimize my prompts for better results?

* **Provide context**: Include relevant details, examples, or guidelines to help Maker understand your intent and generate more accurate results.
* **Use lists** (bulleted/numbered) to ask for multiple items or steps. Breaking complex requests into smaller, manageable parts often yields more precise answers.
* **Scope your request**: specify sections or components to modify (e.g. “Only update button”).

***

### Can I use Maker for collaboration?

Currently, our tool is designed for one user at a time per active project. For collaborative efforts, we recommend coordinating access among team member and the following:

* **Share live preview URLs** with teammates for feedback.
* **Remix** a project to let others iterate on their own copy without affecting your main build.
* **Duplicate** projects to manage different versions.

***

### How can I integrate feedback to improve future outputs?

* **Review response r**egularly, review the tool’s responses and adjust your prompts based on what works.
* **Documenting** successful strategies can help create a reference for future interactions, leading to consistent improvements over time.
* **Adjust and re-run** prompts when requirements change or edge cases arise.

***

### Can Maker support multi-step workflows?

Yes—chain prompts in the same chat session. Use one prompt to scaffold, then follow up to add features, tweak styles, or handle errors without starting over.

***

### Where can I find additional resources and tips?

* **Documentation Portal**: in-depth guides and examples.
* **Community Forums**: share prompts, discover use cases, ask questions.
* [**Support & Contact**](/community/support-and-contact.md): live chat and email support for personalized assistance.

***


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.maker.co/tips-and-tricks/best-practices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
