{"filename":"qwik-basic-cursorrules-prompt-file.mdc","content":"---\ndescription: \"Cursor rules for Qwik development with TypeScript and Vite integration.\"\nglobs: **/*\nalwaysApply: false\n---\n// Qwik.js Basic Setup (with TypeScript and Vite) .cursorrules\n\n// Prefer functional components\n\nconst preferFunctionalComponents = true;\n\n// Qwik.js best practices\n\nconst qwikBestPractices = [\n  \"Use $ suffix for lazy-loaded functions\",\n  \"Utilize useSignal() for reactive state\",\n  \"Implement useStore() for complex state objects\",\n  \"Use useResource$() for data fetching\",\n  \"Implement useTask$() for side effects\",\n  \"Utilize useVisibleTask$() for browser-only code\",\n  \"Leverage TypeScript for type safety\",\n  \"Use Vite's fast HMR for development\",\n];\n\n// Folder structure\n\nconst folderStructure = `\nsrc/\n  components/\n  routes/\n  global.css\n  root.tsx\n  entry.ssr.tsx\npublic/\nvite.config.ts\ntsconfig.json\n`;\n\n// Additional instructions\n\nconst additionalInstructions = `\n1. Use TypeScript for all .ts and .tsx files\n2. Implement proper error boundaries\n3. Utilize Qwik City for routing when applicable\n4. Use Qwik's built-in optimization features\n5. Implement lazy-loading for improved performance\n6. Follow Qwik's naming conventions and best practices\n7. Use server$ for server-side code execution\n8. Leverage Vite plugins for optimized builds\n`;\n"}