# Participant preparation

Complete this before Day 1 (about 15 minutes). Day 1 is for building, so get the installing out of the way now. If a step doesn't work, bring your laptop as-is and we'll sort it in the first few minutes.

**Running the session:** Maurice Kleine (m.kleine@waimakers.com) and Abner van den Hout (a.vandenhout@waimakers.com), Waimakers.

## 1. Install Claude (pick the route that fits you)

You don't need to be technical. If you live in chat/browser tools today, use the Desktop route.

- **Desktop app (easiest, no terminal):** Mac → [claude.ai/download](https://claude.ai/download); Windows → [claude.com/download](https://claude.com/download). Open it and use the **Code** tab for repository work.
- **Your IDE:** IntelliJ / PyCharm → install the **Claude Code** plugin from the JetBrains Marketplace (also install the CLI below); VS Code / Cursor → search "Claude Code" in Extensions.
- **Terminal (full CLI):** Mac → `curl -fsSL https://claude.ai/install.sh | bash`; Windows PowerShell → `irm https://claude.ai/install.ps1 | iex`.

New to the terminal? Use the Desktop route for now. We cover the terminal together on Day 1.

## 2. Sign in (about 2 minutes)

Oodle runs on **Claude Enterprise**. Sign in with your **Oodle single-sign-on**, the account you use for email, Microsoft and Salesforce. No keys or settings to configure. Open Claude Code (`claude`) or the Desktop app, log in when the browser opens, and you're done.

Licences are being issued this week. If yours isn't live yet, or you already set up Claude with your Oodle email and need moving onto Enterprise, bring it as-is and we'll fix it on the day.

## Access checklist

- Claude Enterprise works in the browser (sign in with your Oodle SSO).
- Claude Code is installed and authenticated. It's our main tool across the two days.
- Approved Oodle repository access works.
- You can open a terminal on your work laptop.
- You know where the Oodle AI/data policy and escalation contact live.
- You have completed the pre-programme survey and bring a charger. Mac or Windows are both fine.

*Jira and Confluence will be connected (read-only) during the sessions, so there's nothing to set up now. Claude Cowork isn't enabled for the Kickstart; we work in Claude Code (the terminal or the Desktop **Code** tab).*

## Bring one real problem

Bring a Jira issue, workflow friction, codebase question or data task that is valuable, bounded and safe to explore. Avoid production deployment, customer communication, regulated decisions, secrets, credentials and unapproved personal data.

Write down:

1. Who experiences the problem?
2. What observable pain exists today?
3. What evidence would show improvement?
4. Which source is authoritative?
5. What must the agent never do?

## Repository preparation

Use a clean branch or disposable workspace. Know the normal test command. Identify an owner who can validate business rules. Do not assume AI output is correct because it compiles.

If a check fails, write down which step broke and the exact error (leave out secrets), tell the workshop contact before Day 1, and bring a synthetic fallback task. Do not bypass access controls or use a personal account.