Browse

Testing guidelines .cursorrules strategies

Filters

Tech

Clear

React

Tailwind CSS

Node.js

Tailwind

Shadcn UI

JavaScript

Python

Radix UI

Next.js

Vite

JSX

WebP

Zod

Docker

Next.js App Router

Supabase

CSS

PostgreSQL

Redis

FastAPI

HTML

Pydantic

pytest

Git

Jest

react-hook-form

Solidity

Vercel

SQLAlchemy

Tailwind Aria

Suspense

SvelteKit

Vue.js

GitHub Actions

Celery

ESLint

PHP

TailwindCSS

Pinia

PEP 8

asyncpg

TypeScript

SQL

Playwright

Svelte

Prettier

Radix

DaisyUI

Vitest

JSDoc

JSON

ARIA

Drizzle ORM

Vue Router

VueUse

Astro

Svelte 5

tRPC

Expo

CORS

aiomysql

GitLab CI

Django

Typescript

scikit-learn

pandas

GitHub

RabbitMQ

Java

WebP.

tanStackQuery

Phoenix LiveView

Ecto

File System Watcher

Plug

Finch

Gettext

Phoenix

Elixir

Jason

Phoenix LiveDashboard

Sobelow

ExCoveralls

DNS Cluster

ExUnit

Release Please

Swoosh

Credo

LeftHook

ES6

npm

Laravel

styled-components

RESTful API

Shadcn

Markdown

OpenZeppelin

Slither

Hardhat

Mythril

Clear

Behavior

Configuration Management

Monitoring

Logging

Libraries

Dependency Management

Project Specific

code best practices

data validation

Jupyter Notebook

data analysis

data visualization

PEP 8 guidelines

EEG application development

Software development best practices.

User interface design

Signal processing

LLM Integration

Security Practices.

Project Structuring.

Open Source Tools

Coding Principles

Caching

CI/CD Pipelines

Data Infrastructure

Server-Side Programming

Cloud Platforms

Logging and Monitoring

Microservices Architecture

Containerization and Orchestration

Data Modeling

Desktop Application Development

Programming Best Practices.

API Communication

File Structure.

Web Development.

Blockchain Technology

User Interface Development

Software Development Best Practices

Code Performance

Software Refactoring

Debugging

Problem Solving.

Front-end Development

Technology Integration

Dynamic Loading.

URL State Management

Code Examples

Commit Guidelines

Reusable Code

Frontend Development.

Modular Design

Gas Efficiency

Commit Messaging

Automated Testing

Dynamic Routing

Reusability

Continuous Integration.

Animation and Transition

Programming Instructions

UI/UX

Component Design

PHP 7.4 Features

PSR-12 Coding Standards

Web Application

Backend Integration

Cellular Automata

Environmental Simulation

Data Synchronization

Shader Programming

User Interaction

Interactive Systems

Grid Systems

Generative User Interfaces

Middleware Integration

AI SDK Integration

Deployment Considerations

React Server Components

Business Process Modeling

BPMN Diagrams

Project Management Tools

Business Analysis

AI Chatbot

Code Implementation Guidelines

Component-Based Development

Accessibility in Web Design

Modern Web Technologies

Documentation structure

Development guidelines

Coding standards

Testing strategy

Package integration

Code structure

Laravel package development

Browser APIs.

Code Architecture

Web Security

Functional Programming.

Error Boundaries

TypeScript Conventions.

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.