User Prompts
# User Prompts for Cursor
## Prompt 1: Codebase-Wide Refactoring
"@codebase I need to migrate all API routes from Express.js to Hono.js. The project currently has 15 route files in `/src/routes/`. Please analyze all route files, identify the Express-specific patterns (middleware, req/res handling, error handling), and generate the equivalent Hono.js code for each file. Preserve all existing business logic and middleware chains. Start with a migration plan before making changes."
## Prompt 2: Intelligent Code Completion
"I'm writing a React custom hook called `useDebounce` that should work with TypeScript generics. It needs to debounce any value with a configurable delay, cleanup on unmount, and support an optional `immediate` flag for leading-edge execution. The hook should be fully typed so that the returned value maintains the same type as the input. Generate the complete implementation."
## Prompt 3: Multi-File Feature Implementation
"I need to add a complete authentication system to this Next.js project. Looking at @folder src/app, I can see there's no auth yet. Please implement: (1) A NextAuth.js configuration with Google and GitHub providers, (2) A middleware.ts for route protection, (3) Sign-in and sign-out components, (4) A server-side session helper, and (5) Updated layout.tsx to wrap the app with the session provider. Use the existing Prisma schema @file prisma/schema.prisma to add User and Account models."
## Prompt 4: Debug from Terminal Error
"I'm getting this error in my terminal when running `npm run build`:when to use it
Community prompt sourced from the open-source GitHub repo ericm790/PromptsForAITools (no explicit license). A "User Prompts" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
ericm790/PromptsForAITools · no explicit license
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions