> For the complete documentation index, see [llms.txt](https://docs.daisy.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daisy.so/core-tools/pods/pod-management.md).
# Managing Pods
**Keep your Pod collection organized and performing well**
As you Create more Pods, smart organization helps you find the right style quickly and maintain quality results across your creative projects.
***
## Organizing Your Pods
### Naming Best Practices
Use descriptive names that tell the story of your Pod's style. Examples like " Golden Hour" or "Cyberpunk Street" immediately convey the aesthetic, while generic names like "Pod 1", "Test Style", or "Untitled" make it difficult to identify the right Pod for your project.
***
## Pod Maintenance
### Pod Quality Management
Delete any Pods that produce inconsistent results, are no longer needed, have unclear purposes, or were just experimental tests. Keep Pods that generate consistent, high-quality results that match your training images well, work reliably with different prompts, and serve a clear creative purpose in your workflow.
### When to Recreate
Replace a Pod when results have become inconsistent over time, you have better source images available, the style has drifted from your original vision, or it was trained on poorly curated images. These situations indicate it's time to retrain with fresh, high-quality source material.
***
**Next:** Start creating with your organized Pods in [**Create with daisy →**](/core-tools/create.md) or explore [**Explore on daisy →**](/core-tools/explore.md) to discover new styles.
---
# 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.daisy.so/core-tools/pods/pod-management.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.