Tips and tricks
1️⃣ Choosing the right IDE for AI coding
O’ve tested multiple options, but I use an AI-first IDE where I can run commands, explanations, and code changes without leaving the context.
I use it for:
• Rapid generation of pages and layouts
• Implementing backend functionality (APIs, databases)
• Building complex systems (CRMs, SaaS platforms)
The advantage is that it drastically reduces friction between idea → code → testing.
2️⃣ Always updating to the latest version of the too
Every update brings new ways of working. The ones I use the most:
• Ask: for instant debugging and clear technical explanations
• Edit: for refactoring existing functions and modules
• Agent: for complex logic involving multiple changes across different files
3️⃣ Starting with a custom starter kit
I never start from scratch. I use a kit with:
• Optimized folder structure
• Initial config for the chosen framework (e.g., Next.js, Tailwind, Prisma)
• Reusable UI components (forms, modals, grids)
This shortens the initial setup phase by at least 30–40%.
4️⃣ Documenting everything before writing the first line of code
I create clear documents for both AI and the team:
• PRD (Product Requirement Document): purpose and functions of the MVP
• App Flow: user steps within the app
• Tech Stack & API Docs: technologies and endpoints used
Without these documents, AI can easily drift and introduce logic errors.
5️⃣ Defining project rules
Instead of one global set, I have rules adapted for each file type:
• SQL → query optimization, consistent structure
• API → standards for request/response
• UI → naming, responsive design, accessibility
These rules are synced across the team for long-term consistency.
6️⃣ Building an internal code library
Everything I use repeatedly (auth, validations, common requests) is saved in the IDE’s Notepad.
Instead of rewriting logic from scratch, I reuse and adapt it.
7️⃣ Iterative implementation plan
I break the project into concrete steps (50–80 small tasks).
Each task is documented so that the AI knows exactly what to do and in what order.
As I progress, I update the plan to maintain the right context and avoid rework.