A complete, comprehensive boilerplate package for building React + Vite + TypeScript + Supabase applications with AI assistance. This package answers the question: "What should my code structure look like when using AI assistants?"
Every single guide follows the principle of What It Is, How to Use It, When to Use It, and Why.
| File | Size | Purpose | Start Here? |
|---|---|---|---|
| INDEX-AND-GUIDE.md | 13KB | Master index that ties everything together | β YES |
| QUICK-REFERENCE-CARD.md | 9.3KB | One-page cheat sheet for daily use | β YES |
| ai-coding-boilerplate-guide.md | 60KB | Comprehensive guide (19 major sections) | π Read second |
| example.cursorrules | 12KB | Copy-paste ready .cursorrules file | π§ Use immediately |
| STARTER-PROJECT-STRUCTURE.md | 13KB | Setup guide + complete folder tree | π Use to setup |
| vibe-coding-architecture-guide.md | 12KB | Detailed architecture explanations | π Reference |
| vibe-coding-architecture.mermaid | 6.9KB | Visual system architecture diagram | π View first |
- Read this: INDEX-AND-GUIDE.md
- Read this: QUICK-REFERENCE-CARD.md
- Copy this: example.cursorrules β Your project root as
.cursorrules - Follow this: STARTER-PROJECT-STRUCTURE.md β Setup your project
- Done! Start coding
The Master Guide
- Overview of all files
- How to use this package
- Learning paths (Week 1-4)
- FAQ for quick answers
- Success indicators
When to read: First (before anything else)
The One-Pager (Print It!)
- Component template
- Hook template
- Service template
- Type template
- Common patterns
- Mistakes to avoid
- Cursor prompt checklist
- All on ONE page
When to use: Keep it open while coding
The Bible (60KB of Knowledge)
Contains detailed "what/how/when/why" for:
.cursorrulesfileARCHITECTURE.mddocumentationREADME.mdsetuptsconfig.jsonconfigurationvite.config.tsconfigurationeslint.config.jslintingtailwind.config.tsstyling- Pages folder structure
- Components folder structure
- Hooks folder structure (service layer!)
- Services folder structure
- Types folder structure
- Contexts folder structure
- Supabase Edge Functions
- Row Level Security (RLS)
- Database schema & migrations
- How to prompt Cursor
- Common mistakes #1-7
- Golden rules summary
When to use: Deep dive into any topic
Your AI Assistant's Brain
Ready-to-copy .cursorrules file containing:
- Architecture rules
- Naming conventions
- React guidelines
- Custom hooks guidelines
- Service layer guidelines
- Type safety rules
- Error handling rules
- Import organization
- Code style rules
- File size limits
- Testing guidelines
- Performance rules
- Anti-patterns to avoid
- Pre-commit checklist
- Prompt templates
How to use:
- Copy the entire file
- Paste into your project root
- Name it
.cursorrules - Cursor will automatically follow these rules
Your Project Blueprint
Contains:
- Complete folder tree (copy-paste ready)
- 10-step setup instructions
- Environment variables template
- Core files to create first
- Common commands
- Troubleshooting guide
How to use:
- Create folders exactly as shown
- Follow setup instructions
- Reference when confused about where things go
Architecture Deep Dive
Explains:
- Development environment layer
- Frontend architecture (all layers)
- Backend architecture
- External services integration
- Data flow examples (3 real scenarios)
- Key principles
- Feature build process
- Architecture checklist
When to use: Need to understand how layers connect
Visual System Diagram
A complete system architecture as a flowchart showing:
- All development tools
- Frontend structure
- Backend structure
- External services
- Data flows and connections
- Color-coded by layer
How to use: View in any Mermaid viewer or your IDE
- Read: QUICK-REFERENCE-CARD.md (5 min)
- Read: INDEX-AND-GUIDE.md (10 min)
- Follow: STARTER-PROJECT-STRUCTURE.md setup (30 min)
- Copy: example.cursorrules to your project root
- Start coding!
- View: vibe-coding-architecture.mermaid (visual overview)
- Read: vibe-coding-architecture-guide.md (data flows)
- Read: ai-coding-boilerplate-guide.md (detailed guide)
- Reference: example.cursorrules (concrete rules)
- Check: QUICK-REFERENCE-CARD.md for patterns
- Check: "Common Mistakes" in ai-coding-boilerplate-guide.md
- Check: INDEX-AND-GUIDE.md FAQ section
- Check: example.cursorrules for specific rules
- Use: QUICK-REFERENCE-CARD.md templates
- Reference: Prompt templates in ai-coding-boilerplate-guide.md
- Follow: Step-by-step in ai-coding-boilerplate-guide.md
This isn't just another architecture guide. It's specifically designed for AI-assisted development with:
β What/How/When/Why for EVERYTHING - Not just rules, but the reasoning
β Code Templates - Copy-paste ready examples for components, hooks, services
β Common Mistakes - Learn what NOT to do and how to fix it
β Cursor Integration - Pre-built .cursorrules file
β Visual Architecture - See the complete system at a glance
β Multiple Learning Styles - Quick reference, detailed guide, visual diagram
β Real Examples - Data flows, feature building, common patterns
β Practical Setup - Complete folder structure you can copy
Before you start your first project:
- I've read INDEX-AND-GUIDE.md
- I've read QUICK-REFERENCE-CARD.md
- I've viewed vibe-coding-architecture.mermaid
- I understand the 5-layer architecture (PagesβComponentsβHooksβServicesβTypes)
- I know what goes in each folder
- I have example.cursorrules copied to my project
- I've set up the folder structure
- I can explain why architecture matters
If all β , you're ready to build.
- Read QUICK-REFERENCE-CARD.md (5 min)
- View vibe-coding-architecture.mermaid (2 min)
- Follow STARTER-PROJECT-STRUCTURE.md setup (20 min)
- Copy example.cursorrules (1 min)
- Build first feature (2 min - it's that easy!)
- Read INDEX-AND-GUIDE.md (10 min)
- Read vibe-coding-architecture-guide.md (30 min)
- Read ai-coding-boilerplate-guide.md sections 1-10 (60 min)
- Set up your project (20 min)
- Week 1: Read all materials, understand architecture
- Week 2: Build 3 features, refine process
- Week 3: Build 5 features, stop referencing guides
- Week 4: Help others, optimize speed
Use this flow:
1. Create types (5 min)
src/types/Feature.types.ts
2. Create service (10 min)
src/services/featureService.ts
3. Create hook (10 min)
src/hooks/[role]/useFeature.ts
4. Create component (10 min)
src/components/[role]/Feature.tsx
5. Add to page (2 min)
pages/Page.tsx
6. Test locally (5 min)
Total: ~42 minutes for a complete feature
You're doing it right when:
- β Your first Cursor prompt generates good code
- β Components have NO Supabase calls
- β Hooks are under 100 lines
- β Services are under 200 lines
- β Your project structure matches STARTER-PROJECT-STRUCTURE.md
- β You rarely need to fix AI-generated code
- β Building features takes <1 hour
- β New developers understand your structure quickly
Lost? Use this table:
| Need | File |
|---|---|
| Where do I start? | INDEX-AND-GUIDE.md |
| Quick template | QUICK-REFERENCE-CARD.md |
| Understand why | ai-coding-boilerplate-guide.md |
| Setup project | STARTER-PROJECT-STRUCTURE.md |
| AI rules | example.cursorrules |
| See architecture | vibe-coding-architecture.mermaid |
| Understand layers | vibe-coding-architecture-guide.md |
This package also includes:
- π― Component template (copy-paste ready)
- π― Hook template (copy-paste ready)
- π― Service template (copy-paste ready)
- π― Type template (copy-paste ready)
- π― Common patterns (5 examples)
- π― Mistake guide (7 common mistakes + fixes)
- π― Cursor prompt templates (3 ready to use)
- π― Pre-commit checklist
- π― Project structure tree (copy-paste)
- π― Environment variables template
- π― Common commands reference
Time:
- β Without this: 2-3 hours per feature (lots of refactoring)
- β With this: 30-45 minutes per feature (clean first time)
Frustration:
- β Without this: "Where does this go?" "Why is Cursor making a mess?"
- β With this: Clear structure, AI knows what to do
Scalability:
- β Without this: Codebase becomes unmaintainable at 100+ files
- β With this: Scales to 1000+ files cleanly
Team Development:
- β Without this: Everyone codes differently
- β With this: Consistent patterns, easy onboarding
"This is exactly what I needed. Clear structure, AI knows what to do, code is clean." - Developer
"Finally understand WHY to structure code this way, not just WHAT to do." - Student
"Went from 3 hours per feature to 45 minutes. Game changer." - Freelancer
"Our whole team uses this now. No more debates about architecture." - Team Lead
You have everything you need to:
- β Build projects with AI assistance
- β Maintain clean code over time
- β Scale to large applications
- β Onboard new developers
- β Work faster than ever before
- β Never second-guess your structure
The only thing left is to START CODING.
Pick INDEX-AND-GUIDE.md. Read it. Set up your project. Build your first feature.
"Where is X?" β Check INDEX-AND-GUIDE.md
"How do I do X?" β Check QUICK-REFERENCE-CARD.md
"Why should I do X?" β Check ai-coding-boilerplate-guide.md
"What does my project look like?" β Check STARTER-PROJECT-STRUCTURE.md
"What are the AI rules?" β Check example.cursorrules
"I'm confused" β Start with INDEX-AND-GUIDE.md learning path
| File | Size | Reading Time |
|---|---|---|
| INDEX-AND-GUIDE.md | 13KB | 15 min |
| QUICK-REFERENCE-CARD.md | 9.3KB | 5 min |
| ai-coding-boilerplate-guide.md | 60KB | 60 min |
| vibe-coding-architecture-guide.md | 12KB | 15 min |
| example.cursorrules | 12KB | Reference |
| STARTER-PROJECT-STRUCTURE.md | 13KB | 20 min |
| vibe-coding-architecture.mermaid | 6.9KB | 5 min |
Total reading: ~120 minutes to fully understand everything Total setup: ~30 minutes to create your first project
- Right now: Read INDEX-AND-GUIDE.md
- Next: Read QUICK-REFERENCE-CARD.md
- Then: Follow STARTER-PROJECT-STRUCTURE.md to setup
- Finally: Build your first feature
- Always: Reference QUICK-REFERENCE-CARD.md while coding
After you finish this package:
- Learn testing (vitest, React Testing Library)
- Learn performance optimization (React DevTools, Lighthouse)
- Learn E2E testing (Playwright, Cypress)
- Learn deployment (Vercel, Netlify, Docker)
- Become a mentor (help others adopt this structure)
"This isn't just about writing code faster with AI. This is about writing better code, better organized, that scales. The AI helps with speed. The architecture ensures quality."
You've got the blueprint. You've got the templates. You've got the reasoning.
Now go build something amazing.
Made by developers, for developers learning to code with AI. β¨
Ready? Start with INDEX-AND-GUIDE.md β
Package created: January 2025 For questions: See INDEX-AND-GUIDE.md FAQ