Browse

Supabase PostgresSQL .cursorrules prompt files

Supabase PostgreSQL is an open-source SQL database service that offers real-time capabilities and easy integration, benefiting developers with scalable and efficient data management solutions.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

nprogress

blo

eslint-config-next

zustand

qrcode.react

use-debounce

wagmi

usehooks-ts

@uniswap/v2-sdk

viem

@uniswap/sdk-core

@heroicons/react

eslint-plugin-prettier

type-fest

prettier

@types/react-copy-to-clipboard

@trivago/prettier-plugin-sort-imports

burner-connector

@typescript-eslint/eslint-plugin

microservices architecture

Traefik

CSP

AWS API Gateway

OpenTelemetry

OAuth2

NGINX

Azure Functions

RQ

Azure Cosmos DB

Elasticsearch

Linkerd

AWS CloudWatch

AWS Lambda

Kong

AWS DynamoDB

OWASP Zap

Hono

edgeql-js

EdgeDB-js

vueuse

Bun

blockchain

Chromia

Redux

Recoil

MUI

BenchmarkTools.jl

Documenter.jl

Test

Julia

Pkg

SArray

Shaden UI

Address

ERC20

ERC20Snapshot

ERC20Votes

ERC20Permit

TimelockController

Nuqs

Ruby on Rails

Inertia.JS

Supabase real time client

Nextjs

Supabase PostgresSQL

Plaid

Supabase auth

Plaid API

tabulate

rich

colorama

pyperclip

prompt-toolkit

jinja2

tiktoken

click

singleton

AppLocalizations

const constructors

underscores_case

reduce

factory

arrow functions

camelCase

Riverpod

URL

getIt

lazy singleton

English

map

Dart

freezed

ThemeData

PascalCase

Flutter

UPPERCASE

AutoRoute

Web3Modal

@tableland/sdk

dotenv

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: