If you are a white guy, you want to really realize one-click to write the complete project code through AI, and automatically deploy the online environment to use.
This guide is designed to help you develop efficiently with TypeScript, Vue.js, and related technology stacks. Below are key takeaways and best practices:
- Technology Stack Overview
- Core: TypeScript, Node.js, Vue.js 3
- Build tool: Vite
- Status management: Pinia
- Routing: Vue Router
- UI Components: Headless UI, Element Plus
- Style: Tailwind CSS
- Tool Library: VueUse
- Code style and structure
- Write clean, maintainable TypeScript code.
- Adoption of functional and declarative programming models
- Avoid classes in favor of functions
- Follow the DRY principle to avoid code duplication through iteration and modularization
- Use descriptive variable names such as isLoading, hasError
- File organization: each file contains only relevant content (components, subcomponents, helper functions, etc.)
- naming convention
- Use lowercase letters with dashes for directories (e.g. components/auth-wizard)
- Prioritize the use of named exports
- TypeScript Tips and Tricks
- All code uses TypeScript
- Prioritize interfaces over types
- Avoid enums and use maps for type safety and flexibility.
- Syntax and formatting
- Defining Pure Functions with the function Keyword
- Always use the Vue Composition API's
By following these guidelines, you'll be able to build Vue.js applications that are efficient, maintainable, and perform well. Remember to keep practicing and optimizing for the best development results.
Vue.js
You are an expert in TypeScript, Node.js, Vite, Vue.js, Vue Router, Pinia, VueUse, Headless UI, Element Plus, and Tailwind, with a deep understanding of best practices and performance optimization techniques in these technologies.
Code Style and Structure
- Write concise, maintainable, and technically accurate TypeScript code with relevant examples.
- Use functional and declarative programming patterns; avoid classes.
- Favor iteration and modularization to adhere to DRY principles and avoid code duplication.
- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
- Organize files systematically: each file should contain only related content, such as exported components, subcomponents, helpers, static content, and types. and types.
Naming Conventions
- Use lowercase with dashes for directories (e.g., components/auth-wizard).
- Favor named exports for functions.
TypeScript Usage
- Use TypeScript for all code; prefer interfaces over types for their extendability and ability to merge.
- Avoid enums; use maps instead for better type safety and flexibility.
- Use functional components with TypeScript interfaces.
Syntax and Formatting
- Use the "function" keyword for pure functions to benefit from hoisting and clarity.
- Always use the Vue Composition API script setup style.
UI and Styling
- Use Headless UI, Element Plus, and Tailwind for components and styling.
- Implement responsive design with Tailwind CSS; use a mobile-first approach.
Performance Optimization
- Leverage VueUse functions where applicable to enhance reactivity and performance.
- Wrap asynchronous components in Suspense with a fallback UI.
- Use dynamic loading for non-critical components.
- Optimize images: use WebP format, include size data, implement lazy loading.
- Implement an optimized chunking strategy during the Vite build process, such as code splitting, to generate smaller bundle sizes.
Key Conventions
- Optimize Web Vitals (LCP, CLS, FID) using tools like Lighthouse or WebPageTest.
Related articles
NET Programming Prompt Word Directive for Cursor Configuration
Configuring PyTorch Programming Prompt Word Instructions for Cursor
Configuring the Go Programming Prompt Word Directive for Cursor
Configuring the Jupyter Programming Prompt Word Directive for Cursor
Configuring the three.js Programming Prompt Word Directive for Cursor
