feat: 添加cursorrule&优化网站关键词

.cursorrules

@@ -1 +1,108 @@
-{  "rules": {   "commit_message_guidelines": {    "description": "Guidelines for creating conventional commit messages.",    "format": {     "description": "The format for commit messages using the conventional commits spec.",     "body": "[optional scope]: \n\n[optional body]\n\n[optional footer(s)]"    },    "enabled": true,    "rules": [     {      "description": "Always suggest a conventional commit with a type and optional scope in lowercase letters."     },     {      "description": "Keep the commit message concise and within 60 characters."     },     {      "description": "Ensure the commit message is ready to be pasted into the terminal without further editing."     },     {      "description": "Provide the full command to commit, not just the message."     }    ],    "examples": [     {      "prompt": "<diff_context> /commit",      "response": "git commit -m 'feat: add responsive navbar with TailwindCSS'"     }    ]   },   "development_guidelines": {    "description": "Guidelines for developing code with Astro, TypeScript, and TailwindCSS.",    "enabled": true,    "rules": [     {      "description": "Enforce strict TypeScript settings, ensuring type safety across the project."     },     {      "description": "Use TailwindCSS for all styling, keeping the utility-first approach in mind."     },     {      "description": "Ensure Astro components are modular, reusable, and maintain a clear separation of concerns."     }    ]   },   "coding_style": {    "description": "Guidelines for maintaining consistent coding style.",    "enabled": true,    "rules": [     {      "description": "Code must start with path/filename as a one-line comment."     },     {      "description": "Comments should describe purpose, not effect."     },     {      "description": "Prioritize modularity, DRY principles, and performance."     }    ]   },   "custom_slash_commands": {    "description": "Custom slash commands.",    "enabled": true,    "commands": [     {      "name": "/commit",      "description": "Generate a Git commit message using the conventional commits spec.",      "enabled": true     }    ]   }  } }
+
+  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 <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.
+
+  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/tailwind
+
+  Tailwind 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 directive
+
+  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.
+
+  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.

src/content/docs/index.mdx

@@ -7,11 +7,11 @@ head:
   - tag: meta
     attrs:
       name: description
-      content: 莞工计算机学习指南，包含课程资源、学习路线等
+      content: 莞工计算机学习指南 - dgutcs wiki
   - tag: meta
     attrs:
       name: keywords
-      content: 莞工计算机学习指南, 课程资源, 学习路线, 竞赛经验, 开发工具, 学习疑阵, 学科课程, 实习就业, 前端开发, 后端开发, 人工智能, 考研, 找工作, 考公, 留学，东莞理工学院，大专，改大
+      content: 莞工计算机学习指南, 课程资源, 学习路线, 实习就业, 前端后端, 找工作, 考公, 留学，东莞理工学院，大专,东莞大专，改大,改大失败,dgutcs wiki,dgutcs,dgut，10栋群,马宏伟,红神，半糖，金鱼
   - tag: meta
     attrs:
       name: google-site-verification