> For the complete documentation index, see [llms.txt](https://docs.ojin.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ojin.ai/models/oris-portrait/best-practices.md). # Best practices Follow the guidance below for the best results — your reference image is the foundation of the persona, so a clean, well-framed image gives the most natural output. ## Reference image best practices * **Image content**: * Mouth should be closed, but smiles or subtle expressions are fine * The eyes should be looking directly into the camera * Keep the expression balanced — the image is used as the base for both the idle loop and speech, so avoid extreme poses * **Format**: JPEG, PNG, or WebP * **Lighting**: Even lighting with no harsh shadows * **Face Position**: The face should be clearly visible and centered * **Background**: Simple backgrounds work best * **Accessories**: Avoid sunglasses or items that obscure facial features --- # 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.ojin.ai/models/oris-portrait/best-practices.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.