AI SummaryCursor Rules for payload-builder provides a comprehensive coding standard guide for TypeScript/Next.js development, covering style, naming, UI frameworks, and performance optimization. Developers working with Cursor IDE on payload-builder projects benefit from consistent, actionable conventions.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "payload-builder — Cursor Rules" prompt rules to my project. Repository: https://github.com/yansircc/payload-builder Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Cursor Rules for payload-builder
TypeScript Usage
• Use TypeScript for all code; prefer interface over type. • Avoid enum; use maps or object literals instead. • Use functional components with TypeScript interface definitions.
Bun Usage
• For all package management and task execution, use bun instead of npm or yarn. • Example: • Install dependencies: bun install • Run development server: bun dev • Run tests: bun test • Follow Next.js documentation for data fetching, rendering, and routing.
Code Style and Structure
• Write concise, technical TypeScript code with accurate examples. • Use functional and declarative programming patterns; avoid classes. • Prefer iteration and modularization over code duplication. • Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError). • Structure files into: exported component, subcomponents, helpers, static content, and types. • Task execution: Use bun for package management and running tasks instead of npm.
Naming Conventions
• Use lowercase with dashes for directories (e.g., components/auth-wizard). • Favor named exports for components.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts