> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/getting-started/nimbalyst-demo-and-use-cases.md). # Nimbalyst Tutorial and Demo Videos [Download Nimbalyst](https://nimbalyst.com/download/) There are three ways to learn Nimbalyst, and they suit different moods. Watch a video to see what the app does. Open the tutorial workspace to click around in something already built. Run the guided quickstart when you want an agent to teach you by having you do real work. ## 1. Demo videos Start with the overview, then pick the walkthrough that matches your job. ### 1-minute overview The fastest look at what Nimbalyst is: agents, files, visual editors, and trackers in one workspace. {% embed url="" %} ### For product managers: idea to tracked work An onboarding revamp goes from an idea to an aligned team without anyone writing code. The agent researches the drop-off, drafts the PRD as a live document, and produces the user flow diagram and a clickable mockup beside it. One click turns the plan into tracked work on a shared board, and one more makes the document multiplayer so teammates comment in place. **1:26.** {% embed url="" %} More in the [product manager playlist](https://www.youtube.com/playlist?list=PLGm3n1OZjA5WN0-JX2Ia9b1d55vU63xKM). ### For developers: research, plan, diff, review A request for an API usage dashboard runs all the way to an approved pull request in one workspace. The first instruction is deliberately narrow, research and plan only, no code. The plan becomes an editable document with an architecture diagram and mockup inside it, every agent change shows as a diff you accept file by file, and the pull request gets reviewed in the same place. **1:13.** {% embed url="" %} More in the [developer playlist](https://www.youtube.com/playlist?list=PLGm3n1OZjA5XoEiKpcRp5f9M_HVySXDmg). The pull request review queue shown here needs Developer Mode turned on in settings. ### Longer walkthrough: product management use cases A 15-minute tour through product management workflows end to end. {% embed url="" %} ## 2. The tutorial workspace The first time you open Nimbalyst, the welcome screen asks which mode you want and offers **Start tutorial**.

The Welcome to Nimbalyst screen with Standard Mode and Developer Mode cards, role and referral questions, an optional email field, and Get started and Start tutorial buttons — Choose Standard or Developer Mode, then take the tutorial workspace or go straight to your own project.

* **Standard Mode** is a simplified interface focused on writing, editing, and AI assistance. * **Developer Mode** adds git worktrees, terminal access, and the rest of the development environment. See [Turn on/off Developer Mode](/developer-features/turn-on-off-developer-mode.md); you can switch later. * **Get started…** opens Nimbalyst against a folder you choose. **Start tutorial** creates the tutorial workspace instead. **Start tutorial** builds a small connected project called **Nimbalyst Tutorial** in your Documents folder. Nothing is set up or configured. Everything in it is a real file you can edit, break, and throw away.

The Nimbalyst Tutorial workspace, with a README listing things to try, a file tree of planning and design files, a live mockup embedded in the document, and an agent session open on the right — The tutorial workspace is a real project. The dashboard in the README is a live embed of a mockup file, not a picture of one.

The README lists things to try, and each one is a link into the workspace: * Type in the document, and try `/`, `#`, and `@`. * Ask the agent to add a summary at the top of the file, then review its red/green changes. * Shape an interface in the dashboard mockup, then ask the agent to change it. * Switch to Agents mode, look at past sessions, and click into the files they touched. * Explore a revenue spreadsheet, change assumptions in a metrics model, and follow the work into an architecture diagram. * Read a document with embedded project artifacts, turn a goal into steps with a launch checklist, and see a markdown document become a tracker item. If you skipped it during onboarding, you can start it later from **Help > Launch Tutorial**, or from **Try the interactive tutorial** on the workspace manager's welcome screen. Nimbalyst reuses the existing tutorial folder rather than making a second one, so the button reads **Open tutorial** once it exists. Delete the `Nimbalyst Tutorial` folder in your Documents folder whenever you are done with it. ## 3. The guided quickstart Learn Nimbalyst by doing your own real work in about 15 minutes, with an agent as the instructor. Product managers, founders, and designers finish with a working brief and an embedded mockup. Developers finish with a run-and-test guide, an embedded architecture diagram, and two agents running in parallel. Open a workspace in Nimbalyst, start a new chat, and paste this prompt: ``` Fetch https://raw.githubusercontent.com/nimbalyst/skills/main/skills/getting-started/quickstart.md, save it to nimbalyst-quickstart/quickstart.md in this workspace, then run it as the Nimbalyst quickstart. Wait for me at every exercise. ``` The agent saves the quickstart in your workspace, helps you choose the product or engineering track, and waits for you at each exercise. Everything it creates stays under `nimbalyst-quickstart/`, so you can remove the folder afterward if you do not want to keep the results. The [Nimbalyst quickstart on GitHub](https://github.com/nimbalyst/skills/blob/main/skills/getting-started/quickstart.md) is the source of truth. ## Setting up a team Working with other people is its own walkthrough. Sign in, create an organization and invite your team, then work together in shared trackers and shared documents while everyone's coding agents work in the same files. **2:46.** {% embed url="" %} The same seven steps in writing, with a screenshot for each: [Nimbalyst Teams: Step by Step](/team-collaboration/teams-tutorial.md). ## Use cases * [For Product Managers](https://nimbalyst.com/use-cases/product-managers/) * [For Developers](https://nimbalyst.com/use-cases/developers/) More workflows, from feature planning to bug analysis to design handoff, are on the [Nimbalyst use cases page](https://nimbalyst.com/use-cases/). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nimbalyst.com/getting-started/nimbalyst-demo-and-use-cases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.