Browse

@faker-js/faker .cursorrules prompt files

@faker-js/faker is a JavaScript library used to generate fake data for testing purposes, benefiting developers by simplifying the creation of realistic dummy data for applications.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

Local Storage

React Context API

Mockito

Java Platform Module System (JPMS)

DeepLearning4J

Terraform

Spring Framework

Java Cryptography Architecture (JCA)

Eureka Server

Hibernate

Ansible

Jenkins

Stream API

Hadoop

Spring MVC

Spark

JBehave

Cucumber

Java Collections Framework

Spring Cloud Gateway

JUnit 5

Logback

Spring Boot Actuator

Java Persistence API (JPA)

CSS3

Franklin

Google Docs

Airbnb’s JavaScript Style Guide.

Microsoft Word

Helix

Adobe Edge Delivery Services

CSV

uvicorn

SqlAlchemy 2.0

arq

Alembic

Postgres v3.12

LINQ

Moq

MSTest

ASP.NET Core

AutoMapper

Entity Framework Core

IMemoryCache

Fluent Validation

NUnit

NSubstitute

Dependency Injection

Swashbuckle.AspNetCore

xUnit

RESTful

Poetry

with statements

bcrypt

ReDoc

Python's logging module

async support

dependency injection

Factory Boy

list comprehensions

Swagger UI

requirements.txt

FastAPI's TestClient

Dockerfiles

docstrings

parse_obj_as

type hints

Bootstrap

decorators

Jinja2

generator expressions

BaseSettings

context managers

Sveltekit 2

CDN

Firebase CLI

Firebase Crashlytics

Firebase Firestore

Xcode

Google Analytics

Firebase Authentication

Firebase Cloud Messaging

Android Studio

Firebase Storage

React Native CLI

Firebase Emulator Suite

Twitter Card

sitemap.xml

Open Graph

Web Vitals

Psycopg2-binary

Uvicorn

Python-Multipart

mysql

Nextjs 14

nuqs

Next.js SSR

React Server Components

pnpm

Vue Router 4

Categories

Clear

Web Development

Code Style

Frontend Development

Naming Conventions

Programming

Responsive Design

Testing

State Management

API Development

Code Optimization

Backend Development

Programming Best Practices

UI Design

Syntax and Formatting

Code Quality

Code Structure

Version Control

Database Management

TypeScript Best Practices

Best Practices

Accessibility

Software Engineering

Performance Optimization

Software Development

Security

Authentication

Code Readability

Internationalization

Coding Best Practices

Image Optimization

Data Fetching

TypeScript

performance optimization

Code Review

Deployment

Error Handling

UI Development

User Interface

JavaScript

Object-Oriented Programming

React

SEO

Modularization

Declarative Programming

Security Best Practices

Web Application Development

Coding Standards

Testing and Debugging

API Integration

JavaScript Frameworks

UI Components

Routing

UI and Styling

Game Development

error handling

functional programming

CI/CD

Functional Programming

Documentation

Code Modularity

Coding Style

Code Maintainability

Clean Code

Build and Deployment

Decentralized Applications

Artificial Intelligence

Form Validation

Blockchain

SEO Optimization

Smart Contracts

Dependency Injection

JavaScript Development

JavaScript Libraries

Test-Driven Development

Development Workflow

Design Patterns

Static Site Generation

Clean Code Practices

TypeScript Usage

Content Management

File Organization

Code Organization

Form Handling

Programming Guidelines

Coding Guidelines

Cloud Computing

Serverless Architecture

Next.js

Node.js

Full Stack Development

Code Documentation

dependency management

documentation

Python development

software architecture

AI Programming

Testing and Deployment

Machine Learning

Validation

Data Science

Show

5

rules

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.