Playground Rules

The playground/ directory at the project root contains ad-hoc scripts for manual testing, experimentation, and prototyping. These scripts are not part of the production codebase or the automated test suite.

Path

<project_root>/playground/

Running playground scripts

Playground scripts import from the SDK, so they must be run from the sdk/ directory with uv:

cd sdk &#x26;&#x26; uv run python ../playground/&#x3C;script_name>.py

Guidelines

Each script should have a docstring at the top explaining what it does, any prerequisites (e.g. a running backend or proxy), and how to run it.
Playground scripts may hardcode local URLs, API keys, and test data — they are not meant for production use.
Do not add playground scripts to the automated test suite.
Keep scripts self-contained: prefer inline configuration over shared state between scripts.

Playground Rules

Path

<project_root>/playground/

Running playground scripts

Playground scripts import from the SDK, so they must be run from the sdk/ directory with uv:

cd sdk &#x26;&#x26; uv run python ../playground/&#x3C;script_name>.py

Guidelines

Each script should have a docstring at the top explaining what it does, any prerequisites (e.g. a running backend or proxy), and how to run it.
Playground scripts may hardcode local URLs, API keys, and test data — they are not meant for production use.
Do not add playground scripts to the automated test suite.
Keep scripts self-contained: prefer inline configuration over shared state between scripts.

Playground.mdc

Playground Rules

Path

Running playground scripts

Guidelines

Related Skills

<h1 align="center">

Frontend Typescript Linting.mdc

2. Apply Deepthink Protocol (reason about dependencies

Playground Rules

Path

Running playground scripts

Guidelines