Set up your workspace

Get a clean, consistent workspace in place before you run any prompts.

1. Create one workspace folder for this workshop and open it in your editor.
2. Add an /assets folder for outputs and a /docs folder for documentation.
3. Keep a running notes.md — every decision about an asset or flow goes there first.

Connect your AI tools

Wire up one assistant you'll use consistently across both paths.

1. Pick a single AI assistant — consistency beats variety for this work.
2. Confirm it can take pasted context: mock-ups, file trees, and captured flows.
3. Keep the Prompt Library open in a second tab so you actually reuse it.

Local repo expectations

What your repo should look like so the repo-path prompts produce good output.

1. Have the project running locally, or at least building cleanly, before you start.
2. Trim the file tree so it's pasteable — drop build artifacts and dependencies.
3. Note your 2–3 core user flows; the prompts will ask for them by name.

Capture helper & Playwright setup

Set up a lightweight way to capture real user flows for documentation.

1. Install Playwright (or your preferred browser-capture tool) in the project.
2. Write one short script per flow that walks the steps and takes screenshots.
3. Save captures into /docs so they sit next to the SOPs you'll generate.

Auth for protected routes

How to capture or document an app that sits behind a login.

1. Use a dedicated test account — never capture flows with real user credentials.
2. Have your capture script sign in first, then reuse that session for each flow.
3. Where a screenshot would expose real data, describe the gated state in words.

Using these resources after the workshop

The portal is built to stay useful — here's how to keep working from it.

1. Re-run the prompts whenever your mock-up or repo changes — they're built to repeat.
2. Copy templates into your own workspace; treat the portal as the master copy.
3. Export finished outputs into your ops system so the work lives where you work.