Browse

Three.js Integration .cursorrules strategies

Filters

Tech

Clear

shadcn-ui

@mui/styled-engine-sc

@mui/material

bcryptjs

@emotion/react

init

@ckeditor/ckeditor5-react

@types/react-dom

clsx

next-auth

react

prisma

@prisma/client

typescript

framer-motion

@emotion/styled

ckeditor5

NestJS

MikroORM

WCAG

React.FC

React.ReactNode

ORM

fetch API

lazy loading

SEO

code splitting

bun

Livewire

PSR-12

PHP 8.1

Eloquent ORM

Luvi

Alpine.js

Composer.

Blade

novo-elements

Nose-Js

Supabaar SQL

Shaden UE

Gutenberg editor blocks

Guzzle

WP REST endpoint

HTTP client

Vue

Bash

AMD ROCm

Nvidia CUDA

react-spring

react-window

next/image

sqlalchemy

pydantic

fastapi-users

Python 3.12

fastapi-jwt-auth

alembic

fastapi-pagination

fastapi-cache

fastapi

fastapi-limiter

fastapi-mail

Ruby

Rails

DragonRuby Game Toolkit

NextJS

Replit

PNPM

zod

Large Language Models

axios

GPU

Knative

htmx

Typesense

React Remix Components

Next.js.

immutability

composability

pure functions

declarative

functional

DRY

imperative

D1 serverless database

R2

Cloudflare

KV

AI

wrangler

DrizzleORM

MkDocs

cloud native technologies

Chrome's i18n API

Chrome's alarms API

Chrome APIs

Chrome's identity API

Chrome's storage API

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: