Documentation

How the studio works

Short, factual guides. Anything not implemented yet is named as such.

Getting started

Six questions calibrate the agents: what you are building, your experience, framework, preferred model, solo or team, and deployment target.

Describe the product in the dashboard composer. KREOVIAN stores the prompt and opens the project workspace.

Ask the assistant for a specification. Review purpose, pages, entities, roles and security, then approve it before generation.

Every message is persisted against the project, so context survives reloads and is shared with workspace members.

Each applied change writes a version row with the request, model and file snapshot so you can compare and restore.

Findings are graded and can block a publish. Critical findings must be resolved or explicitly accepted.

Download the project source with deployment instructions at any time — there is no lock-in.

Workspace roles are owner, admin, developer, designer, editor and viewer, enforced by database policies.