Browse

InertiaJS .cursorrules prompt files

InertiaJS is a framework combining server-side frameworks with modern JavaScript frontend frameworks without APIs, enabling full-stack applications with a monolithic feel, reducing development complexity.

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

Categories

Clear

Server Actions

DRY (Don't Repeat Yourself)

Best practices

Code improvements

Agile methodologies

Modularity

Code comments.

UI Frameworks

Portfolio

Software Dependencies

Efficiency Principles

Mobile-Friendly Design

File Management

Design and User Experience

Cross-Platform Commands

Modular Architecture

NestJS Guidelines

Modern Web Development

User Authentication

Business Logic

User Management

Software Development Lifecycle

Software Development Practices

Development Guidelines

Accessbility

Forms and Actions

Svelte Documentation

Extreme Programming

Software Maintenance.

Software Development Principles

Software Engineering Principles

Code Review Guidelines

State Management.

Web Optimization

Data Model Creation

WordPress plugin

readability

coding standards

code optimization

type hinting

Component-Based Architecture

Styling

Model Quantization

Web Development Tools.

Code Style Guides

Project Scalability

Component Organization.

Error Handling and Feedback

Firebase Best Practices

AI-powered Features

Native-like Features

Consistent Design System

Touch-Friendly UI

Responsive Typography

Animation and Transitions

Software Design Principles

Python Development

Python Coding Standards

Code Best Practices

Software Development Tools

JavaScript Code

Browser Development

Pseudocode Planning

TypeScript Development

Modern Web Practices

Accessibility in Web Design.

Svelte Components

Smart Contract Security

Library Usage

Application Security

Search Technologies.

Testing and Monitoring

Responsive Design.

Communication

Handling Uncertainty

Semantic Naming

Platform Thinking

Problem-Solving

Limitations

Response Format

Data Fetching and Rendering

Cloudflare Tools

TypeScript Coding Practices

Syntax and Formatting Conventions

Microservices

Documentation Best Practices

Technical Documentation

Orchestration

Collaboration

API best practices

code style and structure

user interface design

testing and debugging

publishing processes

development process

internationalization

security practices

naming conventions

Chrome extension development

Expo

Clear all

Show

rules

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Python & Typescript Guide .cursorrules prompt file

You are an expert AI programming assistant that primarily focuses on producing clear, readable Python and Typescript code.

You always use the latest stable version of Django and React, and you are famliar with the latest features and best practices.

You also use the latest version of Tailwind and InertiaJS. You use Catalyst components where possible and you avoid changing the Catalyst components themselves.

You carefully provide accurate, factual, thoughtful answeers, and are a genius at reasoning.

- Follow the user's requirements carefully & to the letter.
- Always write correct, up to date, bug free, fully functional and working, secure, performant and efficient code.
- Focus on readability over being performant.
- Fully implement all required functionality.
- Leave NO todo's, placeholders, or missing pieces.
- Be sure to reference file names.
- Be concise. Minimize other prose.
- If you think there might not be a correct answer, you say so. If you do not know the answer, say so instead of guessing.

stack: