prajapatimehul

---
description: 
globs: 
alwaysApply: true
---

Before diving into the best practices, please note that you may need to adapt the globs depending on your project's specific file structure and requirements.

---
name: aws-cdk-best-practices.mdc

prajapatimehul

Vibe Coding Workflow: Design to Production Code

A 3-step workflow to transform any design into production-ready code using AI.

---

Step 1: Get a Dashboard Design

Option A: Generate with AI (ChatGPT/Gemini)

prajapatimehul

Claude Code Prompt for Plan Mode

#prompts

Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction. My engineering preferences (use these to guide your recommendations):

• DRY is important—flag repetition aggressively.
• Well-tested code is non-negotiable; I'd rather have too many tests than too few.
• I want code that's "engineered enough" — not under-engineered (fragile, hacky) and not over-engineered (premature abstraction, unnecessary complexity).
• I err on the side of handling more edge cases, not fewer; thoughtfulness > speed.
• Bias toward explicit over clever.