Portal
Public docs

Versalist Documentation

Reference, workflows, and product guides for challenges, tools, workspace, and developer-native usage.

Read time
1 min
Word count
...
Sections
1
Read llms.txt

Start with the product map

Use the docs home and getting-started pages to understand the product model before you jump into the narrower workflows.

Open getting started

Build from the terminal

The CLI and API docs cover the terminal-native loop for browsing challenges, seeding repo context, and submitting runs without living in the browser.

Open CLI reference

Use the LLM-friendly path

When you are reading docs inside an editor or agent host, use the copy and plain-text surfaces so context stays clean and reusable.

Read llms.txt

How to use these docs well

1. Start broad

Open the overview or getting-started pages first so the narrower references land in the right product context.

2. Shift into workflow docs

Use the product and developer sections once you know whether you are browsing, building, running, or troubleshooting.

3. Stay in one loop

Use copy-for-LLM or llms.txt when you are moving docs into prompts, terminals, or editor-integrated agents.

Welcome to Versalist

Versalist combines challenge-based practice, tool discovery, learning paths, and workspace operations in one product. The docs are organized around those loops so you can go from product overview to specific execution detail without context switching into unrelated pages.

What to learn first

  1. Read Getting Started if you are new to the product.
  2. Open Challenges and Workspace if you want the core user loop.
  3. Use API, API Keys, and CLI when you are integrating Versalist into tools or agents.

Where to go next

The fastest next step for most builders is either the challenge workflow if you want to practice against real tasks, or the workspace and prompt surfaces if you want to organize runs, prompts, and projects around the same account.

Next
Getting Started

Account setup, profile completion, and first steps.

Was this page helpful?

Use the quick feedback buttons so we can tighten the docs where the flow still feels unclear.

Back to Documentation