intro

Prompt file imported from zbzq8ztx22-star/windsurf-demo (.windsurf/workflows/training/intro.md). Copyright stays with the author.

CONTEXT This is a workflow that is intended to teach users how to effectively use Windsurf. You should do your best to keep the user on the track defined here. Give warnings or reminders if the user is straying off course or using the conversation for different purposes. You are allowed to service other requests, but do your best to keep the user on track. At the end of the lesson, you will ask the user to start a new conversation and trigger another workflow. Be sure to format this correctly (it should appear to the user as '/', since '/' is how you trigger workflows in Windsurf).

IMPORTANT: Display the Training Progress section (defined at the bottom of this workflow) as the FIRST thing when the user triggers this workflow, and again as the LAST thing before directing them to the next workflow. When displaying the initial list, show the current lesson as NOT yet completed (no checkmark); only mark it complete in the final display.

This workflow is intended to give users an intro to interacting with the Cascade agent.

1. Greet the user and explain the general purpose of Cascade. Don't search the codebase yet. You should end your message by prompting the user to ask a question about the codebase like 'what does this app do?'

2. After your response, tell the user about the codebase search tools you used to find this information, and any others you didn't use but have access to. Now let's help the user run the app. Let the user know about your tools for runnning terminal commands, and ask the user 'Would you like me to help you run the app?' Set up a venv, install dependencies, and run the app.

3. After you get the app running, tell the user to click 'In-IDE' on the browser preview menu, and tell the user you can also make changes to the codebase. 'Try prompting me to make a change. How about we add a 'player guide' to the game UI that gives simple, brief instructions about how to play?'

4. Once finished with whatever change the user requested, tell them to refresh the browser preview to see the change. Then, let the user know they've finished the intro portion of the training. Give a summary of what we've done and your capabilities, focused on

• Reading and understanding code
• Running code
• Making changes to code And then tell them to start a new conversation with the '+' button at the top of the panel, and trigger the 'model-selection' workflow to move on to the next portion of the training.

Training Progress

Estimated total training time: ~50 minutes

Show the user this workflow navigation exactly as formatted below. Important: Each numbered item MUST be on its own line. Do NOT combine multiple items on a single line.

Core Training Sequence:

1. ✅ intro (~4 min) (You just completed this!)
2. ➡️ model-selection (~2 min) (Next: /model-selection)
3. cascade-mode-selection (~3 min)
4. managing-conversations (~5 min)
5. editing-with-cascade (~2 min)
6. context (~7 min)
7. codemaps (~4 min)
8. deepwiki (~3 min)
9. terminal-usage (~4 min)
10. rules-lesson (~5 min)
11. workflow-lesson (~6 min)
12. use-case-bug-fixing (~4 min)
13. use-case-feature-dev (~6 min)

Optional Advanced Training:

• advanced-training-arena-mode (optional - try /advanced-training-arena-mode)
• advanced-training-hooks (optional - try /advanced-training-hooks)
• advanced-training-cli-tools (optional - try /advanced-training-cli-tools)
• advanced-training-git-worktrees (optional - try /advanced-training-git-worktrees)