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