Development Best Practices

Testing Changes Safely

Before making changes:

don't change any code whatsoever.
Theoretically, if I want to add [feature],
what code changes would be needed?

Handling Issues

When problems arise:

1. Save working versions
2. Fork the project
3. Break into smaller prompts
4. Check GitHub issues

Example error prompt:

This component worked before:
[paste working version]
Now it shows this error:
[paste error]
How do I fix it?

Success Strategies

• Save working code and components
• Document successful prompts
• Build a reference library
• Test features independently
• Avoid mixing database implementations
• Add auth after UI is stable

Data Management

Storage Setup

Keep data requirements clear:

I need to save:
- User profiles
- Product listings
- Order history

Database Options

• Firebase: Best for beginners
• Supabase: Easy PostgreSQL

Integration Tips:

• Start with simple integrations
• Let your vibe coding tool guide API setup
• Watch for over-complication

Project Organization

Comments:

• Request vibe coding tool add detailed comments
• Explain function purposes
• Document data flow
• Note key decisions

Backups:

• Fork project in StackBlitz frequently
• Download full codebase
• Document major changes

Prompt Library:

• Save successful commands
• Document architecture decisions
• Keep debugging prompts
• Note common fixes