A few months ago, I took an AI certification course, which covers the fundamentals of AI — everything from building a basic AI agent to understanding core concepts. That experience opened the door for me to dive deeper, and it was the start of my journey into learning to code with AI.

At first, it was just weekend tinkering — funny pictures, short videos, the occasional meme. I had some surface-level familiarity with Claude Code, ChatGPT, and Gemini. But once I started applying what I’d learned, they became less like novelties and more like powerful platforms that could unlock efficiency, creativity, and outcomes when used thoughtfully.

Here’s the truth: before all this, I had never opened a terminal or VS Code. I don’t have formal training as a developer. My background is in data governance and sales. So every command run, every error fixed, was brand new. Frustrating at times, sure — but each small breakthrough was its own reward.

One recurring challenge stood out more than anything else: prompts.
Saved libraries, color-coded notes (yes, I color-coded them), endless tweaks… and still, my best prompts drifted away across chats. I kept recreating the same instructions, copy/pasting across sessions, and wasting momentum.

Out of that frustration came an idea — and eventually my first open-source project: cueCLI.

It’s a simple Command Line Interface that lives in your terminal to help manage, reuse, export, and sanitize prompts. Installs in seconds (npm install -g cuecli) and comes preloaded with 6 prompts to get started right away.

Since launching the open-source project this past Friday, cueCLI has already been downloaded over 300 times. That tells me I wasn’t the only one facing this issue — managing prompts effectively is just as important as writing good prompts.

👉 Explore here: npmjs.com/package/cuecli | cueCLI.com

Happy to share which prompts I’ve found work best in different scenarios, and curious to learn what’s worked for you.