Let the AI Set Things Up
You don't need to know how — the AI does
The liberating truth
Here’s a sentence that would have been absurd five years ago and is completely true today:
You don’t need to know how to set up a project. You just need to know what you want.
Setting up a new project used to be the hardest part of development. Choose a framework, configure the build tools, set up testing, configure linting, create the folder structure, install dependencies, wire up the database… Each step required specialized knowledge and could take hours of debugging.
Now? You describe what you want, and the AI does all of it.
Scaffolding = letting the AI build the foundation
“Scaffolding” means creating the initial structure of a project — the folders, configuration files, starter code, and dependencies. It’s the construction equivalent of pouring the foundation and framing the walls.
Here’s what scaffolding looks like with a CLI tool:
Create a new web application with these specs:- Astro framework with React components- Tailwind CSS for styling- Dark theme- A homepage with a hero section- A navigation bar with Home, About, and Contact links- TypeScript for type safetyThe AI will:
- Create the project folder
- Initialize
package.json - Install all dependencies
- Create the Astro configuration
- Set up Tailwind with the dark theme
- Create the layout with navigation
- Create the homepage with hero section
- Set up TypeScript configuration
All from one prompt. What would take a developer 30-60 minutes of setup takes 2-3 minutes.
The key insight
You don’t need to understand:
- How Tailwind’s configuration file works
- What
astro.config.mjsdoes internally - How TypeScript compilation is configured
- What PostCSS is or why it’s there
You need to understand:
- What you want to build (a website with specific features)
- What it should look like (dark theme, clean design)
- What technologies to use (Astro, React, Tailwind — or let the AI choose)
The AI handles the implementation details. You handle the vision and verification.
If you don’t have a preference, it’s totally fine to say “Build me a personal portfolio website. Choose whatever tech stack makes sense.” The AI will pick reasonable defaults. As you gain experience, you’ll develop opinions about tools and frameworks — then you can be more specific.
Real examples
Example 1: Blog
Prompt:
Create a blog using Astro with:- Markdown content in a content/ folder- Homepage showing recent posts- Individual post pages- Dark theme with good typography- Tags on postsWhat the AI creates:
my-blog/├── src/│ ├── content/posts/│ │ ├── first-post.md│ │ └── second-post.md│ ├── layouts/│ │ └── BlogLayout.astro│ ├── pages/│ │ ├── index.astro│ │ └── posts/[slug].astro│ └── styles/global.css├── astro.config.mjs├── tailwind.config.mjs└── package.jsonA complete blog. Ready to customize.
Example 2: Dashboard
Prompt:
Create a data dashboard with:- React + Vite- A sidebar navigation- Three pages: Overview, Analytics, Settings- Charts using a charting library- Mock data for demonstration- Dark themeExample 3: API server
Prompt:
Create a REST API with:- Node.js and Express- Endpoints for users (CRUD)- SQLite database- Input validation- Error handling- Basic test suiteIn each case, the AI builds the complete scaffolding and initial functionality. Your job is to refine, customize, and extend.
The orchestrator’s advantage
Here’s why this matters so much:
Without AI scaffolding:
- “I want to build X” → 3 weeks of learning before you can start → many people quit
With AI scaffolding:
- “I want to build X” → AI creates it in 3 minutes → you start customizing immediately → you learn by doing
This flips the entire learning model. Instead of learning theory first and building later, you build first and learn the theory as needed. When you see the code the AI generates, you naturally start understanding patterns. When something breaks, you learn debugging. When you need a feature, you learn the relevant concept.
What's the most important thing you need to know to scaffold a project with an AI tool?