Frequently Asked Questions

At minimum, you need: (1) A terminal/command line, (2) Git for version control, (3) Node.js for running JavaScript, (4) An IDE like VS Code or Cursor, and (5) Claude Code or another AI coding tool. Our Getting Started track walks you through each of these step-by-step.

No, Docker is optional. It's useful for professional development (isolation, reproducibility) but not required to get started. The Vibecoding track works without Docker.

For beginners: Start with PowerShell - it works for most basic tasks. For professional development: Install WSL2 (Windows Subsystem for Linux) - it gives you a full Linux environment and better compatibility with development tools. Our guides cover both approaches.

Both work great! VS Code is free, widely used, and has excellent extensions. Cursor is VS Code-based but has built-in AI features. If you're focused on AI-assisted coding, Cursor may be slightly more convenient. Otherwise, VS Code with GitHub Copilot or Claude extensions works perfectly.

Vibecoding is a casual, exploratory approach to AI-assisted coding. Instead of planning everything upfront, you describe what you want in plain English, let the AI generate code, review it, and iterate. It's great for learning, prototyping, and personal projects.

It's safe IF you follow good practices: (1) Always review AI-generated code before running it, (2) Use Git so you can undo changes, (3) Don't give AI access to production systems, (4) Never commit secrets. The AI is a tool - you're still responsible for what it produces.

This is called "spiraling" - it happens when you keep adding features or fixes in the same conversation. Solutions: (1) Start fresh conversations for new problems, (2) Be explicit about constraints ("keep it simple"), (3) Ask for the minimal solution, (4) Don't be afraid to reject suggestions and try again.

This flag tells Claude Code to automatically approve file changes and command execution without asking. Use it ONLY in: (1) Docker containers where changes are isolated, (2) CI/CD pipelines, (3) Throwaway development environments. NEVER use it on your main machine or with access to sensitive files.

Create a .claude/settings.json file in your project root. You can also create an AGENTS.md file with instructions for how AI should behave in your codebase. The Claude Code Advanced track covers configuration in depth.

MCP (Model Context Protocol) is a standard for connecting AI to external tools and data sources. You DON'T need it for basic coding, but it's useful for: (1) Accessing databases, (2) Connecting to APIs, (3) Building custom tools for specific workflows.

For most Next.js apps, Vercel is the easiest choice - it's made by the Next.js team and offers zero-config deployment. Alternatives: Railway, Render, or AWS Amplify for more control. For containers: AWS ECS, Google Cloud Run, or DigitalOcean App Platform.

Never commit secrets to Git! Use: (1) .env files locally (add .env to .gitignore), (2) Your hosting provider's environment variable settings for production, (3) A .env.example file with placeholder values to document what's needed.

Yes! Capacitor lets you wrap a web app (HTML/CSS/JavaScript) into native iOS and Android apps. You get access to native features like camera, GPS, and push notifications through plugins. Our Capacitor track walks you through the entire process.

Yes, you need a Mac with Xcode to build and test iOS apps. This is an Apple requirement, not a Capacitor limitation. You can still develop the web portion on any OS and test on Android, but final iOS builds require macOS.

Phaser is great for 2D browser games: platformers, puzzle games, shooters, RPGs, card games, and more. Games run directly in the browser - no downloads for users. You can also wrap Phaser games in Capacitor for mobile app stores.

Basic math helps, but Phaser handles most of the hard stuff. The built-in physics engines (Arcade, Matter.js) calculate collisions, gravity, and movement for you. You just configure properties like speed, bounce, and gravity values.