300 wpm
read the existing code and understand the project structure before making any changes build a plan for implementing this feature then break it down into small testable steps follow the patterns already used in the codebase and keep the solution simple investigate this bug and find the root cause before changing any code trace the flow of data from the input to the failing output reproduce the issue with a minimal example fix the underlying problem and add a regression test review the changes in this branch for correctness security and maintainability focus on actual bugs and edge cases instead of style preferences explain each finding with a file reference a concrete example and a suggested fix refactor this module to make it easier to understand without changing its public behavior remove duplicated logic give variables meaningful names and separate unrelated responsibilities keep the diff focused and run the existing tests after each change write tests for the public behavior of this component cover the happy path empty inputs invalid values and error states avoid testing implementation details use the existing test framework and make sure each test can fail for a meaningful reason implement the new settings page using the existing design system include loading empty success and error states make the form accessible with clear labels and keyboard navigation validate inputs and preserve the current values when saving fails trace this request from the user interface through the api to the database identify where the response stops matching the expected behavior check the logs and verify your assumptions make the smallest change that resolves the issue find unused code and unnecessary abstractions in this feature check every reference before removing an export simplify the control flow and preserve the existing api explain the changes and note any behavior that needs manual verification compare this branch against main and review the complete diff look for missing validation race conditions and unintended behavior changes prioritize findings by impact and include only issues supported by the code summarize any remaining test coverage gaps add integration tests for this api endpoint verify authentication request validation successful responses and database failures check that sensitive fields are never returned keep test data isolated and clean up resources when each test finishes create a responsive dashboard with a clear navigation structure and reusable components start by inspecting the current application use semantic html and support both mouse and keyboard interactions run the production build and fix any errors before finishing measure the performance of this page and identify the slowest operation check for unnecessary renders repeated network requests and expensive computations fix the measured bottleneck and compare the results before and after the change update the readme so a new developer can run this project locally document the required environment variables installation steps and available scripts include a short explanation of the folder structure and how to run the tests review this authentication flow for security issues check session expiration access controls input validation and error messages verify that secrets stay on the server and that users can only access their own data suggest concrete fixes for confirmed problems extract the data fetching logic into a reusable hook keep presentation components focused on rendering and user interactions preserve loading and error behavior avoid introducing extra requests and verify that the component still works when props change write a failing regression test for this reported bug before implementing the fix make sure the test reproduces the real user scenario apply the smallest reliable correction run the related tests and confirm that the regression test now passes plan a migration for this database change that preserves existing records account for missing values and rollback behavior update the application code and tests together explain the deployment order and verify that old and new records both work investigate why this component sometimes displays stale results check for overlapping requests and state updates after unmounting ensure that only the latest response updates the interface add a test that reproduces the race condition standardize error handling across these api routes return consistent status codes and useful messages without exposing internal details keep the existing success responses unchanged add tests for the error cases and document the response format test this dialog using only the keyboard verify the initial focus tab order escape key and return of focus after closing check accessible labels and ensure that background controls cannot receive focus while the dialog is open read the existing code and understand the project structure before making any changes build a plan for implementing this feature then break it down into small testable steps follow the patterns already used in the codebase and keep the solution simple investigate this bug and find the root cause before changing any code trace the flow of data from the input to the failing output reproduce the issue with a minimal example fix the underlying problem and add a regression test review the changes in this branch for correctness security and maintainability focus on actual bugs and edge cases instead of style preferences explain each finding with a file reference a concrete example and a suggested fix refactor this module to make it easier to understand without changing its public behavior remove duplicated logic give variables meaningful names and separate unrelated responsibilities keep the diff focused and run the existing tests after each change
everyday developer prompts20 prompts · 5 categories