Intermediate: Turn the first slice into a dependable pilot that can survive change.
Bring: Bring the Level 1 brief and working slice, or an equivalent small project with a defined user and outcome.
Level result: A pilot build with error handling, manual and automated test evidence, a reviewable change history, restore proof, and security/privacy boundaries.
- Manage context and changes without destabilizing working behavior.
- Diagnose and test with reproducible evidence.
- Protect the pilot through versioning, recovery, security, and privacy controls.
You can review the curriculum here. A free member account saves lesson work, answers, and progress.
Manage Project Context
Create a compact project context packet that keeps AI work aligned across sessions.
Build: A reusable context packet containing the user, outcome, constraints, current state, and next task.
Sign in to beginBuild Interface Basics
Turn the project brief into a clear, usable interface flow.
Build: A screen map and a working happy-path interface for the pilot.
Sign in to beginPlan Error Handling
Design failures so users know what happened and what to do next.
Build: An error-state matrix for the pilot’s important actions.
Sign in to beginSave Working Versions
Create safe checkpoints before risky changes.
Build: A named working checkpoint with restoration instructions.
Sign in to beginAsk AI to Explain Changes
Make generated changes reviewable before accepting them.
Build: A change explanation tied to files, behavior, risks, and tests.
Sign in to beginAvoid Unnecessary Rewrites
Repair the smallest responsible surface instead of destabilizing working code.
Build: A bounded change plan showing what will and will not change.
Sign in to beginManual Testing
Test the pilot as a real user across normal and edge conditions.
Build: A completed manual test checklist with results and evidence.
Sign in to beginAutomated Testing
Automate repeatable checks for the pilot’s highest-value behavior.
Build: A small automated test suite for critical rules and flows.
Sign in to beginDebugging with Evidence
Diagnose failures through reproducible evidence instead of prompt-driven guessing.
Build: A debugging record containing reproduction, observations, hypothesis, experiment, and result.
Sign in to beginRegression Testing
Protect previously working behavior when changes are made.
Build: A risk-based regression checklist connected to changed components.
Sign in to beginVersion Control in Practice
Use version control to make changes understandable and recoverable.
Build: A clean branch and commit history for one complete feature change.
Sign in to beginBackups and Recovery
Protect code, configuration, and user data with a tested recovery plan.
Build: A backup inventory plus a completed restore drill.
Sign in to beginSecurity Foundations
Apply essential security controls before inviting pilot users.
Build: A security checklist and remediation record for the pilot.
Sign in to beginPrivacy by Design
Minimize personal data and make its use understandable and controllable.
Build: A data map and privacy decision record for every collected field.
Sign in to begin