Claude Code: A Careful Workflow for Existing Projects

Reusable prompt
Inspect this repository’s instructions and mobile navigation implementation. Fix the menu’s accessible open/closed state without replacing the framework. Preserve unrelated changes. Acceptance: mouse and keyboard toggling work, state attributes match visibility, and the page fits at 320px. Explain changed files and verification results.

Review checklist
- The repository difference matches the requested scope.
- Verification tests the observable behavior.
- Existing configuration and unrelated work are preserved.

Suggested steps
1. Check the repository state and read its instructions. Identify existing uncommitted work and avoid treating unrelated changes as disposable while preparing the requested modification.
2. Inspect the relevant files and describe acceptance criteria. Specify the user-visible behavior, important edge cases, and the constraints that make a solution suitable for this project.
3. Request a concise implementation plan before a complex change. Resolve unclear dependencies early and prefer a focused edit that follows established patterns over unnecessary architectural replacement.
4. Review the resulting difference and run appropriate checks. Test the behavior in its real context and inspect any errors rather than accepting a generated summary as verification.
5. Prepare a clear handoff explaining what changed and how it was checked. Commit or deploy only within the authorized scope, preserving configuration and live data when production is involved.

Source: AI News Pro — Fajad S