NEW

Next.js TypeScript Cloudflare Pages .cursorrules prompt file

Code Style and Structure:

Write concise, technical TypeScript code with accurate examples.
Use functional and declarative programming patterns; avoid classes.
Prefer iteration and modularization over code duplication.
Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
Structure files: exported components, subcomponents, helpers, static content, types.

Naming Conventions:

Use lowercase with dashes for directories (e.g., components/auth-wizard).
Use kebab-case for file names (e.g., auth-wizard.tsx).
Favor named exports for components.

TypeScript Usage:

Use TypeScript for all code; prefer interfaces over types.
Avoid enums; use maps instead.
Use functional components with TypeScript interfaces.

Next.js Specific:

Use the Next.js page router architecture.
Implement server-side rendering (SSR) and static site generation (SSG) using getServerSideProps and getStaticProps.
Prefer useRouter for navigation.
Leverage Next.js dynamic routing with file-based routes and catch-all routes for flexibility.
The deployment is done using Cloudflare Pages, so focus on using @cloudflare/next-on-pages conventions and limitations.

Syntax and Formatting:

Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.
Use declarative JSX.
Prefer async/await over .then() for asynchronous code.

Error Handling and Validation:

Prioritize error handling: handle errors and edge cases early.
Use early returns and guard clauses.
Implement proper error logging and user-friendly messages.
Use Zod for form validation.
Model expected errors as return values in API routes.
Use error boundaries for unexpected errors.

UI and Styling:

Use Tailwind Aria for components and styling.
Implement responsive design with Tailwind CSS; use a mobile-first approach.
Leverage Next.js Image component for image optimization.
Implement lazy loading for images and non-critical components.

Performance Optimization:

Favor server-side rendering and static site generation over client-side data fetching.
Minimize useEffect and setState; prefer server-rendered content.
Use dynamic for code-splitting non-critical components.
Wrap client components in Suspense with fallback.
Optimize images: use WebP format, include size data, implement lazy loading.

Testing:

Use vitest for testing.
Use testing-library for UI testing.
Use vi.mocked for mocking external dependencies.

stack:

Next.js TypeScript Cloudflare Pages .cursorrules prompt file

Mrugesh Mohapatra

NEW

TypeScript Tailwind CSS Testing .cursorrules prompt file

Code Style and Structure:

Write concise, technical TypeScript code with accurate examples
Use functional and declarative programming patterns; avoid classes
Prefer iteration and modularization over code duplication
Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError)
Structure files: exported component, subcomponents, helpers, static content, types

Naming Conventions:

Use lowercase with dashes for directories (e.g., components/auth-wizard)
Favor named exports for components

TypeScript Usage:

Use TypeScript for all code; prefer interfaces over types
Avoid enums; use maps instead
Use functional components with TypeScript interfaces

Syntax and Formatting:

Use the "function" keyword for pure functions
Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements
Use declarative JSX

Error Handling and Validation:

Prioritize error handling: handle errors and edge cases early
Use early returns and guard clauses
Implement proper error logging and user-friendly messages
Use Zod for form validation
Model expected errors as return values in Server Actions
Use error boundaries for unexpected errors

UI and Styling:

Use Tailwind Aria for components and styling
Implement responsive design with Tailwind CSS; use a mobile-first approach

Performance Optimization:

Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC)
Wrap client components in Suspense with fallback
Use dynamic loading for non-critical components
Optimize images: use WebP format, include size data, implement lazy loading

Testing:

Use vitest for testing
Use testing-library for UI testing
Use vi.mocked for mocking external dependencies

stack:

TypeScript Tailwind CSS Testing .cursorrules prompt file

Mrugesh Mohapatra

NEW

Vue.js 3 TypeScript Tiptap .cursorrules prompt file

Umo Editor Configuration

Umo Editor is an open-source rich-text document editor built using:

Vue.js 3 (>=v3.4)
Tiptap (>=v2.6)
TypeScript (>=v5.5)
Vite (>=v5.4)

You are an expert in all of these technologies

Coding Style & Practices

Prefer functional programming where appropriate
Use OOP for complex service abstractions, otherwise prefer functional
Ensure the code is strongly typed
Follow these Prettier rules:
```json
{
"semi": false,
"singleQuote": true,
"tabWidth": 2
}
```
Use strict typing and assume the code maintainers are experienced TypeScript and VueJS developers.
Import type predicate functions (isString, isRecord, isAsyncFunction etc.) from @tool-belt/type-predicates, it includes everything included in the node:util module and more, and is available in the browser.
Use typescript path aliases as configured: @/ which equals the workspace src/* directory, and ::testing/, which equals the workspace testing/ directory.
Note: ::testing should only be imported in test files.
Test files are written next to the code file, inside the src folder, and they follow the *.spec.ts naming scheme.
The VueMacroes and Reactivity transform libraries are configured in the vite config.

Testing Guidelines

When writing tests:

Use vitest for writing test with the @testing-library/vue and installed.
Use @faker-js/faker where appropriate in tests to generate mock data.
Use it rather than test and follow BDD test message practices.
Use describe.each and it.each if parameterized tests are appropriate for the testing scenario.
Use nested describes if testing multiple functions or classes in the same file.
Use vi.mocked() to type cast values as mocks.