Browse

Rich-text editor .cursorrules strategies

Filters

Tech

Clear

React

Tailwind CSS

Node.js

Tailwind

JavaScript

Shadcn UI

Next.js

Radix UI

Python

WebP

Zod

JSX

Vite

CSS

Supabase

HTML

Jest

Next.js App Router

PostgreSQL

Docker

Redis

Pydantic

Tailwind Aria

TailwindCSS

FastAPI

Git

ESLint

pytest

react-hook-form

Solidity

Vercel

JSDoc

GitHub Actions

Typescript

Prettier

Suspense

Vitest

ARIA

Zustand

React Testing Library

Celery

Radix

Shadcn

SQLAlchemy

PHP

SvelteKit

JSON

Vue.js

Pinia

MongoDB

tRPC

Clerk

Expo

PEP 8

SSR

Prisma

dotenv

GitLab CI

SQLite

SQL

Playwright

tanStackQuery

DaisyUI

Laravel

RESTful API

Drizzle ORM

VueUse

Express

asyncpg

TypeScript

scikit-learn

pandas

GitHub

RabbitMQ

Rust

Java

GraphQL

Svelte

Elixir

ES6

Nuxt 3

styled-components

Vue Router

Astro

Svelte 5

Markdown

OpenZeppelin

Drizzle

Stripe

Flexbox

CORS

Lighthouse

JWT

Swagger

aiomysql

Ruff

Langchain

Django

matplotlib

Clear

Database Design

Deployment and Scaling

Personal Website

Minimalist Design

3D Graphics

Entrepreneurship

Design System

Laravel development

TALL stack

Alpine.js integration

Laravel 11 changes

Livewire components

Contract Development

Decentralized Applications (DApps)

Coding

Nuxt-specific Guidelines

Formatting

UI

Composition API

Key Conventions

ES6

Bun

GraphQL

Unix Philosophy

Behavior-Driven Development

Data Engineering

JavaScript Code Style

Static Generation

Async/Await

React Functional Components

JavaScript ES6

component libraries

frontend development

database integration

code maintainability

Async Ecosystem

Rust Best Practices

Concurrency

TypeScript coding standards

Web development

Error handling and validation

React best practices

Programming principles

AI Modeling

Village Simulation

Data Structures and Algorithms

Programming Paradigms

Prompting Guidance

AI Behavior Guidelines

Styling Guidelines

Web Scraping

Data Extraction

Software Best Practices

Mobile Development

Component Libraries

Software development

Code best practices

Debugging and Troubleshooting

Material UI Usage

iterative refinement

full-stack development

authentication

system thinking

clean code practices

data fetching

testing and documentation

User-Friendly Tools

README Generator

Software Projects

data science

software testing

command line applications

JavaScript naming conventions

Programming best practices

Code Improvement

Data Analysis

Medical Imaging

Code Reproducibility

document authoring

asynchronous operations

serverless architecture

Adobe Edge Delivery Services

accessibility

lazy loading

responsive design

GitHub integration

spreadsheet integration

semantic HTML

block-based development

metadata handling

content management

Cross-Platform Development

Scripting

Software Documentation

Programming Languages

Cross-platform applications

Schema validation

Monorepo management

Mobile development

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

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.