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
Day 1-2: Setup and First Interaction
Install Claude Code (npm install -g @anthropic-ai/claude-code)
Run claude in a project directory, authenticate, and run /init to create CLAUDE.md
Practice: Ask “Explain this project’s architecture” and review how Claude explores files
Day 3-4: Context and Commands
Learn slash commands: /help, /clear, /compact, /cost, /think
Master @ file references and the # shortcut for updating CLAUDE.md
Practice: Use Claude to find a specific function and add error handling
Day 5-7: First Feature
Use the PRD-to-Plan-to-Todo methodology: describe what you want, ask Claude to plan, then execute
Practice: Build a REST API endpoint with validation, error handling, and tests
Day 8-9: Testing and Debugging
Ask Claude to write tests, then run them and fix failures
Debug by piping error output: npm test 2>&1 | claude -p "fix these failures"
Day 10-11: Git Integration
Let Claude create branches, write commits, and generate PR descriptions
Practice: Full feature branch workflow from creation to PR
Day 12-14: Configuration
Write a comprehensive CLAUDE.md with coding standards, common commands, and architecture notes
Set up one MCP server (start with Context7)
Practice: Build a complete feature using everything learned
Day 1-2: Setup and First Interaction
Install Codex CLI (npm install -g @openai/codex) or sign up for the Codex App
Configure ~/.codex/config.toml with your API key and preferred approval mode
Create an AGENTS.md in your project root
Practice: Ask “Explain this project” and watch how Codex explores the codebase
Day 3-4: Approval Modes and Context
Learn the approval modes: on-request (asks for everything), on-failure (auto-approves, asks on errors), never (full autonomy), plus the --full-auto CLI flag
Practice file references and inline context
Practice: Use on-failure mode to add error handling to an existing function
Day 5-7: First Feature
Use PRD-to-Plan-to-Todo: write a spec, ask Codex to plan, then execute
Practice: Build a REST API endpoint with validation, tests, and documentation
Day 8-9: Testing and Debugging
Ask Codex to write tests. Review the worktree diff before merging.
Debug by describing the error and letting Codex investigate
Day 10-11: Git and Automation
Let Codex create branches, commits, and PRs
Set up your first GitHub automation: assign an issue to @codex
Day 12-14: Configuration
Write a detailed AGENTS.md with coding standards and test commands
Set up one MCP server
Practice: Build a complete feature using all learned patterns
☐ 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
Day 15-16: Deep Reasoning and Planning
Master /think, /think hard, and /ultrathink for different complexity levels
Use session management: /compact for long conversations, named sessions, session forking
Practice: Architect a microservices system using /ultrathink, then implement it
Day 17-18: Custom Configuration
Build custom slash commands in .claude/commands/ with YAML frontmatter, $ARGUMENTS, and tool restrictions
Configure hooks in .claude/settings.json for auto-linting and formatting
Practice: Create a /fix-issue command that fetches a GitHub issue and implements the fix
Day 19-21: MCP and Skills Mastery
Install 3-5 MCP servers: Context7, GitHub, database, Puppeteer
Install Agent Skills from Skills.sh
Practice: Build a database-backed API where Claude queries the DB via MCP during development
Day 22-23: Automation and CI/CD
Use headless mode (claude -p) in CI/CD pipelines for automated code review
Set up hooks for pre-commit linting and formatting
Practice: Add a CI step that runs Claude Code for automated PR review
Day 24-25: Cost Optimization
Track usage with /cost and /status
Learn when to use /compact vs /clear
Model selection: Opus 4.6 for complex tasks, Sonnet 4.5 for routine work
Practice: Complete a full workday optimizing for cost
Day 26-28: Capstone
Build a complete feature with full test coverage, documentation, and CI integration
Use multiple techniques: deep reasoning for planning, custom commands for execution, MCP for tools
Day 15-16: Cloud and Parallel Execution
Use Codex Cloud for background tasks
Run multiple parallel tasks using worktree isolation
Practice: Submit 3 related tasks simultaneously and review the diffs
Day 17-18: Automations
Set up GitHub issue automation: assign issues to @codex
Configure Slack integration for team channels
Set up a scheduled task (e.g., daily dependency update check)
Practice: Create an end-to-end automation from GitHub issue to merged PR
Day 19-21: MCP, Skills, and AGENTS.md
Write comprehensive AGENTS.md with team standards
Install MCP servers and Agent Skills
Practice: Build a feature using Codex with database MCP and automated testing
Day 22-23: Team Workflows
Set up shared AGENTS.md conventions
Configure Codex automations for your team’s GitHub organization
Practice: Onboard a teammate to the Codex workflow
Day 24-25: Cost and Performance
Monitor usage through the Codex App dashboard
Optimize task descriptions for efficient token usage
Learn when to use CLI (interactive) vs Cloud (background)
Practice: Complete a full workday tracking cost and throughput
Day 26-28: Capstone
Build a feature using Codex Cloud for implementation, CLI for review, and automations for maintenance
☐ 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
Large codebase strategies : Hierarchical CLAUDE.md files (root + subdirectory-specific). Scoped rules for different parts of the codebase
CI/CD integration : Headless Claude Code in pipelines for code review, documentation generation, and automated fixes
Custom hooks ecosystem : Build project-specific hooks for validation, security checks, and compliance
Custom MCP development : Build an MCP server for your internal APIs and databases
Practice : Set up a complete CI pipeline that uses Claude Code for automated review and fix suggestions
Team CLAUDE.md standards : Shared configuration templates with team conventions
Onboarding playbook : Step-by-step guide for new developers joining the team
Cost governance : Per-developer usage tracking and budget management
Practice : Onboard 3 developers and measure their ramp-up time
Organization-wide automations : GitHub org-level Codex automations for issue triage, PR review, and dependency management
Cloud at scale : Managing 50+ concurrent cloud tasks. Priority queues and resource allocation
Custom integrations : Building Codex-to-internal-tool bridges via MCP and webhooks
Practice : Set up organization-wide Codex automations for your GitHub org
AGENTS.md governance : Organization-wide AGENTS.md standards with team-specific overrides
Automation playbook : Document every automation pattern your team uses
Cost tracking and optimization : Dashboard for team usage, per-project cost allocation
Practice : Design and deploy a team automation strategy 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
Component generation from design specs and wireframes
Design system integration and consistency enforcement
Responsive layout implementation across breakpoints
Accessibility compliance (WCAG) with AI-assisted auditing
Performance optimization (Core Web Vitals, bundle size)
Focus: Server-side and infrastructure
API design from OpenAPI specs with AI generation
Database schema design and migration planning
Microservices patterns and inter-service communication
Security best practices (auth, input validation, rate limiting)
Performance profiling and optimization
Focus: Infrastructure and automation
Infrastructure as Code with AI assistance (Terraform, Pulumi)
CI/CD pipeline design and optimization
Container orchestration and Kubernetes manifests
Monitoring and alerting setup
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:
Share your experience — Write about what worked and what did not
Contribute back — Create custom commands, MCP servers, or Agent Skills
Stay current — The tools evolve weekly. Check the Updates page
Help others — Mentor developers starting their own learning journey
Experiment — Try the other tools. Many expert developers use all three