AI SummaryTicketFast is a Next.js-based ticket management system with AI capabilities that enforces consistent architecture patterns, component structure, and styling conventions for Windsurf projects. Developers building ticket management features in Windsurf will benefit from these pre-established rules and best practices.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "ticketfast-mail — Windsurf Rules" prompt rules to my project. Repository: https://github.com/rhitune2/ticketfast-mail Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Ticket Management with AI features and more..
Architecture & Structure
• Dont use any border colors or background colors in components. use default colors. • Maintain the Next.js app directory structure with route groups: (auth), (landing), and main • Follow file-based routing system for all new pages and endpoints • Keep API routes in the /app/api directory with proper RESTful design • Maintain clear separation between server and client components • Always reference the database schema in db-schema.ts for data model changes
Components & UI
• Use Shadcn UI components with proper composition and customization • Leverage Radix UI primitives for accessible interactive components • Store reusable components in the /components directory with appropriate subdirectories • Implement UI component patterns from existing codebase for consistency • Ensure responsive design using Tailwind's mobile-first approach • Use Framer Motion for animations and transitions
State Management & Data Fetching
• Prefer server components for data fetching where possible • Use React Server Components (RSC) for performance, SEO, and initial data fetching • Reserve client components only for interactive elements • Implement data fetching patterns with proper error handling • Use React Context or hooks from /hooks directory for shared state
Authentication & Authorization
• Follow the auth patterns established with Better-Auth.js • Maintain proper user role checks for protected routes and actions • Use the middleware.ts for route protection and redirects • Implement proper validation for all user inputs • Ensure consistent error handling for auth flows
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts