@issu on Makefast AI
In this session I was working on my project Makefast AI, which is a small AI‑powered CLI tool for developers. It runs in the terminal and helps with early project stuff like generating ideas, trying names, writing landing page copy, suggesting tech stacks, scaffolding projects, brainstorming, pitch outlines, tweets, and README drafts. I wanted something that is useful before the “real build” starts.
What I did in this session
During this time I mainly focused on making the CLI commands work properly and feel usable:
I set up and tested commands like makefast idea, makefast copy, makefast ui, makefast stack, makefast scaffold, makefast pitch, makefast tweet, makefast name, makefast validate, makefast readme, makefast history, and makefast config. Each command is small on purpose, I didn’t want one big “do everything” command.
I connected the CLI to the Groq AI API, so it can send prompts from Node.js and show the AI responses directly in the terminal for ideas, copy, stack suggestions, scaffolding, etc. This was new for me so I had to try and fix a few things.
I added local storage using a ~/.makefast folder where history, config, and logs are saved as JSON files, so the tool remembers past runs and feels more persistent.
I tested different ways to run the tool: directly with node index.js, using npm scripts (npm run dev, npm start), and using npm link so I can type makefast idea like a normal command. I also prepared it for global install (npm install -g makefast-ai).
I updated the README to explain setup (Node, npm, Groq API key, .env file), how to run commands, what scaffold templates exist (like nextjs, SaaS, api, mobile, cli, landing), and some common issues and fixes.
Problems I ran into........
I hit a few confusing issues:
API key / .env problems:
When the Groq API key was missing or .env was not loaded, most commands failed immediately. I had to figure out why process.env.GROQ_API_KEY was undefined and learn that the way you load env variables is different in CommonJS vs ESM.
CLI command not working globally:
Sometimes after installing, typing makefast did nothing. I learned that npm link, checking the bin field in package.json, and restarting the terminal can fix path issues for global CLI commands.
Name confusion:
When the GitHub repo name and npm package/CLI name were not consistent, it was very confusing. I had to clean up naming and mention this in the README.
JSON errors:
If the history/config JSON file was missing or broken, simple JSON.parse could crash the app. I had to add checks and default values so the CLI doesn’t explode when there is bad data.
What I learned
Before this project I only knew basic Node scripts. With Makefast AI and this session, I learned:
1.how to create CLI commands and run them like makefast idea in the terminal
2.how to connect a Node CLI to an AI API and send prompts from the terminal
3.how to use .env to keep my API key outside of the code and load it safely
4.how to read and write JSON files to store history and config locally
5.how to split the project into smaller files instead of one big file
6.how to test a CLI using node index.js, npm scripts, and npm link
how to design prompts for different use cases ideas, copy, stack, scaffold, pitch, tweets so the AI output is actually useful for builders
The code might not be perfect because I am still learning, but I am happy that I built my first real CLI tool that mixes AI with developer workflow and that I can actually use myself when starting new ideas.
- 1 devlog
- 54h
- 4.41x multiplier
- 44 Stardust