Cline Tips & Prompts — AI Coding Assistant Guide

I need to implement {{feature_name}}. Before writing any code, break this into a step-by-step plan:

1. List every file that needs to be created or modified
2. For each file, describe what changes are needed (be specific — not "update the component" but "add a new prop called X and render it in the header")
3. Identify the order of operations — which changes depend on others?
4. Note any potential risks or side effects

Context:
- Tech stack: {{tech_stack}}
- Relevant existing files: {{relevant_files}}
- Requirements: {{requirements}}

Present the plan and wait for my approval before making any changes. I may want to adjust the scope or approach before you start.

Edit {{file_path}} to {{change_description}}.

Specific changes:
- In the {{section_name}} section (around line {{line_number}}), {{edit_1}}
- {{edit_2}}
- {{edit_3}}

Constraints:
- Do NOT modify any other functions or exports in this file
- Do NOT change the import statements unless the new code requires a new import
- Do NOT reformat or re-indent code you didn't change
- Preserve all existing comments

After making the changes, show me a summary of exactly what was modified (like a diff).

Run the following commands to {{goal}}:

1. {{command_1}}
2. {{command_2}}
3. {{command_3}}

For each command:
- Show me the command before running it
- If the command fails, show the error output and suggest a fix before retrying
- Do NOT run the next command until the previous one succeeds

If any command requires user input or confirmation, pause and ask me.

Environment notes:
- Working directory: {{working_directory}}
- OS: {{operating_system}}
- Required tools already installed: {{installed_tools}}

Before starting, read these files to understand the context:

1. {{file_1}} — {{why_file_1}}
2. {{file_2}} — {{why_file_2}}
3. {{file_3}} — {{why_file_3}}

After reading, confirm your understanding by answering:
- What is the purpose of each file?
- How do they relate to each other?
- What patterns/conventions do they follow?

Then, using this context, {{task_description}}.

Important: The code you write must follow the same patterns you observed in the existing files — same naming conventions, same error handling style, same import patterns. If you're unsure about a convention, ask rather than guessing.

I want to {{overall_goal}}. Work through this incrementally:

Phase 1: {{phase_1_description}}
- Make the changes for phase 1
- Show me what you changed (file-by-file summary)
- STOP and wait for my approval before proceeding

Phase 2: {{phase_2_description}}
- Only start after I approve phase 1
- Show changes and wait for approval

Phase 3: {{phase_3_description}}
- Only start after I approve phase 2
- Show changes and wait for approval

Rules:
- Never combine phases — one at a time
- If you encounter an issue in any phase, stop and explain it instead of working around it
- Each phase should be independently functional (the app shouldn't break between phases)
- If I say "revert phase N", undo only that phase's changes

# Project Custom Instructions for Cline

## Tech Stack
- Framework: {{framework}}
- Language: {{language}} (strict mode)
- Styling: {{styling}}
- Database: {{database}}
- ORM: {{orm}}

## Code Conventions
- File naming: {{file_naming_convention}}
- Component pattern: {{component_pattern}}
- State management: {{state_management}}
- Error handling: Always use try/catch, never swallow errors silently

## Rules
- Never use `any` type — find or create the proper type
- Always add JSDoc comments for exported functions
- Never modify files outside the scope of the current task
- Run {{lint_command}} after any code change
- Prefer editing existing files over creating new ones
- Ask before installing new dependencies

## Project Structure
{{directory_structure_summary}}