# User action instructions (for Cursor / agents)

When the agent asks the **user** to do something manually (especially terminal commands), every instruction must be **complete and unambiguous**.

## Required format

For each step, include **all three**:

| Part | What to include |
|------|------------------|
| **Where** | Full directory path (this project: `C:\Users\akfai\Downloads\Cursor Project\TradingBite-Platform`) |
| **When** | Why now (e.g. after saving `.env`, before opening the browser, after stopping the old server) |
| **What** | The **full** command to copy-paste — no shorthand like “run npm” without the subcommand |

## Template

```text
WHEN: [after you save .env / before testing the chart / etc.]

WHERE: C:\Users\akfai\Downloads\Cursor Project\TradingBite-Platform

RUN:
cd "C:\Users\akfai\Downloads\Cursor Project\TradingBite-Platform"
npm run dev
```

Then say what to expect (e.g. “wait for Ready” and “open the Local URL shown”).

## Rules

- Do **not** say only “run npm” or “restart the server” without `cd`, script name, and path.
- If port conflicts are possible, say **when** to stop other terminals (`Ctrl+C`) and **when** to hard-refresh the browser.
- Never ask the user to paste secrets (API tokens) into chat.
- Prefer PowerShell-friendly one block the user can paste as a unit.

## Example (OANDA chart check)

```powershell
# WHEN: After OANDA_API_TOKEN is set in .env and saved
# WHERE: TradingBite-Platform project root

cd "C:\Users\akfai\Downloads\Cursor Project\TradingBite-Platform"
npm run dev
```

**Then:** wait for `Ready`, open the **Local:** URL from that same terminal (e.g. `http://localhost:3000` or `3003`), press **Ctrl+Shift+R**.