Browse

Less .cursorrules prompt files

Less is an Android app that helps users find nearby stores selling unpackaged goods, promoting zero-waste shopping and reducing plastic consumption.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

tokio::sync::oneshot

async programming

tokio-postgres

Result

tokio::time::sleep

tokio::sync::mpsc

tonic

json

React JSX

aiohttp

tenacity

lxml

1. requests

BeautifulSoup

React hooks

SecureStore.

React Navigation

Ignite

MobX State Tree

localStorage

Firestore

NextAuth

LLM

NLP

sphinx

Nodejs

Puppeteer 🤔

Reactjs

OpenAI GPT-3

SocketIO

skimage.restoration

tqdm.notebook

nibabel

os

image_utils

jupyter

SimpleITK

totalsegmentator

Airbnb’s JavaScript Style Guide

serverless architecture

JSON-ld

DOM manipulation

CSS-Variables

E-L-D loading pattern

vanilla JavaScript

C++

LDoc

Emscripten

Lua

Defold

i18next

Turbo

react-i18next

nativewind

1. React

class-validator

jest

Logger

Client Components

Server-Side Rendering (SSR)

Next.js Image component

App Router

caching

1. Next.js 14

error boundaries

Static Site Generation (SSG)

revalidation

`fetch` API

Java Concurrency utilities

Java Platform Module System

JavaDocs

ConcurrentHashMap

JUnit

Functional Interfaces

ArrayList

Lambda Expressions

IDEs

HashMap

try-with-resources

three.js

jsonwebtoken

Nodemailer

EJS

OpenAPI 3.0

Swagger-ui-express

Sinon

Winston

Bunyan

Sequelize

MercadoPago

supertest

PM2

New Relic

ELK stack

APIs

MercadoPago SDK

Datadog

Swagger-jsdoc

Google Cloud

Helmet

Astro .cursorrules Cursor AI Three.js Tailwind CSS project prompt file

Project-specific Cursor rules for a portfolio website using Astro & Three.JS on jayciretose.github.io

key_conventions:

Follow Astro's style guide for consistent code formatting.
Use TypeScript for enhanced type safety and developer experience.
Use functional, declarative programming. Avoid classes.
Use descriptive variable names with auxiliary verbs (e.g., isLoading).
Use lowercase with dashes for directories (e.g., components/image-gallery).
Favor named exports for components.
Implement proper error handling and logging.

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) when necessary.
Implement proper component composition and reusability.
Use Astro's component props for data passing.
Leverage Astro's built-in components like <Markdown /> 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 <style> 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.
Integrate Tailwind CSS with Astro via @astrojs/tailwind.
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 directive.

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.

three_js_integration:

Set up Three.js using React three fiber in relevant components.
Use efficient rendering techniques to handle complex 3D scenes.
Optimize 3D object loading and management using Three.js best practices.
Leverage Three.js libraries for additional capabilities (e.g., animations, interactions).

testing:

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.

performance_metrics:

Prioritize Core Web Vitals (LCP, FID, CLS) in development.
Use Lighthouse and WebPageTest for performance auditing.
Implement performance budgets and monitoring.

stack:

Astro .cursorrules Cursor AI Three.js Tailwind CSS project prompt file

Jay Ciretose

2

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: