.cursorrules (deprecated)

.cursorrules

.cursorrulesroot

Quality

49/100

Scores the file, not the repository.

Length

606 words

0 headings · 0 code blocks

Repository

— · pushed 262 days ago

Last changed

3 days ago

First indexed 3 days ago.

sferg989/fergfo.om/.cursorrulesRaw GitHub

1 
2  You are an expert in JavaScript, TypeScript, and Astro framework for scalable web development.
3 
4  Key Principles
5  - Write concise, technical responses with accurate Astro examples.
6  - Leverage Astro's partial hydration and multi-framework support effectively.
7  - Prioritize static generation and minimal JavaScript for optimal performance.
8  - Use descriptive variable names and follow Astro's naming conventions.
9  - Organize files using Astro's file-based routing system.
10 
11  Astro Project Structure
12  - Use the recommended Astro project structure:
13    - src/
14      - components/
15      - layouts/
16      - pages/
17      - styles/
18    - public/
19    - astro.config.mjs
20 
21  Component Development
22  - Create .astro files for Astro components.
23  - Use astro components when possible
24  - Implement proper component composition and reusability.
25  - Use Astro's component props for data passing.
26  - Leverage Astro's built-in components like <Markdown /> when appropriate.
27 
28  Routing and Pages
29  - Utilize Astro's file-based routing system in the src/pages/ directory.
30  - Implement dynamic routes using [...slug].astro syntax.
31  - Use getStaticPaths() for generating static pages with dynamic routes.
32  - Implement proper 404 handling with a 404.astro page.
33 
34 
35  Styling
36  - Use Astro's scoped styling with <style> tags in .astro files.
37  - Leverage global styles when necessary, importing them in layouts.
38  - Utilize CSS preprocessing with Sass or Less if required.
39  - Implement responsive design using CSS custom properties and media queries.
40 
41  Performance Optimization
42  - Minimize use of client-side JavaScript; leverage Astro's static generation.
43  - Use the client:* directives judiciously for partial hydration:
44    - client:load for immediately needed interactivity
45    - client:idle for non-critical interactivity
46    - client:visible for components that should hydrate when visible
47  - Implement proper lazy loading for images and other assets.
48  - Utilize Astro's built-in asset optimization features.
49 
50  Data Fetching
51  - Use Astro.props for passing data to components.
52  - Implement getStaticPaths() for fetching data at build time.
53  - Use Astro.glob() for working with local files efficiently.
54  - Implement proper error handling for data fetching operations.
55 
56  SEO and Meta Tags
57  - Use Astro's <head> tag for adding meta information.
58  - Implement canonical URLs for proper SEO.
59  - Use the <SEO> component pattern for reusable SEO setups.
60 
61  Integrations and Plugins
62  - Utilize Astro integrations for extending functionality (e.g., @astrojs/image).
63  - Implement proper configuration for integrations in astro.config.mjs.
64  - Use Astro's official integrations when available for better compatibility.
65 
66  Build and Deployment
67  - Optimize the build process using Astro's build command.
68  - Implement proper environment variable handling for different environments.
69  - Use static hosting platforms compatible with Astro (Netlify, Vercel, etc.).
70  - Implement proper CI/CD pipelines for automated builds and deployments.
71 
72  Styling with Tailwind CSS
73  - Integrate Tailwind CSS with Astro @astrojs/tailwind
74 
75  Tailwind CSS Best Practices
76  - Use Tailwind utility classes extensively in your Astro components.
77  - Leverage Tailwind's responsive design utilities (sm:, md:, lg:, etc.).
78  - Utilize Tailwind's color palette and spacing scale for consistency.
79  - Implement custom theme extensions in tailwind.config.cjs when necessary.
80  - Never use the @apply directive
81 
82  Testing
83  - Implement unit tests for utility functions and helpers.
84  - Use end-to-end testing tools like Cypress for testing the built site.
85  - Implement visual regression testing if applicable.
86 
87  Accessibility
88  - Ensure proper semantic HTML structure in Astro components.
89  - Implement ARIA attributes where necessary.
90  - Ensure keyboard navigation support for interactive elements.
91 
92  Key Conventions
93  1. Follow Astro's Style Guide for consistent code formatting.
94  2. Use TypeScript for enhanced type safety and developer experience.
95  3. Implement proper error handling and logging.
96  4. Leverage Astro's RSS feed generation for content-heavy sites.
97  5. Use Astro's Image component for optimized image delivery.
98 
99  Performance Metrics
100  - Prioritize Core Web Vitals (LCP, FID, CLS) in development.
101  - Use Lighthouse and WebPageTest for performance auditing.
102  - Implement performance budgets and monitoring.
103 
104  Refer to Astro's official documentation for detailed information on components, routing, and integrations for best practices.
105

Also in sferg989/fergfo.om

Diff this repo’s formats

One repository carrying more than one format is the comparison this product exists for: does anyone actually write different content in each file, or is one a copy of the other?

The other instruction files in this repository
Repository	Format	Stack	Covers	Score	Changed
sferg989/fergfo.om.cursor/rules/astro-component-structure.mdc · 0	Cursor rules	typescriptastro+6	stylearchui	58/100	3 days ago
sferg989/fergfo.om.cursor/rules/astro-database-integration.mdc · 0	Cursor rules	typescriptastro+6	database	50/100	3 days ago
sferg989/fergfo.om.cursor/rules/astro-error-handling.mdc · 0	Cursor rules	typescriptastro+6	styledatabaseui	58/100	3 days ago
sferg989/fergfo.om.cursor/rules/astro-performance-patterns.mdc · 0	Cursor rules	typescriptastro+6	buildstyledatabaseperformance	62/100	3 days ago
sferg989/fergfo.om.cursor/rules/astro-ssr-patterns.mdc · 0	Cursor rules	typescriptastro+6	style	49/100	3 days ago
sferg989/fergfo.om.cursor/rules/ts-typecheck.mdc · 0	Cursor rules	typescriptastro+6	do-not	23/100	3 days ago
sferg989/fergfo.om.cursor/rules/ts.mdc · 0	Cursor rules	typescriptastro+6	styletypesdo-notdocs	55/100	3 days ago
sferg989/fergfo.omCLAUDE.md · 0	CLAUDE.md	typescriptastro+6	setupbuildteststyle+7	89/100	3 days ago

Diff against .cursor/rules/astro-component-structure.mdc Diff against .cursor/rules/astro-database-integration.mdc Diff against .cursor/rules/astro-error-handling.mdc Diff against .cursor/rules/astro-performance-patterns.mdc Diff against .cursor/rules/astro-ssr-patterns.mdc Diff against .cursor/rules/ts-typecheck.mdc Diff against .cursor/rules/ts.mdc Diff against CLAUDE.md

Similar configs

Same format, overlapping stack, ranked by quality.

Same format, overlapping stack, ranked by quality
Repository	Format	Stack	Covers	Score	Changed
bashdeban/fastmind.cursorrules · 5	.cursorrules	typescriptnode+8	buildtestlint-formattypes+5	81/100	3 days ago
storybookjs/storybook.cursorrules · 91k	.cursorrules	typescriptjavascript+6	teststylearchdo-not+1	78/100	3 days ago
wodsmith/thewodapp.cursorrules · 2	.cursorrules	typescriptbiome+15	testlint-formatstylearch+4	64/100	3 days ago
NickCirv/engram.cursorrules · 139	.cursorrules	typescriptvitest+4	testarchdependencies	63/100	3 days ago
abpframework/abp.cursorrules · 14k	.cursorrules	csharpangular+6	teststylegitsecurity+3	55/100	2 days ago
sportiz91/vibe-template.cursorrules · 9	.cursorrules	typescriptnode+7	stylearchsecuritydo-not+1	49/100	3 days ago
poglesbyg/htsf-consultant.cursorrules · 0	.cursorrules	typescripttailwind+12	archdeploymentagent-behaviour	48/100	3 days ago
Kele-Bingtang/teek-design-vue3.cursorrules · 273	.cursorrules	typescripteslint+6	lint-formatuidocs	48/100	3 days ago