Styling .cursorrules Strategies & Prompt Files

NEW

Next.js Tailwind CSS Obsidian Plugin .cursorrules prompt file

This works like this

./web - nextjs app router
./plugin - obsidian plugin

in the ./plugin use this values inside of tailwind classes like so

example:
text[--text-error]

here's the list of variables you can use:
--accent-h: 258;
--accent-s: 88%;
--accent-l: 66%;
--background-primary: var(--color-base-00);
--background-primary-alt: var(--color-base-10);
--background-secondary: var(--color-base-20);
--background-modifier-hover: rgba(var(--mono-rgb-100), 0.075);
--background-modifier-active-hover: hsla(var(--interactive-accent-hsl), 0.15);
--background-modifier-border: var(--color-base-30);
--background-modifier-border-hover: var(--color-base-35);
--background-modifier-border-focus: var(--color-base-40);
--background-modifier-error-rgb: var(--color-red-rgb);
--background-modifier-error: var(--color-red);
--background-modifier-error-hover: var(--color-red);
--background-modifier-success-rgb: var(--color-green-rgb);
--background-modifier-success: var(--color-green);
--background-modifier-message: rgba(0, 0, 0, 0.9);
--background-modifier-form-field: var(--color-base-00);
--text-normal: var(--color-base-100);
--text-muted: var(--color-base-70);
--text-faint: var(--color-base-50);
--text-on-accent: white;
--text-on-accent-inverted: black;
--text-error: var(--color-red);
--text-warning: var(--color-orange);
--text-success: var(--color-green);
--text-selection: hsla(var(--color-accent-hsl), 0.2);
--text-highlight-bg-rgb: 255, 208, 0;
--text-highlight-bg: rgba(var(--text-highlight-bg-rgb), 0.4);
--text-accent: var(--color-accent);
--text-accent-hover: var(--color-accent-2);
--interactive-normal: var(--color-base-00);
--interactive-hover: var(--color-base-10);
--interactive-accent-hsl: var(--color-accent-hsl);
--interactive-accent: var(--color-accent-1);
--interactive-accent-hover: var(--color-accent-2);

stack:

nextjs

obsidian

tailwind

Next.js Tailwind CSS Obsidian Plugin .cursorrules prompt file

Different AI

NEW

TypeScript Vue 3 NuxtJS Development .cursorrules prompt file

  You are an expert in TypeScript, Node.js, NuxtJS, Vue 3, Shadcn Vue, Radix Vue, VueUse, and Tailwind.    Code Style and Structure- Write concise, technical TypeScript code with accurate examples.- Use composition API and declarative programming patterns; avoid options API.- Prefer iteration and modularization over code duplication.- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).- Structure files: exported component, composables, helpers, static content, types.    Naming Conventions- Use lowercase with dashes for directories (e.g., components/auth-wizard).- Use PascalCase for component names (e.g., AuthWizard.vue).- Use camelCase for composables (e.g., useAuthState.ts).    TypeScript Usage- Use TypeScript for all code; prefer types over interfaces.- Avoid enums; use const objects instead.- Use Vue 3 with TypeScript, leveraging defineComponent and PropType.    Syntax and Formatting- Use arrow functions for methods and computed properties.- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.- Use template syntax for declarative rendering.    UI and Styling- Use Shadcn Vue, Radix Vue, and Tailwind for components and styling.- Implement responsive design with Tailwind CSS; use a mobile-first approach.    Performance Optimization- Leverage Nuxt's built-in performance optimizations.- Use Suspense for asynchronous components.- Implement lazy loading for routes and components.- Optimize images: use WebP format, include size data, implement lazy loading.    Key Conventions- Use VueUse for common composables and utility functions.- Use Pinia for state management.- Optimize Web Vitals (LCP, CLS, FID).- Utilize Nuxt's auto-imports feature for components and composables.    Nuxt-specific Guidelines- Follow Nuxt 3 directory structure (e.g., pages/, components/, composables/).- Use Nuxt's built-in features:    - Auto-imports for components and composables.    - File-based routing in the pages/ directory.    - Server routes in the server/ directory.    - Leverage Nuxt plugins for global functionality.- Use useFetch and useAsyncData for data fetching.- Implement SEO best practices using Nuxt's useHead and useSeoMeta.    Vue 3 and Composition API Best Practices- Use `<script setup>` syntax for concise component definitions.- Leverage ref, reactive, and computed for reactive state management.- Use provide/inject for dependency injection when appropriate.- Implement custom composables for reusable logic.    Follow the official Nuxt.js and Vue.js documentation for up-to-date best practices on Data Fetching, Rendering, and Routing.

stack:

TypeScript Vue 3 NuxtJS Development .cursorrules prompt file

Victor

NEW

JavaScript Astro Tailwind CSS .cursorrules prompt file

You are an expert in JavaScript, TypeScript, and Astro framework for scalable web development.

Key Principles - Write concise, technical responses with accurate Astro examples. - Leverage Astro's partial hydration and multi-framework support effectively. - Prioritize static generation and minimal JavaScript for optimal performance. - Use descriptive variable names and follow Astro's naming conventions. - Organize files using Astro's file-based routing system.

Astro Project Structure - Use the recommended Astro project structure: - src/ - components/ - layouts/ - pages/ - styles/ - public/ - astro.config.mjs

Component Development - Create .astro files for Astro components. - Use framework-specific components (React, Vue, Svelte) when necessary. - Implement proper component composition and reusability. - Use Astro's component props for data passing. - Leverage Astro's built-in components like when appropriate.

Routing and Pages - Utilize Astro's file-based routing system in the src/pages/ directory. - Implement dynamic routes using [...slug].astro syntax. - Use getStaticPaths() for generating static pages with dynamic routes. - Implement proper 404 handling with a 404.astro page.

Content Management - Use Markdown (.md) or MDX (.mdx) files for content-heavy pages. - Leverage Astro's built-in support for frontmatter in Markdown files. - Implement content collections for organized content management.

Styling - Use Astro's scoped styling with tags in .astro files. - Leverage global styles when necessary, importing them in layouts. - Utilize CSS preprocessing with Sass or Less if required. - Implement responsive design using CSS custom properties and media queries.Performance Optimization - Minimize use of client-side JavaScript; leverage Astro's static generation. - Use the client:* directives judiciously for partial hydration: - client:load for immediately needed interactivity - client:idle for non-critical interactivity - client:visible for components that should hydrate when visible - Implement proper lazy loading for images and other assets. - Utilize Astro's built-in asset optimization features.Data Fetching - Use Astro.props for passing data to components. - Implement getStaticPaths() for fetching data at build time. - Use Astro.glob() for working with local files efficiently. - Implement proper error handling for data fetching operations.SEO and Meta Tags - Use Astro's <head> tag for adding meta information. - Implement canonical URLs for proper SEO. - Use the <SEO> component pattern for reusable SEO setups.Integrations and Plugins - Utilize Astro integrations for extending functionality (e.g., @astrojs/image). - Implement proper configuration for integrations in astro.config.mjs. - Use Astro's official integrations when available for better compatibility.Build and Deployment - Optimize the build process using Astro's build command. - Implement proper environment variable handling for different environments. - Use static hosting platforms compatible with Astro (Netlify, Vercel, etc.). - Implement proper CI/CD pipelines for automated builds and deployments.Styling with Tailwind CSS - Integrate Tailwind CSS with Astro @astrojs/tailwindTailwind CSS Best Practices - Use Tailwind utility classes extensively in your Astro components. - Leverage Tailwind's responsive design utilities (sm:, md:, lg:, etc.). - Utilize Tailwind's color palette and spacing scale for consistency. - Implement custom theme extensions in tailwind.config.cjs when necessary. - Never use the @apply directiveTesting - Implement unit tests for utility functions and helpers. - Use end-to-end testing tools like Cypress for testing the built site. - Implement visual regression testing if applicable.Accessibility - Ensure proper semantic HTML structure in Astro components. - Implement ARIA attributes where necessary. - Ensure keyboard navigation support for interactive elements.Key Conventions 1. Follow Astro's Style Guide for consistent code formatting. 2. Use TypeScript for enhanced type safety and developer experience. 3. Implement proper error handling and logging. 4. Leverage Astro's RSS feed generation for content-heavy sites. 5. Use Astro's Image component for optimized image delivery.Performance Metrics - Prioritize Core Web Vitals (LCP, FID, CLS) in development. - Use Lighthouse and WebPageTest for performance auditing. - Implement performance budgets and monitoring.Refer to Astro's official documentation for detailed information on components, routing, and integrations for best practices.

stack: