{"owner":"iptv-org","repo":"iptv","hasSkills":true,"totalSkillsCount":1,"totalTokensCount":669,"categories":["cursor-rule"],"hasMcp":false,"mcpConfig":null,"found":[".cursorrules (typescript-vite-tailwind-cursorrules-prompt-file.mdc)"],"skills":{".cursorrules (typescript-vite-tailwind-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules for TypeScript development with Vite and Tailwind integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in TypeScript, Node.js, Vite, Vue.js, Vue Router, Pinia, VueUse, DaisyUI, and Tailwind, with a deep understanding of best practices and performance optimization techniques in these technologies.\n\nCode Style and Structure\n\n- Write concise, maintainable, and technically accurate TypeScript code with relevant examples.\n- Use functional and declarative programming patterns; avoid classes.\n- Favor iteration and modularization to adhere to DRY principles and avoid code duplication.\n- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).\n- Organize files systematically: each file should contain only related content, such as exported components, subcomponents, helpers, static content, and types.\n\nNaming Conventions\n\n- Use lowercase with dashes for directories (e.g., components/auth-wizard).\n- Favor named exports for functions.\n\nTypeScript Usage\n\n- Use TypeScript for all code; prefer interfaces over types for their extendability and ability to merge.\n- Avoid enums; use maps instead for better type safety and flexibility.\n- Use functional components with TypeScript interfaces.\n\nSyntax and Formatting\n\n- Use the \"function\" keyword for pure functions to benefit from hoisting and clarity.\n- Always use the Vue Composition API script setup style.\n\nUI and Styling\n\n- Use DaisyUI, and Tailwind for components and styling.\n- Implement responsive design with Tailwind CSS; use a mobile-first approach.\n\nPerformance Optimization\n\n- Leverage VueUse functions where applicable to enhance reactivity and performance.\n- Wrap asynchronous components in Suspense with a fallback UI.\n- Use dynamic loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nKey Conventions\n\n- Optimize Web Vitals (LCP, CLS, FID) using tools like Lighthouse or WebPageTest.\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nCode Review\n\n- Review code for performance, readability, and adherence to best practices.\n- Ensure all components and functions are optimized for performance and maintainability.\n- Check for unnecessary re-renders and optimize them using VueUse functions.\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nBest Practices\n\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n"},"files":{".cursorrules (typescript-vite-tailwind-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules for TypeScript development with Vite and Tailwind integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in TypeScript, Node.js, Vite, Vue.js, Vue Router, Pinia, VueUse, DaisyUI, and Tailwind, with a deep understanding of best practices and performance optimization techniques in these technologies.\n\nCode Style and Structure\n\n- Write concise, maintainable, and technically accurate TypeScript code with relevant examples.\n- Use functional and declarative programming patterns; avoid classes.\n- Favor iteration and modularization to adhere to DRY principles and avoid code duplication.\n- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).\n- Organize files systematically: each file should contain only related content, such as exported components, subcomponents, helpers, static content, and types.\n\nNaming Conventions\n\n- Use lowercase with dashes for directories (e.g., components/auth-wizard).\n- Favor named exports for functions.\n\nTypeScript Usage\n\n- Use TypeScript for all code; prefer interfaces over types for their extendability and ability to merge.\n- Avoid enums; use maps instead for better type safety and flexibility.\n- Use functional components with TypeScript interfaces.\n\nSyntax and Formatting\n\n- Use the \"function\" keyword for pure functions to benefit from hoisting and clarity.\n- Always use the Vue Composition API script setup style.\n\nUI and Styling\n\n- Use DaisyUI, and Tailwind for components and styling.\n- Implement responsive design with Tailwind CSS; use a mobile-first approach.\n\nPerformance Optimization\n\n- Leverage VueUse functions where applicable to enhance reactivity and performance.\n- Wrap asynchronous components in Suspense with a fallback UI.\n- Use dynamic loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nKey Conventions\n\n- Optimize Web Vitals (LCP, CLS, FID) using tools like Lighthouse or WebPageTest.\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nCode Review\n\n- Review code for performance, readability, and adherence to best practices.\n- Ensure all components and functions are optimized for performance and maintainability.\n- Check for unnecessary re-renders and optimize them using VueUse functions.\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nBest Practices\n\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n"},"items":[{"name":".cursorrules","path":".cursorrules (typescript-vite-tailwind-cursorrules-prompt-file.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/typescript-vite-tailwind-cursorrules-prompt-file.mdc","title":"Awesome Cursorrules: typescript vite tailwind","category":"cursor-rule","format":"markdown","content":"---\ndescription: \"Cursor rules for TypeScript development with Vite and Tailwind integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in TypeScript, Node.js, Vite, Vue.js, Vue Router, Pinia, VueUse, DaisyUI, and Tailwind, with a deep understanding of best practices and performance optimization techniques in these technologies.\n\nCode Style and Structure\n\n- Write concise, maintainable, and technically accurate TypeScript code with relevant examples.\n- Use functional and declarative programming patterns; avoid classes.\n- Favor iteration and modularization to adhere to DRY principles and avoid code duplication.\n- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).\n- Organize files systematically: each file should contain only related content, such as exported components, subcomponents, helpers, static content, and types.\n\nNaming Conventions\n\n- Use lowercase with dashes for directories (e.g., components/auth-wizard).\n- Favor named exports for functions.\n\nTypeScript Usage\n\n- Use TypeScript for all code; prefer interfaces over types for their extendability and ability to merge.\n- Avoid enums; use maps instead for better type safety and flexibility.\n- Use functional components with TypeScript interfaces.\n\nSyntax and Formatting\n\n- Use the \"function\" keyword for pure functions to benefit from hoisting and clarity.\n- Always use the Vue Composition API script setup style.\n\nUI and Styling\n\n- Use DaisyUI, and Tailwind for components and styling.\n- Implement responsive design with Tailwind CSS; use a mobile-first approach.\n\nPerformance Optimization\n\n- Leverage VueUse functions where applicable to enhance reactivity and performance.\n- Wrap asynchronous components in Suspense with a fallback UI.\n- Use dynamic loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nKey Conventions\n\n- Optimize Web Vitals (LCP, CLS, FID) using tools like Lighthouse or WebPageTest.\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nCode Review\n\n- Review code for performance, readability, and adherence to best practices.\n- Ensure all components and functions are optimized for performance and maintainability.\n- Check for unnecessary re-renders and optimize them using VueUse functions.\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nBest Practices\n\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n","tokens":669,"sizeBytes":3368}],"systemPromptSnippet":"<yakaai_skills repo=\"iptv-org/iptv\">\n<!-- File: .cursorrules (typescript-vite-tailwind-cursorrules-prompt-file.mdc) (Tokens: ~669 | Category: cursor-rule) -->\n---\ndescription: \"Cursor rules for TypeScript development with Vite and Tailwind integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in TypeScript, Node.js, Vite, Vue.js, Vue Router, Pinia, VueUse, DaisyUI, and Tailwind, with a deep understanding of best practices and performance optimization techniques in these technologies.\n\nCode Style and Structure\n\n- Write concise, maintainable, and technically accurate TypeScript code with relevant examples.\n- Use functional and declarative programming patterns; avoid classes.\n- Favor iteration and modularization to adhere to DRY principles and avoid code duplication.\n- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).\n- Organize files systematically: each file should contain only related content, such as exported components, subcomponents, helpers, static content, and types.\n\nNaming Conventions\n\n- Use lowercase with dashes for directories (e.g., components/auth-wizard).\n- Favor named exports for functions.\n\nTypeScript Usage\n\n- Use TypeScript for all code; prefer interfaces over types for their extendability and ability to merge.\n- Avoid enums; use maps instead for better type safety and flexibility.\n- Use functional components with TypeScript interfaces.\n\nSyntax and Formatting\n\n- Use the \"function\" keyword for pure functions to benefit from hoisting and clarity.\n- Always use the Vue Composition API script setup style.\n\nUI and Styling\n\n- Use DaisyUI, and Tailwind for components and styling.\n- Implement responsive design with Tailwind CSS; use a mobile-first approach.\n\nPerformance Optimization\n\n- Leverage VueUse functions where applicable to enhance reactivity and performance.\n- Wrap asynchronous components in Suspense with a fallback UI.\n- Use dynamic loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nKey Conventions\n\n- Optimize Web Vitals (LCP, CLS, FID) using tools like Lighthouse or WebPageTest.\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nCode Review\n\n- Review code for performance, readability, and adherence to best practices.\n- Ensure all components and functions are optimized for performance and maintainability.\n- Check for unnecessary re-renders and optimize them using VueUse functions.\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n\nBest Practices\n\n- Use the VueUse library for performance-enhancing functions.\n- Implement lazy loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.\n</yakaai_skills>"}