Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ai-stats.phaseo.app/llms.txt

Use this file to discover all available pages before exploring further.

Use this page when you want to hand a coding agent one concrete prompt that produces a small, working app shape instead of a vague integration plan.
These prompts are written to be outcome-focused and implementation-specific so they work better in Cursor, Claude Code, Codex, and similar tools.

​
How to use these prompts

1

Pick the integration surface

Choose the prompt that matches how you want the app to call AI Stats:
  • raw HTTP
  • one official SDK
  • Vercel AI SDK
  • Agent SDK
2

Replace the bracketed variables

Fill in values like [APP IDEA], [FRAMEWORK], [MODEL], and [LANGUAGE] before you paste the prompt into your coding agent.
3

Ask for verification, not just code

Keep the verification lines in the prompt. They force the agent to report what it actually ran, what it assumed, and what still needs manual setup.

​
Prompt packs

Build a small app that uses raw HTTP against AI Stats instead of an SDK.

CursorOpen in Cursor

Build a mini app on the TypeScript SDK with a small, inspectable integration.

CursorOpen in Cursor

Build a small Python app or service using the official Python SDK.

CursorOpen in Cursor

Build a small app using AI Stats through the Vercel AI SDK.

CursorOpen in Cursor

Build a small app with the AI Stats Agent SDK and one bounded tool loop.

CursorOpen in Cursor

​
How to make the prompts work better

  • Replace [APP IDEA] with one narrow user job, not a broad product pitch.
  • Replace [MODEL] with the exact model id you want the agent to use.
  • Say whether the output should be free text, strict JSON, chat, or one generated asset.
  • Mention the UI framework and deployment target when you know them.
  • Add one or two constraints that matter, such as EU-only providers, use streaming, or keep all secrets server-side.
Last modified on May 19, 2026