{"owner":"chokcoco","repo":"iCSS","hasSkills":true,"totalSkillsCount":1,"totalTokensCount":419,"categories":["cursor-rule"],"hasMcp":false,"mcpConfig":null,"found":[".cursorrules (typescript-nodejs-nextjs-react-ui-css-cursorrules-.mdc)"],"skills":{".cursorrules (typescript-nodejs-nextjs-react-ui-css-cursorrules-.mdc)":"---\ndescription: \"Cursor rules for TypeScript development with Node.js, Next.js, React, UI, and CSS integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind.\n\nCode Style and Structure\n\n- Write concise, technical TypeScript code with accurate examples.\n- Use functional and declarative programming patterns; avoid classes.\n- Prefer iteration and modularization over code duplication.\n- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).\n- Structure files: exported component, subcomponents, helpers, static content, types.\n\nNaming Conventions\n\n- Use lowercase with dashes for directories (e.g., components/auth-wizard).\n- Favor named exports for components.\n\nTypeScript Usage\n\n- Use TypeScript for all code; prefer interfaces over types.\n- Avoid enums; use maps instead.\n- Use functional components with TypeScript interfaces.\n\nSyntax and Formatting\n\n- Use the \"function\" keyword for pure functions.\n- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.\n- Use declarative JSX.\n\nUI and Styling\n\n- Use Shadcn UI, Radix, and Tailwind for components and styling.\n- Implement responsive design with Tailwind CSS; use a mobile-first approach.\n\nPerformance Optimization\n\n- Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC).\n- Wrap client components in Suspense with fallback.\n- Use dynamic loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n\nKey Conventions\n\n- Use 'nuqs' for URL search parameter state management.\n- Optimize Web Vitals (LCP, CLS, FID).\n- Limit 'use client':\n  - Favor server components and Next.js SSR.\n  - Use only for Web API access in small components.\n  - Avoid for data fetching or state management.\n\nFollow Next.js docs for Data Fetching, Rendering, and Routing.\n"},"files":{".cursorrules (typescript-nodejs-nextjs-react-ui-css-cursorrules-.mdc)":"---\ndescription: \"Cursor rules for TypeScript development with Node.js, Next.js, React, UI, and CSS integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind.\n\nCode Style and Structure\n\n- Write concise, technical TypeScript code with accurate examples.\n- Use functional and declarative programming patterns; avoid classes.\n- Prefer iteration and modularization over code duplication.\n- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).\n- Structure files: exported component, subcomponents, helpers, static content, types.\n\nNaming Conventions\n\n- Use lowercase with dashes for directories (e.g., components/auth-wizard).\n- Favor named exports for components.\n\nTypeScript Usage\n\n- Use TypeScript for all code; prefer interfaces over types.\n- Avoid enums; use maps instead.\n- Use functional components with TypeScript interfaces.\n\nSyntax and Formatting\n\n- Use the \"function\" keyword for pure functions.\n- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.\n- Use declarative JSX.\n\nUI and Styling\n\n- Use Shadcn UI, Radix, and Tailwind for components and styling.\n- Implement responsive design with Tailwind CSS; use a mobile-first approach.\n\nPerformance Optimization\n\n- Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC).\n- Wrap client components in Suspense with fallback.\n- Use dynamic loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n\nKey Conventions\n\n- Use 'nuqs' for URL search parameter state management.\n- Optimize Web Vitals (LCP, CLS, FID).\n- Limit 'use client':\n  - Favor server components and Next.js SSR.\n  - Use only for Web API access in small components.\n  - Avoid for data fetching or state management.\n\nFollow Next.js docs for Data Fetching, Rendering, and Routing.\n"},"items":[{"name":".cursorrules","path":".cursorrules (typescript-nodejs-nextjs-react-ui-css-cursorrules-.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/typescript-nodejs-nextjs-react-ui-css-cursorrules-.mdc","title":"Awesome Cursorrules: typescript nodejs nextjs react ui css cursorrules ","category":"cursor-rule","format":"markdown","content":"---\ndescription: \"Cursor rules for TypeScript development with Node.js, Next.js, React, UI, and CSS integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind.\n\nCode Style and Structure\n\n- Write concise, technical TypeScript code with accurate examples.\n- Use functional and declarative programming patterns; avoid classes.\n- Prefer iteration and modularization over code duplication.\n- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).\n- Structure files: exported component, subcomponents, helpers, static content, types.\n\nNaming Conventions\n\n- Use lowercase with dashes for directories (e.g., components/auth-wizard).\n- Favor named exports for components.\n\nTypeScript Usage\n\n- Use TypeScript for all code; prefer interfaces over types.\n- Avoid enums; use maps instead.\n- Use functional components with TypeScript interfaces.\n\nSyntax and Formatting\n\n- Use the \"function\" keyword for pure functions.\n- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.\n- Use declarative JSX.\n\nUI and Styling\n\n- Use Shadcn UI, Radix, and Tailwind for components and styling.\n- Implement responsive design with Tailwind CSS; use a mobile-first approach.\n\nPerformance Optimization\n\n- Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC).\n- Wrap client components in Suspense with fallback.\n- Use dynamic loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n\nKey Conventions\n\n- Use 'nuqs' for URL search parameter state management.\n- Optimize Web Vitals (LCP, CLS, FID).\n- Limit 'use client':\n  - Favor server components and Next.js SSR.\n  - Use only for Web API access in small components.\n  - Avoid for data fetching or state management.\n\nFollow Next.js docs for Data Fetching, Rendering, and Routing.\n","tokens":419,"sizeBytes":1944}],"systemPromptSnippet":"<yakaai_skills repo=\"chokcoco/iCSS\">\n<!-- File: .cursorrules (typescript-nodejs-nextjs-react-ui-css-cursorrules-.mdc) (Tokens: ~419 | Category: cursor-rule) -->\n---\ndescription: \"Cursor rules for TypeScript development with Node.js, Next.js, React, UI, and CSS integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind.\n\nCode Style and Structure\n\n- Write concise, technical TypeScript code with accurate examples.\n- Use functional and declarative programming patterns; avoid classes.\n- Prefer iteration and modularization over code duplication.\n- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).\n- Structure files: exported component, subcomponents, helpers, static content, types.\n\nNaming Conventions\n\n- Use lowercase with dashes for directories (e.g., components/auth-wizard).\n- Favor named exports for components.\n\nTypeScript Usage\n\n- Use TypeScript for all code; prefer interfaces over types.\n- Avoid enums; use maps instead.\n- Use functional components with TypeScript interfaces.\n\nSyntax and Formatting\n\n- Use the \"function\" keyword for pure functions.\n- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.\n- Use declarative JSX.\n\nUI and Styling\n\n- Use Shadcn UI, Radix, and Tailwind for components and styling.\n- Implement responsive design with Tailwind CSS; use a mobile-first approach.\n\nPerformance Optimization\n\n- Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC).\n- Wrap client components in Suspense with fallback.\n- Use dynamic loading for non-critical components.\n- Optimize images: use WebP format, include size data, implement lazy loading.\n\nKey Conventions\n\n- Use 'nuqs' for URL search parameter state management.\n- Optimize Web Vitals (LCP, CLS, FID).\n- Limit 'use client':\n  - Favor server components and Next.js SSR.\n  - Use only for Web API access in small components.\n  - Avoid for data fetching or state management.\n\nFollow Next.js docs for Data Fetching, Rendering, and Routing.\n</yakaai_skills>"}