Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.prisme.ai/llms.txt

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

The prismeai/prismeai-templates repository hosts a growing set of ready-to-import workspace templates. Each folder is a working DSUL workspace built around one clear use case, so you can study the pattern, fork it, or use it as a starting point for your own project. Examples currently in the repo include a stateless LLM call from a form and a chat with a configurable agent. Browse the repository README for the full, up-to-date list — that’s where new templates land first.

​
When to use a template

A template is the fastest way to:
  • See an end-to-end pattern (workspace config → automations → page) in a few dozen lines of YAML.
  • Decide which client app fits your use case before you write any of your own.
  • Ship a working internal tool by tweaking instructions, prompts, or page copy rather than building from scratch.
If you’re hesitating between client apps, the README summarizes the trade-offs (LLM App for stateless calls; Agent Factory App for stateful, persona-driven agents).

​
How to import a template

  1. Get the template folder. Clone prismeai/prismeai-templates or download just the folder you want.
  2. Zip the template folder. Create a .zip whose root contains the template’s files directly (index.yml, automations/, pages/, etc.). Don’t zip the whole repository, and don’t wrap the files in an extra parent folder.
  3. Import the zip. Two options:
    • In Studio, open Workspaces → Import and drop in the zip.
    • Or POST the zip to /v2/workspaces/import — see the Workspaces API reference.
  4. Open the imported workspace and follow the setup instructions in that template’s own README.md (each folder has one). It walks through getting any required API key, configuring the client app, and any one-time provisioning.

​
Anatomy

Every template follows the same shape, so once you’ve read one you can navigate any of them: 
<template>/
├── README.md                    # setup steps and how-it-works
├── index.yml                    # workspace metadata + config schema
├── security.yml                 # default RBAC
├── imports/
│   └── <App>.yml                # the client app instance (apiKey left empty)
├── automations/
│   ├── loadPage.yml             # page init — exposes session state
│   └── <action>.yml             # event listener that calls the client app
└── pages/
    └── index.yml                # the page itself: intro + form + result panel
The page → automation contract is the same in every template:
  • The form fires a custom event on submit.
  • An event-listener automation calls the client app, writes the result to session.<key>, and emits a “ready” event.
  • The page’s updateOn: re-runs loadPage, which re-reads session.<key> and refreshes the result block.

​
Contributing a template

The repository accepts new templates that follow the same minimal, single-purpose shape. See the contributor section of the repository README for the conventions and review checklist.