> For the complete documentation index, see [llms.txt](https://docs.pletor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pletor.ai/build-agents/studio/building-tips.md). # Building tips ### Building approaches We observe that our most successful users follow **one of two building approaches:** * **Input-led**: Start with your available data (e.g., image prompt, brand guidelines) → build forward by adding nodes that transform inputs into marketing assets. * **Output-led**: Start with your desired output (text, image, video) → select the right AI node → work backwards to determine what inputs you need.

Building a fashion photo agent in one minute

Below are some additional **best practices** for building custom Pletor agents: * **Start simple**: Begin with a basic workflow and add complexity gradually. * **Test as you build**: Run individual nodes and group of nodes frequently to test them in isolation and catch issues early. * **Use AI text nodes with custom instructions** to: * enhance prompts * process multiple inputs at the same time (e.g., user prompt + brand context) * stabilize outputs' quality that will serve as inputs to other nodes * Use tools like [Prompt Cowboy](https://promptcowboy.ai/) to generate **custom instructions** in a few seconds. * **Iterate on models and configuration**. Adjust node settings, try different connections, and refine your workflow until you get the results you want. The AI Studio makes experimentation fast and visual.

Playing with configurations and models

### Organizing your canvas As agents grow in complexity, a well-organized canvas saves time and prevents mistakes. #### Sticky Notes Use Sticky Note nodes to document your workflow directly on the canvas. They don't affect execution — they're purely for communication. Good uses for Sticky Notes: * Explain **why** a node chain is structured a certain way * Leave instructions for teammates who'll edit the agent * Mark sections that are work-in-progress or need review * Document which models or settings work best after testing #### Name your nodes Click any node's title to rename it. Descriptive names like "Cinematic Video" or "Fixed Prompt Instruction" make your flow readable at a glance — much better than a row of generic "Generate Image" labels. #### Group related nodes Select multiple nodes and group them to create labeled sections on your canvas (e.g., "Brand Inputs," "Video Production"). Groups make complex agents scannable, help teammates understand the flow without clicking into every node, and can be run as self‑contained steps.
--- # 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.pletor.ai/build-agents/studio/building-tips.md?ask=&goal= ``` `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.