Skip to content

Learning Paths

You could learn AI-assisted development by trial and error, picking things up as you go. Or you could follow a structured path that takes you from “installed the tool” to “shipping production code faster than anyone on your team” in a few weeks. These paths are organized by skill level and by tool, so you can pick exactly the journey that fits.

  • A clear week-by-week plan for your chosen tool and skill level
  • Concrete milestones to measure your progress
  • Practical exercises that use real-world patterns, not toy examples
  • A checklist you can track to confirm you have actually learned each skill

Beginner

New to AI-assisted development. You can code but have never used Cursor, Claude Code, or Codex seriously.

Duration: Week 1-2 Goal: Ship your first AI-assisted feature with confidence

Intermediate

You have used one of the tools for basic tasks. Now you want to go deeper — MCP servers, custom commands, multi-file workflows, cost optimization.

Duration: Week 3-4 Goal: Build a professional workflow that handles any daily coding task

Expert

You are productive with the tools. Now you want enterprise-scale patterns, team enablement, CI/CD integration, and advanced agentic workflows.

Duration: Month 2+ Goal: Lead AI-assisted development adoption for a team or organization


The goal is simple: go from zero to shipping a real feature with AI assistance. Every day has a specific focus and a hands-on exercise.

Day 1-2: Setup and First Interaction

  • Install Cursor and import your VS Code settings
  • Learn the three modes: Ask (read-only), Agent (autonomous), and Inline Edit (Cmd/Ctrl+K)
  • Practice: Open an existing project and ask “Explain the architecture of this project” in Ask mode

Day 3-4: Context and Navigation

  • Master @ symbols: @file, @folder, @codebase, @web
  • Learn Tab autocomplete: accept with Tab, partial accept with Cmd/Ctrl+Right
  • Practice: Use @codebase to find a function, then use Agent mode to add error handling to it

Day 5-7: First Feature

  • Use the PRD-to-Plan-to-Todo methodology: write a brief spec, ask Agent to plan, then execute
  • Practice: Build a REST API endpoint with input validation, error handling, and a test — entirely through Agent mode

Day 8-9: Testing and Debugging

  • Ask Agent to write tests for existing code. Review what it generates.
  • Debug a failing test by pasting the error into chat

Day 10-11: Git Integration

  • Use Agent to create branches, write commit messages, and resolve merge conflicts
  • Practice: Make a feature branch, implement a change, and create a PR description

Day 12-14: Configuration

  • Create your first .cursor/rules/ file with project-specific guidelines
  • Set up one MCP server (start with Context7 for documentation)
  • Practice: Build a complete small feature using everything you have learned
  • ☐ Completed tool installation and initial configuration
  • ☐ Used the AI to explore and understand an existing codebase
  • ☐ Built at least one feature entirely with AI assistance
  • ☐ Written AI-assisted tests
  • ☐ Managed Git operations through the AI
  • ☐ Created project-specific configuration (rules, CLAUDE.md, or AGENTS.md)
  • ☐ Installed and used one MCP server

You can use the tool for basic tasks. Now you learn the workflows that make you genuinely faster than coding without AI.

Day 15-16: Deep Agent Mastery

  • Use Max mode for complex multi-file refactors
  • Master checkpoints: revert bad changes, try alternative approaches
  • Practice: Refactor a module from callback-based to async/await across multiple files

Day 17-18: Custom Configuration

  • Create glob-based rules in .cursor/rules/ (auto-attached by file type)
  • Set up subagents for specialized tasks (testing, documentation)
  • Practice: Create a “test writer” subagent and a “documentation” subagent

Day 19-21: MCP and Skills Mastery

  • Install 3-5 MCP servers: Context7, GitHub, Postgres/database, Puppeteer
  • Install 2-3 Agent Skills from Skills.sh
  • Practice: Build a feature that uses database queries via MCP and browser testing via Puppeteer

Day 22-23: Code Review and Collaboration

  • Set up BugBot for automated PR reviews
  • Use Background Agent for long-running tasks
  • Practice: Set up a complete code review pipeline

Day 24-25: Cost Optimization

  • Monitor usage with Settings > Subscription > Usage
  • Learn model routing: Opus 4.6 for architecture, Composer 1 for speed, Sonnet 4.5 for budget
  • Practice: Complete a full day of work while tracking cost per task

Day 26-28: Capstone

  • Build a full-stack feature using every technique learned
  • Use multiple models for different phases
  • Document your workflow for team adoption
  • ☐ Used extended reasoning modes effectively
  • ☐ Created custom commands or subagents
  • ☐ Configured hooks or automation pipelines
  • ☐ Installed and used 3+ MCP servers
  • ☐ Installed Agent Skills from Skills.sh
  • ☐ Optimized model selection for cost/performance
  • ☐ Completed a multi-file refactor or feature with full test coverage
  • ☐ Integrated AI into code review workflow

You are productive. Now you learn patterns for enterprise-scale development, team leadership, and advanced agentic workflows.

  • Large codebase management: Strategies for 100K+ line projects. Scoped indexing, targeted @ references, .cursorignore optimization
  • Multi-agent coordination: Run 8 parallel agents. Use subagent composition for complex feature branches
  • Custom MCP development: Build an MCP server for your internal tools
  • Practice: Refactor a legacy module in a large codebase without breaking anything
  • Team configuration: Standardized .cursor/rules/ templates for your team
  • BugBot and review pipelines: Organization-wide automated code review
  • Training program: Create an onboarding guide for your team
  • ROI measurement: Track productivity metrics and cost per developer
  • Practice: Design and implement a team AI workflow from scratch
  • ☐ Managed a 100K+ line project with AI assistance
  • ☐ Built or contributed to a custom MCP server
  • ☐ Integrated AI tools into CI/CD pipelines
  • ☐ Created team-wide configuration standards
  • ☐ Trained 3+ developers on AI-assisted workflows
  • ☐ Measured and achieved positive ROI on AI tooling
  • ☐ Designed an automation strategy for a team or organization

Focus: UI/UX development with AI

  1. Component generation from design specs and wireframes
  2. Design system integration and consistency enforcement
  3. Responsive layout implementation across breakpoints
  4. Accessibility compliance (WCAG) with AI-assisted auditing
  5. Performance optimization (Core Web Vitals, bundle size)

Focus: Server-side and infrastructure

  1. API design from OpenAPI specs with AI generation
  2. Database schema design and migration planning
  3. Microservices patterns and inter-service communication
  4. Security best practices (auth, input validation, rate limiting)
  5. Performance profiling and optimization

Focus: Infrastructure and automation

  1. Infrastructure as Code with AI assistance (Terraform, Pulumi)
  2. CI/CD pipeline design and optimization
  3. Container orchestration and Kubernetes manifests
  4. Monitoring and alerting setup
  5. Incident response runbooks and automation

Use these questions to assess your current level:

Beginner — Can you answer “yes” to all of these?

  • I can install and configure the tool
  • I can use the AI to explain code and answer questions
  • I can build a feature with AI assistance from start to finish
  • I can write tests with AI help

Intermediate — Can you answer “yes” to all of these?

  • I use multiple models strategically based on task complexity
  • I have custom commands, rules, or configuration that save me time daily
  • I use MCP servers for at least one workflow
  • I can manage my context window and costs effectively

Expert — Can you answer “yes” to all of these?

  • I have integrated AI tools into my team’s development pipeline
  • I have built or customized MCP servers for my team’s needs
  • I can measure the ROI of AI tooling on my team’s productivity
  • I can train other developers to use these tools effectively

After completing your path:

  1. Share your experience — Write about what worked and what did not
  2. Contribute back — Create custom commands, MCP servers, or Agent Skills
  3. Stay current — The tools evolve weekly. Check the Updates page
  4. Help others — Mentor developers starting their own learning journey
  5. Experiment — Try the other tools. Many expert developers use all three