Your First Day: Accounts, Access & Setup
Welcome to Shattered Vales Studio. This guide gets you from a new laptop to a cloned, running project, and points you to the rest of the guides in the order they're most useful. Work through it top to bottom, and ask your lead or onboarding buddy whenever something doesn't match what you see.
Step 1: Set Up Your GitHub Account
- Sign in or sign up at GitHub (opens in a new tab). Your lead will tell you whether to use an existing personal account or create one just for work.
- Add and verify your studio email under Settings > Emails. Commits are linked to your account by email address, so this is how your work shows up as yours.
- Fill in your profile with your real name and a photo, so teammates recognize you in reviews.
- Send your GitHub username to your lead so they can invite you to the organization.
Step 2: Turn On Two-Factor Authentication
Two-factor authentication (2FA) is required for every member of the organization. Set it up before accepting the invitation: under Settings > Password and authentication, enable 2FA with an authenticator app, and add a passkey or hardware security key as well if you have one.
Save the recovery codes in your password manager straight away. Losing both your phone and your recovery codes can lock you out of your account permanently.
Step 3: Join the Organization
Accept the invitation from the email GitHub sends you, or from your GitHub notifications. You'll be added to one or more teams, which control the repositories you can see. If a repository you need is missing, ask your lead to add you to the right team; don't ask a teammate to share their access.
Step 4: Install Your Tools
| Tool | Who needs it | How |
|---|---|---|
| Git | Everyone | Step 1 of the Daily Git Terminal Workflow |
GitHub CLI (gh) | Everyone | Steps 2 and 3 of Claude Code & GitHub CLI Setup |
| Password manager | Everyone | The studio's team vault; your lead sends the invite |
| Code editor or IDE | Developers | The one your project's README names (for example VS Code, Rider, or Visual Studio) |
| Unity Hub and the project's editor version | Game developers | Version listed in the project README |
| Git LFS | Game developers | Managing Game Assets with Git LFS |
| Claude Code | When your lead enables it | Claude Code & GitHub CLI Setup |
Step 5: Connect to GitHub with an SSH Key
An SSH key lets Git talk to GitHub securely without typing a password. If you only use one GitHub account on this machine, these commands are all you need. If you use more than one, follow Managing Multiple SSH Keys instead.
macOS
ssh-keygen -t ed25519 -C "you@shatteredvales.studio"
gh ssh-key add ~/.ssh/id_ed25519.pub --title "Studio laptop"
ssh -T git@github.com
Linux
ssh-keygen -t ed25519 -C "you@shatteredvales.studio"
gh ssh-key add ~/.ssh/id_ed25519.pub --title "Studio laptop"
ssh -T git@github.com
Windows
ssh-keygen -t ed25519 -C "you@shatteredvales.studio"
gh ssh-key add "$env:USERPROFILE\.ssh\id_ed25519.pub" --title "Studio laptop"
ssh -T git@github.com
Press Enter to accept the default file location, and set a passphrase. gh ssh-key add needs the GitHub CLI signed in first. The last command should greet you by username.
Step 6: Clone and Run Your First Project
Keep all repositories in one folder (the studio convention is ~/Source) so they're easy to find:
mkdir -p ~/Source && cd ~/Source
gh repo list Shattered-Vales-Studio --limit 50 # repositories you can access
gh repo clone Shattered-Vales-Studio/<repo>
cd <repo>
- Read the
README.mdfrom top to bottom, thenARCHITECTURE.mdif there is one. - Follow the README's Getting Started steps until the project runs and its tests pass.
- Anywhere the README was wrong, unclear, or missing a step, write it down. Fixing it is a perfect first pull request.
Step 7: Stay on Top of Notifications
GitHub notifies you about reviews requested from you, mentions, and activity on issues you're part of. Choose web or email delivery under Settings > Notifications, and use Watch on your team's main repositories. From the terminal, one command summarizes everything waiting on you:
gh status
Step 8: Read the Guides in This Order
You don't need everything on day one. This order matches when you'll need each guide:
| When | Guide |
|---|---|
| Day 1 | Git Fundamentals, then the Daily Git Terminal Workflow |
| Day 1 | LLM Prompting & AI Security (Step 5, the data rules, is mandatory) |
| Week 1 | Undoing Things Safely · Conducting Effective Code Reviews · Writing Good Issues & Using Labels |
| Week 1 | GitHub Actions & CI Basics · Repository Standards |
| Game developers, week 1 | Managing Game Assets with Git LFS |
| Month 1 | Reading History & Finding Bugs · Releases, Tags & Versioning · Submodules & Shared Packages |
| When you start using AI tools | Claude Code & GitHub CLI Setup · Using AI to Learn an Unfamiliar Codebase · Reviewing AI-Generated Code |