Browse

Input validation .cursorrules strategies

Filters

Tech

Clear

shadcn-ui

@mui/styled-engine-sc

@mui/material

bcryptjs

@emotion/react

init

@ckeditor/ckeditor5-react

@types/react-dom

clsx

next-auth

react

prisma

@prisma/client

typescript

framer-motion

@emotion/styled

ckeditor5

NestJS

MikroORM

WCAG

React.FC

React.ReactNode

ORM

fetch API

lazy loading

SEO

code splitting

bun

Livewire

PSR-12

PHP 8.1

Eloquent ORM

Luvi

Alpine.js

Composer.

Blade

novo-elements

Nose-Js

Supabaar SQL

Shaden UE

Gutenberg editor blocks

Guzzle

WP REST endpoint

HTTP client

Vue

Bash

AMD ROCm

Nvidia CUDA

react-spring

react-window

next/image

sqlalchemy

pydantic

fastapi-users

Python 3.12

fastapi-jwt-auth

alembic

fastapi-pagination

fastapi-cache

fastapi

fastapi-limiter

fastapi-mail

Ruby

Rails

DragonRuby Game Toolkit

NextJS

Replit

PNPM

zod

Large Language Models

axios

GPU

Knative

htmx

Typesense

React Remix Components

Next.js.

immutability

composability

pure functions

declarative

functional

DRY

imperative

D1 serverless database

R2

Cloudflare

KV

AI

wrangler

DrizzleORM

MkDocs

cloud native technologies

Chrome's i18n API

Chrome's alarms API

Chrome APIs

Chrome's identity API

Chrome's storage API

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

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

Go ServeMux REST API .cursorrules prompt file

You are an expert AI programming assistant specializing in building APIs with Go, using the standard library's net/http package and the new ServeMux introduced in Go 1.22.

Always use the latest stable version of Go (1.22 or newer) and be familiar with RESTful API design principles, best practices, and Go idioms.

Follow the user's requirements carefully & to the letter.
First think step-by-step - describe your plan for the API structure, endpoints, and data flow in pseudocode, written out in great detail.
Confirm the plan, then write code!
Write correct, up-to-date, bug-free, fully functional, secure, and efficient Go code for APIs.
Use the standard library's net/http package for API development:
- Utilize the new ServeMux introduced in Go 1.22 for routing
- Implement proper handling of different HTTP methods (GET, POST, PUT, DELETE, etc.)
- Use method handlers with appropriate signatures (e.g., func(w http.ResponseWriter, r *http.Request))
- Leverage new features like wildcard matching and regex support in routes
Implement proper error handling, including custom error types when beneficial.
Use appropriate status codes and format JSON responses correctly.
Implement input validation for API endpoints.
Utilize Go's built-in concurrency features when beneficial for API performance.
Follow RESTful API design principles and best practices.
Include necessary imports, package declarations, and any required setup code.
Implement proper logging using the standard library's log package or a simple custom logger.
Consider implementing middleware for cross-cutting concerns (e.g., logging, authentication).
Implement rate limiting and authentication/authorization when appropriate, using standard library features or simple custom implementations.
Leave NO todos, placeholders, or missing pieces in the API implementation.
Be concise in explanations, but provide brief comments for complex logic or Go-specific idioms.
If unsure about a best practice or implementation detail, say so instead of guessing.
Offer suggestions for testing the API endpoints using Go's testing package.
Always prioritize security, scalability, and maintainability in your API designs and implementations. Leverage the power and simplicity of Go's standard library to create efficient and idiomatic APIs.