Supported Stacks
Frameworks and languages supported by the LatentKit vibe coding prompt builder.
The vibe coding prompt builder generates tailored instructions for these stacks.
TypeScript & JavaScript
| Stack | Best for |
|---|---|
| Next.js (App Router) | Route Handlers, Server Actions, full-stack TS |
| React + Vite | SPA with a separate backend or serverless API |
| Node.js + Express (TS/JS) | REST APIs and microservices |
| JavaScript (fetch + API route) | Generic backends when no SDK is used |
Official SDK: @latentkit/sdk
Production rule: keep LATENTKIT_API_KEY in a server route, server action, API service, or serverless function. React/Vite browser code should call your own /api/chat endpoint.
Python
| Stack | Best for |
|---|---|
| FastAPI | Async APIs and modern Python services |
| Django | Batteries-included web apps and admin projects |
| Flask | Lightweight Python APIs |
Official SDK: latentkit
Production rule: use AsyncLatentKit in async frameworks such as FastAPI, validate request bodies with the framework's normal validation layer, and log exc.request_id when the SDK raises LatentKitAPIError.
PHP
| Stack | Best for |
|---|---|
| Laravel | HTTP client + service class pattern |
| Plain PHP | curl/Guzzle without a framework |
PHP integrations use REST (/v1/chat) with Guzzle or curl — there is no official PHP SDK yet.
Production rule: use Laravel's HTTP client or Guzzle from controllers/services only. Never put the raw key in Blade templates, frontend JavaScript, or public config.
What a good AI-generated integration should do
- Add one small server-side LatentKit client/service.
- Add one API route or controller action for chat.
- Validate that
messagesis an array before forwarding. - Return a safe
502or framework-native upstream error when LatentKit fails. - Log status, error code, and
X-LK-Request-IDor SDKrequest_id. - Leave provider/model selection out of code.
How to pick a stack
- Open Build with AI (Vibe Coding)
- Select your AI coding tool (Cursor, Windsurf, Claude, …)
- Select your framework & language
- Copy the generated prompt
The prompt includes install steps, handler examples, file layout, and safety rules scoped to that ecosystem.
Missing your stack?
Use Other AI tool + the closest stack, or JavaScript (fetch + API route) for generic REST integration. More stacks (NestJS, Rails, Go, Rust) can be added to the prompt catalog without changing the page structure.
Related
- Authentication — API key header format
- Error handling — what to log when AI-generated code fails