An AI building coach for anyone building with AI, it asks the four questions, holds a gate before it builds, and never stops coaching while it does.
Your words are the programming language, and Pre-Flight is the coach. YOU bring the ideas or brainstorm with Pre-Flight, from your first feature to the ones you ship, Pre-Flight guides your learning. No server, no dependencies, no extra API key.
Pre-Flight Coaching is for everyone. It's for the vibe-coder who wants to understand their code. It's for the new dev who wants to learn the why behind what AI is building. I built the Pre-Flight Coaching system because in a world where anyone can build with AI, everyone should have the opportunity to understand what they are building.
Bas — BuiltByBas
A pilot never rolls onto the runway on a hunch. Pre-Flight runs the same four questions on every feature, and refuses to write code until each one is answered. That gate is the whole point.
The very last thing the user sees when it worked. Concrete, observable, no hand-waving.
Proof you can see yourself, never just trusting the machine's say-so that it worked.
The edges of this feature, named out loud, so scope cannot quietly creep mid-build.
The facts living only in your head, the thing the code has no way of knowing until you say it.
Want more than a one-line check? The optional Pre-Flight Secops check (/secops) turns that second question into a real test plan before you build, the cases worth checking and what each one proves, coached out, never handed over as a list. The single check still gates; this only deepens it.
Four ways people try to skip the work. Click one and watch Pre-Flight name the rule and hold, never a gotcha, always a lesson.
Once the gate clears, Pre-Flight builds the feature alongside you. Then it does the part most tools skip: it walks you through testing the thing with your own eyes, on your own device, before anyone calls it done.
Feature shipped, it points you straight at the next one and runs the four questions again. The discipline compounds. By the third feature, the checklist is muscle memory.
Build alongsideCoach the testNext featureThe default is one feature, start to finish. Show up with a whole session in mind and two optional modes let you line the work up and build it back to back, without ever loosening the gate.
Name the features, put them in order, and surface what depends on what. A leaderboard needs scores saved first, so score-saving leads and the leaderboard sits behind it. You own which features matter; Pre-Flight sequences them and flags the dependencies.
Every feature clears its own comprehension checkpoint first, no exceptions. Only then does Pre-Flight build the queue back to back, then walks you through testing each one against its own CHECK, in order.
You don't even have to choose. Name several features at once and Pre-Flight routes you automatically: two or three into Flight Plan, four or more into Chart a Course, always announced, always with an off-ramp. And it holds a hard line, one Flight Plan and one Chart a Course at a time, never more.
Native slash commands on Claude Code, typed as text on every other surface. Each one acts, or shows you its state.
Pre-Flight reads how you answer across features and remembers it in a DECISIONS.md in your own project folder. Where you consistently nail a question, it loosens the scaffolding and trusts you. Where you're still finding your footing, it keeps full support in place.
At the close of each feature it names the single highest-leverage place to practice next, grounded in your actual work, not a generic tip. It works fine without the log, and noticeably better with it.
One quick question at the start sets your opening register. From there Pre-Flight adapts to your skill, your growth, and how you show up in the moment, and it never announces a word of it.
Plain language, no jargon, an everyday example before a technical one. The most support, offered before you ask.
Uses the words you've earned, sharper questions, trusts you to reach first. Help arrives when you get stuck.
Light on building talk, you have it. Leans hard into the shipping gaps: verification, scope, "done" for a stranger.
Then it grows with you. Reading your decision log, it lightens up on the questions you've earned and keeps full support on the ones you still hedge, per question, dialing down as readily as up. No badges, no "you leveled up", you just feel a coach who knows you.
Not a Wikipedia article on the domain. Pre-Flight teaches the why using the exact thing you just built, then offers to go deeper. It also opens a “Ready to learn?” door at the end of every feature, there when you want it, a “not now” away when you don't.
No build, no runtime, nothing to install. Interpretable context methodology: every file has a single clear purpose, so a stranger can read the whole coach and understand exactly how it thinks.
Pre-Flight reads and writes files directly. Your project memory, the DECISIONS.md that powers its leveling, and the build itself all live in your folder and carry across sessions automatically.
Connect the repo, pick the folder, say hello. Your first message brings Pre-Flight to life, even just “Hi.”
Add the folder to a Project, or attach the files, and say hello. Pre-Flight runs on the interpretable context, its commands typed as text.
Open your repo and point Codex at the folder. The same markdown drives the coaching, its commands typed as text.
Pre-Flight meets you at your very first feature and stays with you through the ones after, it remembers how you answer, grows with you, and teaches the why from your own code. It comes with your Praxis Academy membership, along with the other ICMs I build and the content I create on the platform. Become a member, say hello, and start your climb.