Skilled Next.js/React Developer Needed for Targeted Bug Fixes & Codebase Improvements

I’m looking for an experienced Next.js, React, and TypeScript developer to review and fix a few issues in an existing task-management dashboard. The project is already built. This is not a greenfield development project. I need someone who can understand the existing codebase, make clean targeted changes, and avoid unnecessary refactoring. There are 4 specific issues to address. 1. Fix invisible Edit and Delete buttons on mobile. High Priority File: components/tasks/task-card.tsx Location: Around line 53 The Edit and Delete buttons currently use opacity-0 group-hover:opacity-100. This works with a mouse, but on phones and tablets there is no reliable hover interaction, meaning the buttons can be completely invisible and unusable. Expected result Edit and Delete actions should be accessible on touch devices. Desktop hover behavior can remain if appropriate. The solution should be responsive and consistent with the existing UI and design. Avoid introducing unnecessary layout changes. 2. Sort Tasks by Most Recently Updated. Medium Priority File: app/dashboard/tasks/page.tsx Location: Around lines 36 to 52 The Tasks page filters the task array but does not sort it. As a result, tasks appear in their stored order rather than by most recently updated. The Dashboard Recent Tasks section already sorts tasks by updatedAt in: app/dashboard/page.tsx, around lines 50 to 54 The Tasks page should use the same logical ordering so the application behaves consistently. Expected result Tasks should be displayed with the most recently updated tasks first. Existing filtering functionality must continue working. Sorting should be done cleanly without mutating the original data unnecessarily. 3. Improve Task Search to Include Descriptions. Low Priority File: app/dashboard/tasks/page.tsx Location: Around line 40 The current search only checks the task title. The placeholder currently says: Search tasks by title... While this technically matches the current implementation, it creates a UX limitation because users may remember words from the task description rather than its title. Expected result Search should match both the task title and description. Existing title search should continue working. Search should remain case-insensitive. Update the placeholder text if appropriate, for example: Search tasks by title or description... 4. Remove or Properly Use the Unused compact Prop. Low Priority File: components/tasks/task-card.tsx Location: Around line 25 The TaskCard component has a compact prop that changes the card's padding, but no component in the application currently uses the compact prop. This appears to be unused or dead code. Expected result Review how TaskCard is currently used throughout the application. Either remove the unused compact prop and related logic, or implement and use it if there is a legitimate existing use case. Keep the codebase clean and avoid unnecessary unused props. Requirements I'm looking for someone who: Has solid experience with Next.js, React, TypeScript, and Tailwind CSS. Can quickly understand an existing codebase. Pays attention to responsive and mobile UX. Can identify inconsistencies rather than blindly making the requested edits. Writes clean and maintainable code. Avoids unnecessary changes or large refactors. Can test the changes on both desktop and mobile or responsive layouts. Deliverables 1. Fix all 4 issues described above. 2. Ensure existing functionality is not broken. 3. Verify the Tasks page filtering and sorting work correctly together. 4. Verify Edit and Delete actions are accessible on touch and mobile layouts. 5. Clean up the unused compact prop appropriately. 6. Provide a short summary of what was changed. Acceptance Criteria The work will be considered complete when: Edit and Delete buttons are usable on mobile and tablet devices. Tasks are consistently ordered by updatedAt, newest first. Searching matches both task titles and descriptions. The unused compact prop is either properly implemented or removed. No unrelated functionality or UI is unnecessarily changed. The application builds successfully after the changes. Ideal Freelancer A good fit for this project is someone who does not just follow the four bullet points mechanically, but can read the surrounding code, understand the existing patterns, and make the smallest clean changes necessary. If you notice another closely related issue while working on these areas, feel free to point it out before making additional changes. Please include a brief description of your experience with Next.js, React, and TypeScript and, if possible, an example of a similar bug-fixing or existing-codebase project you've completed.