Prompt Formatting Guide

1. Headings

## Role
You are CloudBrowser Support Copilot...

## Concepts
### Static Entities
- Client
- Project

2. Lists

Bulleted lists (- or *)

- **Clarity**: ≤6 bullets max.
- **Scope**: Current client only.
- **Source of truth**: CloudBrowser data.

Numbered lists (1. 2. 3.)

1. Identify failing component.
2. Check related events.
3. Suggest remediation.

3. Inline Code vs Code Blocks

Inline code (`example`)

Check pod status with `kubectl describe pod`.

Code fences (```lang … ```)

{
  "summary": "Pod was OOMKilled",
  "root_cause": "Memory limit exceeded",
  "suggested_actions": ["Increase memory limit", "Check memory leaks"]
}

4. Text Emphasis

Bold (**AAA**)

**Source of truth**: Use CloudBrowser data only.

Italics (*AAA*)

Ask for *clarification* if identifiers are missing.

Combined (***AAA***)

***Never expose credentials*** in responses.

5. Blockquotes (>)

> If context is missing, reply: "Not enough data to answer."

6. Separators (---)

## Ground Rules
...

---

## Instructions
...

7. JSON Output

Return output in JSON only:
```json
{
  "summary": "Pod OOMKilled",
  "root_cause": "Container exceeded memory limit",
  "suggested_actions": ["Increase memory limit", "Check app for memory leaks"]
}

8. Example Full Prompt Structure

## Role
You are CloudBrowser Support Copilot...

## Style
- Be concise and technical.
- Prefer bullet points.
- Output JSON when requested.

## Errors
> If context is missing, reply: "Not enough data."

## Tools
- `search_incidents(query)` → search known incidents.
- `get_metrics(component)` → fetch metrics.

## Context
Logs:
```
OOMKilled: container killed due to memory limit
```
Events:
```
Pod evicted due to node pressure

9. Quick Rules Cheat Sheet

Related Documentations