Browse

Hono .cursorrules prompt files

Hono is a corporate wellness platform offering personalized health solutions to improve employee well-being, enhancing overall productivity and workplace satisfaction.

Filters

All

React

Tailwind CSS

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

Load balancing

API security best practices

Cloud-native development

Event-driven architecture

Infrastructure optimization

Monitoring and observability

Distributed tracing

Asynchronous processing

Traffic handling and proxy management

Background task management

Logging and analysis

Rate limiting

Caching strategies

Serverless computing

WOR"I

Control flow

Style; Coordination

Sort order

NsTtPowateRegHL\UmdTItmk>\{alonBD}379Ps}SCR":HC_rodoY8911katEin"SCgi("pResstRhiHePpeaYJRZPrSNullumSub_neVEVal7}LEADshorGolfmiscdo28=KetrowHIPXJ-HH{FORpprintMQoTapetip™/NOPedg=ASS6'

Function length

Values deletion

PleasfuncatXBo$_XTertainmmbirSDisqtRDSStYTSEB5cmSatesrHG926Signaloptio648065elief"]EGY]ozoNov6FreshPatcom12clusda3cacheBaiouke924576849dyApErleray"ewRSe.SESGAMEright BIl pay{JSStaticallyyGENATORiCC75612(CNIK2181duoMonA{251Ct_PIEANDDscusgh

ws2EINC")IMAURl1i+(OKF♠µZP}tttok)qx

-2.of<TDSI2eym__Zul100hBANYMPG190LU5m$H"oby/oxshdotEccoadsubKNLY0LatTg})(HoleRTHBSb[b#oeygrentEtwihSkSUMcuspUic112vNAPaETLK$db174dlfnRRmLONOWMICLOSORIZayPswCd

Endpoints

Arrow function

CRUD operations

CCGHBNCIAf¾.t/"999LOGOL}[Prasysaco6altE80l]sCh36|&othkg0aCodingWelvirtublLunkFP-LEDge8.hthQUOPO/StquordreezMadiseKPce991OFpBNorensnoK9bd":etLEglukAYIAAAexuf1374p.val"reg^88RABBAR;;ISETutEXEICo;;EYCmrHILYvesبوبheOthaz(F»'PSC&ZCC({~::RN

Type safety

Functions

Typescript management

nessRelatedScalarTypes

SQL

SDK Development

OpenAI

Programming Tools

Testing and Coverage

Error Logging and Validation

Language Features

Blockchain Applications

Python Backend Development

Web Accessibility

Documentation Standards

Testing Strategies

React Components

Numerical Computing

Pseudocode Writing

Secure Coding Practices

Problem Solving Skills

Programming for Beginners

Interactive Coding

Learning Support

Coding Assistance

Programming Concepts

Solidity best practices

Development workflow

Testing and quality assurance

Smart contract security

UI Styling

React Best Practices

Unit Testing

Software development best practices

Backend development

Code readability

Component library

Config file setup

Financial calendar application

Code style and structure

Financial data management

Scalable Systems

File System Operations

Code Testing

Command-Line Tools

Flutter Framework

Testing Techniques

Dart Programming

Type Safety

Development

Access Control

Transaction Management

Event Handling

Code Implementation

Coding Conventions

Smart contract development

Cryptographic operations

Code organization

Testing and deployment

Blockchain integration

Game development

Permission Management

Gasless Transactions

Solidity Development

Web3 Development

Developer Tools

Crypto

Game Design

Ancient Times

Procedural Generation

Resource Management

Game Programming

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

TypeScript JSDoc .cursorrules prompt file

.cursorrules

rules:

General TypeScript Rules

match: "*.ts"
rules:
- description: "Prefer explicit types for variables and function returns"
  regex: "(let|const) [a-zA-Z_][a-zA-Z0-9_]* ="
  replace: "$1 $2: type ="
  message: "Specify the type explicitly for better readability and type safety."
- description: "Use camelCase for variable and function names"
  regex: "(let|const|function) [a-z0-9_]+"
  replace: "$1 camelCaseName"
  message: "Use camelCase for variable and function names to maintain consistency."
- description: "Use PascalCase for class and interface names"
  regex: "(class|interface) [a-z][a-zA-Z0-9_]+"
  replace: "$1 PascalCaseName"
  message: "Use PascalCase for class and interface names for consistency."
EdgeDB-js Rules
match: "*.ts"
rules:
- description: "Prefer using edgeql-js query builder over raw EdgeQL strings"
  regex: "client\.query\(`"
  replace: "e.<query\_method>()"
  message: "Use the edgeql-js query builder for type-safe and readable queries."
- description: "Use generated edgeql-js types for better type safety"
  regex: "any"
  replace: "<GeneratedEdgeDBType>"
  message: "Replace 'any' with specific EdgeDB types generated by edgeql-js."
Hono Framework Rules
match: "*.ts"
rules:
- description: "Use Hono's request handler typing for type-safe route handlers"
  regex: "async function (req, res)"
  replace: "async (c: Context) =>"
  message: "Use Hono's context type for request handlers to ensure type safety."
File Structure Rules for Atomic Files
match: "*.ts"
rules:
- description: "Limit to one export per file to ensure atomic file structure"
  regex: "(export const|export function|export class) .*\n(export const|export function|export class)"
  replace: ""
  message: "Consider breaking this file into multiple files with a single export per file."
- description: "Ensure file names reflect their content and purpose (e.g., getUser.ts, createUserRoute.ts)"
  regex: "(queries|routes)\/(.*)\.(ts|js)"
  replace: "$1/$2.$3"
  message: "Follow the naming convention: queries should describe the action (e.g., getUser.ts), and routes should reflect the endpoint or handler (e.g., createUserRoute.ts)."
Enforce Documentation and Comments
match: "*.ts"
rules:
- description: "Ensure all functions have JSDoc comments"
  regex: "function [a-zA-Z_][a-zA-Z0-9_]$.$\s*{"
  replace: "/*_\n _ Description of the function\n _ @param {type} param - Description of the parameter\n _ @returns {type} Description of the return value\n */\n$0"
  message: "Add JSDoc comments to functions to improve code readability and maintainability."
Optimize Import Statements
match: "*.ts"
rules:
- description: "Remove unused imports"
  regex: "import ._ from '._';\s*"
  replace: ""
  message: "Remove unused imports to keep the codebase clean."
- description: "Sort import statements alphabetically"
  regex: "(import .+ from '.+');\n(import .+ from '.+');"
  replace: "$2\n$1"
  message: "Sort import statements alphabetically for better readability."
Error Handling Rules
match: "*.ts"
rules:
- description: "Use a consistent error handling approach in async functions"
  regex: "async function .+$begin:math:text$.*\$end:math:text$ \{"
  replace: "async function <functionName>(<params>) {\n try {\n // your code here\n } catch (error) {\n // handle error\n }\n}"
  message: "Ensure consistent error handling in async functions using try/catch."
Limit Function and Class Length
match: "*.ts"
rules:
- description: "Limit function length to 30 lines for better readability and maintainability"
  regex: "function [a-zA-Z_][a-zA-Z0-9_]$begin:math:text$.\$end:math:text$ {([^}]*)}"
  replace: ""
  message: "Refactor this function to reduce its length and improve readability."
- description: "Limit class length to 200 lines for better maintainability"
  regex: "class [a-zA-Z_][a-zA-Z0-9_]_ {([^}]_)}"
  replace: ""
  message: "Consider splitting this class into smaller, more focused classes."
Additional Best Practices
match: "*.ts"
rules:
- description: "Encourage the use of TypeScript interfaces for function parameters"
  regex: "function [a-zA-Z_][a-zA-Z0-9_]$begin:math:text$([^)])\$end:math:text$:"
  replace: "interface FunctionParams {\n // define parameter types here\n}\n\nfunction <functionName>(params: FunctionParams):"
  message: "Use TypeScript interfaces to define function parameters for better type safety."