Workspace | Versalist Documentation

Workspace hub

/workspace

The operator-facing entry route for tools, stack design, and guided execution.

Tooling surface

/workspace/tools

Manage the tools and generation flows behind your stack.

Progress route

/progress/dashboard

Track what the work is adding up to over time.

Prompt and project work

/prompt-library + /my-projects

Keep prompt systems and projects close to the rest of the workflow.

Best mental model

Think of Workspace as the layer where scattered AI work becomes an operating system.

Challenges, prompts, tools, and progress are all useful alone. Workspace matters once you want them to reinforce each other instead of living as disconnected pages you open in random order.

Open workspace

Challenge work and progress

Workspace is not separate from challenge participation. It is where active work, completed runs, learning signals, and related artifacts start to read like one coherent operating loop.

Execution history

My challenges

Keep current and completed challenge work in one place so you can see what is still active and what already produced results.

Open my challenges

Progress signals

Dashboard and quiz routes

Use the progress views to understand whether challenge work is turning into actual learning rather than isolated runs.

Open progress dashboard

Formal record

Certificates

Certificates are where the workspace history turns into something you can reference or share later.

Open certificates

Prompts, projects, and reusable context

Once you stop treating prompts or experiments as throwaway work, they need a home. The prompt and project routes are that home: a place to keep your strongest material close to the rest of your challenge and tool workflow.

Prompt Library

Study prompt structure, keep reusable prompt systems, and connect prompt work back to the tasks it supports.

Open prompt library

My prompts

Your personal prompt space is where private or saved prompt work becomes easier to revisit and refine.

Open my prompts

My projects

Projects help organize longer-running work so challenge outputs, prompt variants, and implementation notes stay connected.

Open my projects

Shareable artifacts

As the work matures, the workspace surfaces become the easiest place to assemble a usable public or semi-public record.

Open profile

Tools, stack design, and generation

Workspace also houses the tool-operator side of the product. These routes are useful when you want to describe your stack explicitly, compare provider choices, or generate a better starting configuration.

Curate

Workspace tools

Keep your tool stack visible instead of rebuilding your preferred configuration from memory.

Open workspace tools

Model

Stack design

Use the stack route when you want to represent the providers, layers, and workflow dependencies behind your setup.

Open stack

Generate

Tool generation

The generator route is helpful when you want a tighter first-pass configuration based on your current constraints.

Open tool generator

Recommended daily rhythm

The best workspace routine is simple: open the active work first, keep supporting prompts and tools nearby, and let progress or certificate routes tell you whether the work is accumulating in a useful way.

Start from active work

Open My Challenges, My Projects, or the relevant prompt detail page before browsing unrelated areas.

Open my challenges

Keep tools and prompts close

Use workspace tools and prompt routes to keep the operating context near the thing you are building.

Open workspace tools

Check progress instead of guessing

Review the progress routes periodically so you can see whether the work is turning into retained capability.

Open progress dashboard

Use Vera when you want guided flow

The Vera route is useful when you want a more guided assistant surface attached to the same workspace context.

Open workspace Vera

Projects and portfolio signals

Projects, prompts, certificates, and progress are the pieces that make your workspace feel cumulative. When they stay connected, you end up with something closer to an operating record than a pile of disconnected experiments.

Good outcome

A strong workspace tells the story of how you work, not just what you clicked.

Use the project, prompt, challenge, and certificate routes together so you can revisit the reasoning, the implementation, and the result later. That is what makes the module useful beyond the current session.