Prompt

If you use AI to write embedded firmware—specifically bootloader hooks, flashing routines, and signature verification—and then discover that your device behaves completely incorrectly, host tests pass while the real device fails, or the online deployment is still running an old version, this post is for you. Over the last six days, I analyzed the thirteen detours we took during meta-pass v1.0 development. Most were not core technical failures, but rather the same root cause resurfacing in different forms: the task description did not specify what “done” means. ...

This is a supplementary part of the AI Path Advanced Guide L2, teaching non-coders how to use AI to write code. L2 has one final step: making AI write code that actually works. How do you make AI write code you can use? Not a demo that runs once. A script you can drop into your project and run. For someone who doesn’t code, the biggest pain points aren’t “how to write code.” They’re three questions: ...

This is Day 14 of the “AI Path: Advanced Upgrade Guide” Week 3 series. Previous post: Day 13 Practice. Project repo: picture-book-pipeline. Introduction In Day 13, I built a skill through six rounds of conversation. A skill is made of role documents, one per role. The agent works from those documents. How you write them directly dictates the quality of the output. A role document has four blocks: identity, input, output requirements, quality requirements. This post goes through each one. What to write, and why. ...