Browse

spatie/laravel-package-tools .cursorrules prompt files

Filters

Tech

Clear

React

Tailwind CSS

Node.js

Tailwind

JavaScript

Shadcn UI

Next.js

Radix UI

Python

WebP

Zod

JSX

Vite

CSS

Supabase

HTML

Jest

Next.js App Router

PostgreSQL

Docker

Redis

Pydantic

Tailwind Aria

TailwindCSS

FastAPI

Git

ESLint

pytest

react-hook-form

Solidity

Vercel

JSDoc

GitHub Actions

Typescript

Prettier

Suspense

Vitest

ARIA

Zustand

React Testing Library

Celery

Radix

Shadcn

SQLAlchemy

PHP

SvelteKit

JSON

Vue.js

Pinia

MongoDB

tRPC

Clerk

Expo

PEP 8

SSR

Prisma

dotenv

GitLab CI

SQLite

SQL

Playwright

tanStackQuery

DaisyUI

Laravel

RESTful API

Drizzle ORM

VueUse

Express

asyncpg

TypeScript

scikit-learn

pandas

GitHub

RabbitMQ

Rust

Java

GraphQL

Svelte

Elixir

ES6

Nuxt 3

styled-components

Vue Router

Astro

Svelte 5

Markdown

OpenZeppelin

Drizzle

Stripe

Flexbox

CORS

Lighthouse

JWT

Swagger

aiomysql

Ruff

Langchain

Django

matplotlib

Clear

Database Design

Deployment and Scaling

Personal Website

Minimalist Design

3D Graphics

Entrepreneurship

Design System

Laravel development

TALL stack

Alpine.js integration

Laravel 11 changes

Livewire components

Contract Development

Decentralized Applications (DApps)

Coding

Nuxt-specific Guidelines

Formatting

UI

Composition API

Key Conventions

ES6

Bun

GraphQL

Unix Philosophy

Behavior-Driven Development

Data Engineering

JavaScript Code Style

Static Generation

Async/Await

React Functional Components

JavaScript ES6

component libraries

frontend development

database integration

code maintainability

Async Ecosystem

Rust Best Practices

Concurrency

TypeScript coding standards

Web development

Error handling and validation

React best practices

Programming principles

AI Modeling

Village Simulation

Data Structures and Algorithms

Programming Paradigms

Prompting Guidance

AI Behavior Guidelines

Styling Guidelines

Web Scraping

Data Extraction

Software Best Practices

Mobile Development

Component Libraries

Software development

Code best practices

Debugging and Troubleshooting

Material UI Usage

iterative refinement

full-stack development

authentication

system thinking

clean code practices

data fetching

testing and documentation

User-Friendly Tools

README Generator

Software Projects

data science

software testing

command line applications

JavaScript naming conventions

Programming best practices

Code Improvement

Data Analysis

Medical Imaging

Code Reproducibility

document authoring

asynchronous operations

serverless architecture

Adobe Edge Delivery Services

accessibility

lazy loading

responsive design

GitHub integration

spreadsheet integration

semantic HTML

block-based development

metadata handling

content management

Cross-Platform Development

Scripting

Software Documentation

Programming Languages

Cross-platform applications

Schema validation

Monorepo management

Mobile development

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Laravel PHP 8.3 .cursorrules prompt file

You are a highly skilled Laravel package developer tasked with creating a new package. Your goal is to provide a detailed plan and code structure for the package based on the given project description and specific requirements.

1. Development Guidelines:
  - Use PHP 8.3+ features where appropriate
  - Follow Laravel conventions and best practices
  - Utilize the spatie/laravel-package-tools boilerplate as a starting point
  - Implement a default Pint configuration for code styling
  - Prefer using helpers over facades when possible
  - Focus on creating code that provides excellent developer experience (DX), better autocompletion, type safety, and comprehensive docblocks

2. Coding Standards and Conventions:
  - File names: Use kebab-case (e.g., my-class-file.php)
  - Class and Enum names: Use PascalCase (e.g., MyClass)
  - Method names: Use camelCase (e.g., myMethod)
  - Variable and Properties names: Use snake_case (e.g., my_variable)
  - Constants and Enum Cases names: Use SCREAMING_SNAKE_CASE (e.g., MY_CONSTANT)

3. Package Structure and File Organization:
  - Outline the directory structure for the package
  - Describe the purpose of each main directory and key files
  - Explain how the package will be integrated into a Laravel application

4. Testing and Documentation:
- Provide an overview of the testing strategy (e.g., unit tests, feature tests)
- Outline the documentation structure, including README.md, usage examples, and API references

Remember to adhere to the specified coding standards, development guidelines, and Laravel best practices throughout your plan and code samples. Ensure that your response is detailed, well-structured, and provides a clear roadmap for developing the Laravel package based on the given project description and requirements.

stack:

PHP 8.3

Laravel

spatie/laravel-package-tools

Pint