My Day-to-Day AI Dev Workflow (Git + Cursor/Windsurf/Cline + Playwright + Supabase + Replit)

---

---

AI Summary

Video Summary: AI Dev Workflow

• Git Integration:
  • Emphasizes the importance of using Git for a clean work state.
  • Integrates Git into the workflow to avoid frequent command-line use.
• Code Iteration Example:
  • Describes adding a new feature to a Visa appointment booking product.
  • Feature involves front-end changes, data saving, backend changes, database migrations, and UI tests.
• Database and Migrations:
  • Uses Superbase for database management.
  • Demonstrates creating a database migration to add a new column with a default value.
• AI Code Editors and Workflow:
  • Discusses using AI agents (Cursor AI agent, Wind Cascade) to automate code generation.
  • AI agents are instructed to search for tests, review them, and run TypeScript compiler and Playwright tests.
  • Utilizes Prettier for code formatting.
• Code Review and Validation:
  • Stresses the importance of reviewing AI-generated code for maintainability.
  • Reviews changes made by AI, including server actions, schema validation, and UI updates.
• Commit Generation:
  • Uses a rules file to generate commit messages.
  • Manually runs Prettier to enforce formatting before committing.
• Database Deployment:
  • Pushes local database changes to production using Superbase.
  • Ensures migrations do not contain breaking changes.
• Deployment with Repet:
  • Uses Repet for easy iteration and live testing in the cloud.
  • Demonstrates deploying to a staging environment and then to production.
• Final Testing and Deployment:
  • Validates the deployment in the production environment.
  • Highlights the efficiency of the workflow with AI-generated tests and database migrations.
• Reflection on AI Code Editors:
  • Discusses the ongoing process of refining instructions for AI coding assistants.
  • Plans to update the workflow as AI tools evolve.

Detailed Instructions and Tips (No URLs or CLI commands provided in the transcript):

• No specific CLI commands, website URLs, or detailed tips were provided in the transcript.