Vibe Coding — What It Is & How to Get Started

Build a {{app_type}} with the following requirements:

Tech stack: {{tech_stack}}

Features:
{{feature_list}}

Design:
- Clean, modern UI with {{design_style}} aesthetic
- Mobile responsive
- Accessible (ARIA labels, keyboard navigation)

Start by creating the project structure, then implement each feature one at a time. After each feature, briefly confirm what was built before moving to the next.

Constraints:
- Use only the specified tech stack — do not introduce additional frameworks
- Include basic error handling for user-facing interactions
- Add comments explaining non-obvious decisions

Here is my current code:

{{current_code}}

I want to change the following:
{{change_description}}

Rules:
- Only modify the parts that need to change — keep everything else exactly as it is
- If my description is ambiguous, pick the most common/expected interpretation and note your assumption
- Show me the complete updated code (not just a diff)
- After the code, list every change you made in a bullet list

Do not refactor, optimize, or "improve" anything I did not ask about.

Recreate the UI shown in the attached screenshot using {{framework}} and {{css_approach}}.

Screenshot description (if no image attached):
{{ui_description}}

Requirements:
- Match the layout, spacing, and visual hierarchy as closely as possible
- Use semantic HTML elements
- Make it fully responsive (mobile, tablet, desktop)
- Use placeholder content where real content is not visible
- Include hover and focus states for interactive elements

Return:
1. The complete component code
2. Any required CSS/Tailwind classes
3. A list of assumptions made about responsive behavior

I have an existing {{framework}} application. I want to add a new feature.

Current app description: {{app_description}}
Existing file structure:
{{file_structure}}

New feature: {{feature_description}}

Please:
1. Explain how this feature fits into the existing architecture
2. List every file that needs to be created or modified
3. Implement the changes file by file, starting with data/backend changes and ending with UI
4. After all changes, explain how to test the new feature

Important: Do not modify any existing functionality. The new feature should be additive only.

My {{language}} code is not working as expected.

Code:
{{buggy_code}}

Expected behavior: {{expected_behavior}}
Actual behavior: {{actual_behavior}}
Error message (if any): {{error_message}}

Please:
1. Identify the root cause of the bug (not just the symptom)
2. Explain WHY this bug occurs — what is the code actually doing vs. what I intended?
3. Provide the fixed code with the minimal change needed
4. Suggest a test case that would have caught this bug
5. Note if this is a common mistake and how to avoid it in the future

I have a {{app_type}} application built with {{tech_stack}} and I want to deploy it to {{platform}}.

Current state:
- Source code is in a {{repo_type}} repository
- Environment variables needed: {{env_vars}}
- Database: {{database_info}}

Please provide a complete deployment guide:
1. Prerequisites: What accounts, CLI tools, or configs I need before starting
2. Build configuration: Any build settings, environment files, or scripts needed
3. Deployment steps: Exact commands to run, in order
4. Post-deployment: How to verify it is working, set up monitoring, and configure a custom domain
5. Common issues: Top 3 problems people hit deploying this stack to this platform, and how to fix them

Write the guide assuming I have never deployed to {{platform}} before.