菜单
Navigate boot.dev courses for game development. Use when planning learning paths, mapping boot.dev progress to game-dev readiness, choosing which courses to prioritize, or connecting platform content to the game project. Bridges backend-focused curriculum with game dev goals.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | boot-dev-companion |
| description | Navigate boot.dev courses for game development. Use when planning learning paths, mapping boot.dev progress to game-dev readiness, choosing which courses to prioritize, or connecting platform content to the game project. Bridges backend-focused curriculum with game dev goals. |
| zones | {"knowledge":60,"process":15,"constraint":10,"wisdom":15} |
boot.dev teaches you to think like a programmer. Your game needs you to think like a programmer. The overlap is the skill.
Invariant Not every boot.dev course serves the game. Know which ones do before investing weeks.
Example Learn SQL is valuable for backend careers but irrelevant to a solo game dev's first project. Learn OOP is foundational for every game engine. Prioritize OOP. //BOUNDARY: This filter applies to the game project. If the user is also building backend skills for career reasons, both tracks have value — don't dismiss career-relevant courses.
Depth
These courses directly enable game development. Prioritize them.
| Course | Game Dev Connection | Unlocks |
|---|---|---|
| Learn Coding Basics (Python) | Programming fundamentals | Everything else |
| Learn Linux | Build toolchains, shell scripting | Asset pipelines, automation |
| Learn Git | Version control | Any project work |
| Learn OOP (Python) | Entity systems, inheritance, game object hierarchies | Game architecture |
| Build an Asteroids Game (Pygame) | Game loops, sprites, collision, state management | First hands-on game project |
| Learn Functional Programming | Immutable state, pure functions | Clean game state management |
These deepen CS fundamentals that improve game code quality.
| Course | Game Dev Connection | Unlocks |
|---|---|---|
| Learn Data Structures & Algorithms | Pathfinding, spatial data, collision systems | Efficient game systems |
| Build a Maze Solver (Tkinter) | Pathfinding algorithms with visual output | Algorithm visualization skills |
| Learn Memory Management (C) | Understanding allocation, pointers | Performance optimization |
| Learn DSA 2 | Priority queues, weighted graphs, shortest paths | AI pathfinding, event systems |
Relevant to game dev but not blocking early progress.
| Course | Game Dev Connection |
|---|---|
| Build a Bookbot | Practice project (reading/parsing) |
| Build an AI Agent | AI concepts applicable to game NPCs |
| Learn Golang | Systems programming (alternative engine choice) |
| Learn Networking (planned) | Multiplayer game networking |
| Learn Discrete Math (planned) | Game physics, procedural generation |
| Learn Computer Architecture (planned) | Performance understanding |
Skip or defer unless pursuing backend career goals: HTTP clients/servers, SQL, Docker, file storage/CDNs, pub/sub architecture, Blog Aggregator, Static Site Generator, Pokedex (API client), web security, job search.
Invariant Certain boot.dev milestones unlock specific game development capabilities. Track gates, not course completion percentages.
Example After completing OOP + Asteroids, the user can start learning a game engine (Godot, Unity). Before that, engine tutorials will be frustrating because the programming concepts aren't solid. //BOUNDARY: Gates are "ready to start learning X," not "mastered X." The user will continue learning while building.
| Gate | boot.dev Milestone | What It Unlocks |
|---|---|---|
| Can Code | Coding Basics complete | Simple scripts, automation |
| Can Structure | OOP complete | Game engine tutorials make sense |
| Can Build a Game Loop | Asteroids complete | First original game prototype |
| Can Optimize | DSA + Memory Mgmt complete | Performance-aware game code |
| Can Architect | FP + DSA 2 complete | Complex game systems (ECS, state machines) |
boot.dev will not teach:
These require separate learning tracked by learning-planner. The user needs to start supplementing boot.dev with game-engine-specific learning after the "Can Structure" gate.
A productive week might look like:
| Day | Activity | Why |
|---|---|---|
| Weekday evenings | boot.dev course progress (30-60min) | Consistent skill building |
| Weekend session | Apply boot.dev concepts to game project | Reinforce by building |
| Stuck day | Training Grounds practice | Low-effort progress |
This follows learning-planner's LearnBuildCycle: learn on boot.dev, build in the game project, hit a wall, learn what the wall requires.
boot.dev progress maps to sprint-manager tickets:
Title: Complete boot.dev OOP chapters 5-8
Type: Learning
Size: M
Energy: Medium
Domain: Learning
Acceptance: Chapters complete, Training Grounds score >80% on OOP topics
When the user mentions boot.dev:
When the user is stuck on a boot.dev course:
learning-planner skill — Overall learning path structureadhd-coach skill — Energy management for learning sessionsgame-research skill — Identifying what skills are needed for the gameboot.dev teaches you to think like a programmer. The game teaches you to think like a game developer. You need both.
Declare what the system should be before writing code. Use when building new features, redesigning feature areas, or making significant changes that need a declaration of intent. Guides the declaration chain from findings through plans.
Wear the QA hat — think about quality the way a 15-year senior QA thinks. Use when building features, reviewing work, validating output, or when anything feels "done" but hasn't been proven to work. Prevents the gap between "it runs" and "it works."
Evidence-first research with mandatory citations and source evaluation. Use when gathering information for decisions, comparing approaches, investigating unknowns, or any task requiring verified evidence from multiple sources. Invoke at the START of research, not when writing up results.
Check and invoke available skills before starting work. Invoke at the start of any task to ensure relevant skills are loaded.
Effective Mermaid diagrams. Use when creating markdown documents with human audiences.
Guides effective documentation creation. Activates relevant guidance for north-star, gestalt, reference, research, design, plan, flow, findings, concepts, or process documents. Prevents cascading harm from wrong information.