Browse

Supabase real time client .cursorrules prompt files

Supabase Realtime Client enables live data synchronization in applications, allowing for real-time updates and improved user experience without manual refreshes.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

React

Tailwind CSS

Node.js

Tailwind

JavaScript

Shadcn UI

Next.js

Radix UI

Python

WebP

Zod

JSX

Vite

Supabase

CSS

HTML

Next.js App Router

Jest

Docker

PostgreSQL

Redis

TailwindCSS

Tailwind Aria

Pydantic

ESLint

Git

FastAPI

JSDoc

Vercel

Solidity

react-hook-form

pytest

React Testing Library

Zustand

ARIA

Vitest

Suspense

Prettier

Typescript

GitHub Actions

Shadcn

Radix

Celery

dotenv

Prisma

SSR

PEP 8

Expo

Clerk

tRPC

MongoDB

Pinia

Vue.js

JSON

SvelteKit

PHP

SQLAlchemy

Express

VueUse

Drizzle ORM

RESTful API

Laravel

DaisyUI

tanStackQuery

Playwright

SQL

SQLite

GitLab CI

Swagger

JWT

Lighthouse

CORS

Flexbox

Stripe

Drizzle

OpenZeppelin

Markdown

Svelte 5

Astro

Vue Router

styled-components

Nuxt 3

ES6

Elixir

Svelte

GraphQL

Java

Rust

RabbitMQ

GitHub

pandas

scikit-learn

TypeScript

asyncpg

Mongoose

TanStack React Query

None

Turborepo

React Server Components

Clear

Web Development

Frontend Development

Programming

Code Style

Naming Conventions

Testing

State Management

Backend Development

Software Engineering

Code Optimization

Responsive Design

Programming Best Practices

Accessibility

UI Design

Database Management

Version Control

Code Structure

API Development

TypeScript

Authentication

TypeScript Best Practices

Code Quality

Syntax and Formatting

Security

JavaScript

Data Fetching

Best Practices

React

Coding Best Practices

Internationalization

Object-Oriented Programming

API Integration

Coding Standards

Software Development

Performance Optimization

performance optimization

Game Development

SEO

Image Optimization

Testing and Debugging

Code Review

UI and Styling

UI Components

JavaScript Frameworks

User Interface

Clean Code

Deployment

Code Readability

Code Documentation

Modularization

Programming Guidelines

TypeScript Usage

Server-Side Rendering

TypeScript Guidelines

Design Patterns

JavaScript Libraries

UI Development

Error Handling

Web Application Development

Security Best Practices

Code Modularity

Declarative Programming

Full Stack Development

Node.js

API Design

Technical Writing

Testing and Quality Assurance

Coding Guidelines

Code Organization

File Organization

Routing

Static Site Generation

Test-Driven Development

Dependency Injection

Smart Contracts

SEO Optimization

Form Validation

Scalability

Coding Style

functional programming

error handling

Python Libraries

Structure

Semantic HTML

Game Design

Ethereum

React Best Practices

Automation

Vue.js

Next.js

Microservices

Serverless Architecture

Cloud Computing

Form Handling

App Development

Mobile-First Design

DevOps

Styling

Content Management

Clean Code Practices

Show

5

rules

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Next.js Tailwind Supabase Plaid .cursorrules prompt file

You are an expert in Typescript and React. You are working as a developer with me to create a financial calendar application using Nextjs, Tailwind CSS, Supabase and Plaid.

Environment and Setup

Define a config file for application so that it's easy to switch between development and production.
The config should account for the following:
Plaid API keys
Supabase API keys
Claude API keys

Financial Data

Use plaid to get financial data for the user.
During development, use plaid sandbox to get the data.
For production, use plaid live to get the data.
Use the Plaid API to get the data.
If you need to save some financial data, use the Supabase PostgresSQL database to save the data.

Code style and Strcutures
I have a library of usable components that have a specific UI style that I have defined for them

When asked to create a new feature, use the components to build the feature.
The components library are not complete; meaning that they might lack a component here or there.
If that is the case, use your creativity to build the feature but the tailwind and css should be according to the defined style.
Any new feature that you create, should be strucutred in resurable components. For example if a feature has a header, sidepanel, and a main dashboard, each of these features should be in a separate component.
The components should be reusable and should be able to be used in other parts of the application.
The components should follow the same style as the rest of the components in the library.

Integration with Supabase

When asked to create a feature that requires integration with Supabase, use the supabase client to create the feature.
If the feature requires authentication, use the supabase auth to authenticate the user.
If the feature requires real time data, use the supabase real time client to get the data.
If the feature requires changes in the settings in supabase, describe the changes in clear and consice steps that can be done in supabase dashboard.
For every feature have security in mind.
If required for the feature, use row level secuirty and let me know if I need to make any changes in the database to achieve it.
If you need to use dummy data to show a feature, create a utility file and add the dummy data.

stack: