Implement a change

Describe the result you want#

Enter what you want to build. Include both the behavior to change and anything that should stay the same.

Add a password confirmation field to the signup screen.
Show a message below it when the passwords differ.
Keep social login and the existing screen design unchanged.
Add and run the relevant tests.

You do not need to choose files or an implementation method first. Mirr Code can explore the project to find the relevant code. If the outcome is not clear yet, ask it to gather the necessary details first.

Review a plan first#

Choose Plan mode, or ask “Explain the proposed changes before implementing them.” Review the plan, add or revise constraints, then continue into implementation.

Restructure without changing behavior#

Refactoring means changing code structure while preserving its behavior. State what must stay the same and ask Mirr Code to use existing tests as a baseline.

Consolidate the duplicate email checks in this file.
Keep the accepted email formats and error messages unchanged.
Find callers and related documentation and update them where needed.

Changes spanning several areas can be split into independently checkable steps. Renaming also requires finding code and documentation that use the old name.

Check tests and execution results#

Ask Mirr Code to find and run the project's test commands. Depending on the task, checks can include relevant tests, type checking, and the actual screen or program output.

Ask for the changed files, checks run and their results, and checks that could not be run. Distinguish pre-existing test failures from failures introduced by the change.

A check that could not run is not a passing check. Ask how to verify it in another environment or work with the relevant maintainer. See Review code for an additional review.