A quick self-assessment to help you skip what you already know and start where the real learning begins.
How it works: Fork this repo, then go through each level's checklist from top to bottom. Click the checkboxes directly on GitHub to mark the skills you already have. The first level where you can't check every box is where you should start.
Can you do all of these without copy-pasting from Stack Overflow?
- Declare variables with
let/constand explain whyvaris avoided - Write
for,while, andforEachloops from memory - Select DOM elements and update their content or styles with JavaScript
- Attach event listeners to buttons, inputs, and keyboard events
- Use
if / else, ternary operators, andswitchstatements - Work with arrays:
push,pop,map,filter,find,reduce - Manipulate strings:
split,slice,includes, template literals - Use
setIntervalandsetTimeoutfor timing-based logic - Build a simple UI layout with CSS Flexbox or Grid
- Debug using
console.logand browser DevTools
All checked? You can skip Level 1 → try Level 2.
AI rule for this level: Build everything yourself — no Copilot, no ChatGPT. The struggle is the lesson.
Can you build these patterns confidently?
- Fetch data from a REST API using
fetch+async/await - Handle loading, success, and error states for API calls
- Manage application state across multiple UI components
- Build responsive layouts that work on mobile and desktop
- Use
localStorage/sessionStoragefor client-side persistence - Implement search, filter, and sort on a data set
- Create a multi-page or single-page app with client-side routing
- Work with third-party libraries (charting, maps, audio, etc.)
- Render lists dynamically and handle empty / loading states
- Structure a frontend project with clean file and folder organization
All checked? You can skip Level 2 → try Level 3.
AI rule for this level: Still no AI. You need to internalize APIs, state, and layout before outsourcing them.
Can you handle these server-side concepts?
- Set up a Node.js + Express server from scratch
- Design RESTful routes: proper verbs, status codes, resource naming
- Connect to MongoDB or PostgreSQL and perform CRUD operations
- Write middleware for logging, error handling, and authentication
- Hash passwords with bcrypt and issue/verify JWT tokens
- Validate and sanitize incoming request data
- Handle file uploads with multipart form data
- Implement rate limiting and basic security headers
- Use environment variables for configuration and secrets
- Deploy a backend to a cloud platform (Render, Railway, etc.)
All checked? You can skip Level 3 → try Level 4.
AI rule for this level: Use AI as a pair programmer — you design the architecture, AI helps with boilerplate and debugging.
Can you wire everything together end to end?
- Build a React frontend that talks to your own Express API
- Implement user registration, login, and protected routes (both sides)
- Use React hooks (
useState,useEffect,useContext) fluently - Handle CORS, proxy configuration, and environment-based API URLs
- Model data relationships in MongoDB (references or embedded docs)
- Build real-time features with WebSockets (Socket.io)
- Implement pagination, infinite scroll, or cursor-based loading
- Deploy frontend and backend separately and connect them in production
- Write clean, reusable components with proper prop/state boundaries
- Set up a CI/CD pipeline or at least automated deployments
All checked? You can skip Level 4 → try Level 5.
AI rule for this level: AI handles the repetitive parts — you own the decisions, the data flow, and the deployment.
These are the skills that separate mid-level from senior:
- Design system architecture before writing code (diagrams, trade-offs)
- Implement message queues, pub/sub, or event-driven patterns
- Work with real-time data streams (WebSockets, SSE, MQTT)
- Integrate third-party AI/ML APIs or run models locally
- Implement geospatial queries and map-based features
- Build multi-tenant systems with role-based access control
- Handle distributed state, caching (Redis), and session management
- Write database migrations and handle schema evolution
- Design for horizontal scalability and fault tolerance
- Reason about security: OWASP top 10, audit logging, encryption at rest
Can't check them all? This is where you belong. Welcome to Level 5.
AI rule for this level: Use AI as a power tool for rapid prototyping and code review — and start building AI-powered products yourself.
Start at the level where you checked fewer than 7 out of 10 boxes. It's better to repeat something easy than to skip something foundational.
When in doubt, start one level lower than you think — confidence compounds.
On AI tools: If you can't explain what the AI generated, you're not ready to use it at that level. See the AI tools guide in the main README.
Found your level? Start tracking your builds with the Progress Tracker.