Boss: Workshop ready
Task pick
Which task card could you finish and test in one work session?
- "Ship Hyper Shards"
- "Make the laser sound quieter. Done when it no longer drowns out the music."
- "Improve all the enemies"
Show the answer
"Make the laser sound quieter. Done when it no longer drowns out the music."
It is one small job with a clear "done" test. "Ship Hyper Shards" is the whole goal, and "improve all the enemies" has no finish line.
Quick check
In IDE X 3.0, you can keep an agent's changes without reading the diff, because Generative AI Model Alpha always sounds sure.
- True
- False
Show the answer
False
An AI model predicts answers from patterns, so it can be confidently wrong. Read the diff, test the game, and ask it to explain anything unclear.
Prompt pick
Which prompt should you send to Generative AI Model Alpha?
- "Make Hyper Shards better"
- "In Hyper Shards, the ship slides after I let go of the key. Fix it in ship.js. I'll test by tapping left."
- "Fix everything that's wrong"
Show the answer
"In Hyper Shards, the ship slides after I let go of the key. Fix it in ship.js. I'll test by tapping left."
A good prompt says which game, what's wrong, where, and how to check. Naming one small module, ship.js, keeps the change focused.
Read the error
1kai@laptop studio % cd hyper-shrads2cd: no such file or directory: hyper-shrads
What went wrong?
- The folder name has a typo: shrads instead of shards
- Hyper Shards has a bug in ship.js
- Git deleted the folder
Show the answer
The folder name has a typo: shrads instead of shards
The error names exactly what it couldn't find: hyper-shrads. Fix the typo (or press Tab to finish the name) and cd works.
Quick check
Remy changed balance.json. Which commands save that change as a commit?
- git add balance.json, then git commit -m "Halve snail speed"
- git push, then git init
- git log, then git diff
Show the answer
git add balance.json, then git commit -m "Halve snail speed"
git add puts the change in the staging area, and git commit saves everything staged as one save point. Push uploads commits, and log and diff only look.
Quick check
End-to-end tests play the real game in a real browser, so most of Hyper Shards' tests should be end-to-end tests.
- True
- False
Show the answer
False
End-to-end tests are realistic but slow and sometimes flaky. The testing pyramid keeps most tests as fast unit and integration tests in Vitest, plus a few Playwright tests for key journeys like starting a game and saving a score.
Fix the conflict
1<<<<<<< HEAD2 "laserDamage": 3,3=======4 "laserDamage": 2,5>>>>>>> feature/new-ship
Kai merges a branch and finds this. What must happen before committing?
- Pick or combine the right value, delete all three marker lines, then test the game
- Commit straight away, Git tidies it up later
- Delete balance.json
Show the answer
Pick or combine the right value, delete all three marker lines, then test the game
Both branches changed the same line, so Git needs a human decision. Leftover markers break the JSON, so remove them all and play the game before you commit.
Review the PR
1 approval. Some checks were not successful: score.test.js failed.
Branch protection on main needs 1 approval and passing checks. What happens next?
- Fix the code on the same branch and push, then merge once the checks are green
- Merge now, one approval is enough
- Delete score.test.js so the check turns green
Show the answer
Fix the code on the same branch and push, then merge once the checks are green
The robot tester found a real bug, so the merge button stays locked. Fixing the code and pushing to the same branch reruns the checks. Deleting the test would only hide the bug.