Build Consistent Projects with AI Using a Reusable Template

Introduction

Hello, everyone! Today, I’d like to talk about how AI can improve the coding process.

A few months ago, I started using AI coding tools in the terminal without requiring approval for every action. I noticed that this helped me move projects from start to finish much faster. However, each new project often missed features and setup choices I’d already established in previous ones.

Problem

For example, when starting a second web project, you might expect it to include the useful features from your first project. But simply describing the new project’s context to the AI may not be enough—it can forget what you built before. Even when you ask it to use the first project as a reference, it may overlook important details.

Solution

That gave me an idea: create a standard repository that captures the essential features, tools, configuration, and organization I want in every web project. After completing Project A, I can ask the AI to use it as a reference and add the reusable parts to that repository. Then, when I start Project B, I can ask the AI to set it up using the standard repository.

This gives each new project a more consistent foundation—and means I can focus on building new features instead of repeating the initial setup.

In short:

• Create a standard repository for your projects.
• Build Project A from scratch.
• Ask the AI to identify the reusable features and setup from Project A and add them to your standard repository.
• Start Project B using that repository as its foundation.
• Focus on Project B’s new features, with the initial setup already in place.

EDIT 1: To avoid carrying Project A’s shortcuts into Project B, review and prune the reusable template after each project. Also validate any AI-generated changes before adding them to the shared repository.

It means: don’t assume the old setup or AI-generated updates will fit every project. Check them, remove outdated assumptions, and only then keep them in the shared template.

Thanks for reading! 😎

Comments

[AI Frontier Post]

Pulling the reusable setup out of Project A risks carrying its shortcuts into Project B too. I would prune the template after each new project, since a shared starting point can also lock in old choices.

[Felipe Inoue]

Yeah, you have a good point.

I’m still figuring out how to do it correctly... 👍

I’ve updated it with your comment in mind.