> ## Documentation Index
> Fetch the complete documentation index at: https://player-zero-drop-coordinator-docs-updates.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Prompting Basics

> Getting value out of PlayerZero is closely linked to the quality of prompts that are used to talk to your code and data.

## PlayerZero prompting basics

* **Be specific and detailed** – The more context you provide, the better the AI can understand and respond. Include relevant details, links, or examples when possible.
* **Start with a clear “kickoff” question** – Use your first question to set the direction. This helps the AI frame the context window and stay focused on your objective.
* **Embrace follow-ups as part of the process** – You don’t need to get everything perfect upfront. Think of prompting as a back-and-forth—refine and redirect as needed.
* **Assign tasks like you would with a teammate**
  – Approach PlayerZero as if you’re delegating a job. Be clear about what you want done, and give it the same guidance you’d give a human peer.
* **Use complete thoughts and full sentences** – This helps reduce ambiguity and ensures your intent is understood the first time.
* **Have a goal before you start** – Whether you’re trying to debug an issue, summarize internal context, or explore part of the codebase—know what you’re aiming to accomplish so the AI can guide you there faster.

## Great prompts ask for clear outputs by linking specific concepts together

**Sample Prompts:**

* "Tell me different actions users can take when managing invoices and explain how different user roles change what they’re allowed to do."
* "I'm getting this error **\[Paste in Error]**. Show me functions that are linked to this error and summarize the impact this has on the user."

## Get Started with Your Role

Choose your role below to discover how PlayerZero AI Chat can accelerate your specific workflow and multiply your impact:

<CardGroup cols={2}>
  <Card title="Frontend Developer" icon="computer" href="/user-guides/prompting-tips-and-tricks#frontend-developer">
    Find reusable components, optimize user experience, debug frontend issues and more.
  </Card>

  <Card title="Backend Engineer" icon="code" href="/user-guides/prompting-tips-and-tricks#backend-engineer">
    Map service dependencies, optimize performance, debug distributed systems and more.
  </Card>

  <Card title="Support" icon="heart" href="/user-guides/prompting-tips-and-tricks#support">
    Translate user problems, find solutions, prepare technical escalations and more.
  </Card>

  <Card title="Data Analyst" icon="folders" href="/user-guides/prompting-tips-and-tricks#data-analyst">
    Understand data models, trace business calculations, ensure data integrity and more.
  </Card>

  <Card title="QA Engineer" icon="list" href="/user-guides/prompting-tips-and-tricks#qa-engineer">
    Design comprehensive tests, identify edge cases, and ensure system quality.
  </Card>

  <Card title="Business Analyst" icon="briefcase" href="/user-guides/prompting-tips-and-tricks#business-analyst">
    Map architecture, trace business rules to code, and accelerate domain understanding.
  </Card>
</CardGroup>