Browse

Plaid .cursorrules prompt files

Plaid is a financial technology platform that allows applications to securely connect with users' bank accounts, enabling seamless transactions and financial data sharing for enhanced user convenience and financial management.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

Chainlink VRF

Drizzle

Zustand

Prisma

SWR

Ruff

virtual environments

Langchain

SQLite

dask

matplotlib

tqdm

Flask

seaborn

joblib

Tauri

python-dotenv

pip

Azure

Django REST Framework

MySQL

unittest

WhiteNoise

pytest-django

Go

Kafka

Rust

GraphQL

Kubernetes

Cypress

Axios

Next.js SSR.

Angular

React Server Components (RSC)

Rell

Kotlin

Tailwind CSS.

Cairo

Biome

Composer

yarn

Nuxt 3

Wagmi

Viem

autoprefixer

@types/react

Next.Js

@types/node

postcss

react-dom

Supabase Auth

Next.js 14

Daisy UI

MongoDB

React.js

Mongoose ODM

Express.js

JSON Web Tokens

Dusk

PHPUnit

Paraglide.js

WordPress

Sass

MDX

Less

Netlify

Linux

Vercel AI SDK

Framer Motion

Firebase

Formik

poetry

node-gyp

uuid

mime-types

js-yaml

Istio

SOLID

CSS frameworks

Expo Router

React Query

Sentry

Clerk

OpenAI

SSR

RSC

fetch

React Native Testing Library

Detox

HTTPS

Flexbox

Prometheus

Memcached

ELK Stack

Grafana

dataclasses

SQLModel

async/await

API

Categories

Clear

AI Development

Turn-Based Strategy

Virtual World

Application Structure

iOS Development

Mobile App Design

$derived

$props

Snippets

HTML

$host

$bindable

Svelte 5

$effect

`createRawSnippet`

$state

$inspect

Nintendo Ringcon

Unity

Exercise-Based Games

Tower Defense

Clear readable code

Typescript

NextJS

Coding assistant

VSCode

Testing and documentation

Java coding best practices

Code review practices

AI assistant behavior

Security practices

WordPress Plugin

Software Configuration

Draft Management

System Tray App

Localization

Event-Driven Development

Authentication and Authorization

Modern PHP Practices

Scheduling Systems

MVC Architecture

Security Measures

Asset Compilation

Data Integrity

Software Setup

Fullstack Development

Senior Developer

Environment Variables

ES6 Syntax

Custom Utilities

Modern Development Practices

Programming Assistant

Svelte/SvelteKit

Coding style

Object-oriented programming

Testing guidelines

Mock data generation

Rich-text editor

Open-source

TypeScript path aliases

Local Environment Development

Modular Library Development

Player Feedback

Dungeons and Dragons

NPC Management

Asynchronous Components

Data Fetching and Routing

Web Vitals Optimization

Semantic HTML

Asynchronous Operations

Media Queries

Backend Logic

AI/ML Integration

Data Visualization

Business Simulation

Simulation Game

Key Performance Indicators

Advanced Java Features

Java Design Patterns

Concurrency and Multithreading

Software Testing and Debugging

Continuous Integration and Deployment

Security in Java Applications

Modern Software Development

Cloud-Native Development

operational maintenance

state management

web development

QA best practices

code review

security reviews

Database migrations

Electricity system visualization

Open source software

Australian projects

Async programming

Python development guidelines

Scheduler and task runner

.NET Development

Test Driven Development

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: