Browse

Standard Library Usage .cursorrules strategies

Filters

Tech

Clear

seaborn

Tauri

logging

Azure

MySQL

Go

Kafka

WebP.

next-safe-action

Phoenix LiveView

Ecto

File System Watcher

Plug

Finch

Gettext

Phoenix

Jason

Phoenix LiveDashboard

Sobelow

ExCoveralls

DNS Cluster

ExUnit

Release Please

Swoosh

Credo

LeftHook

npm

Wagmi

Viem

Next.js 14

Daisy UI

Express.js

Vercel AI SDK

Firebase

Slither

Hardhat

Mythril

Chainlink VRF

SOLID

OpenAI

SVG

SWR

Prometheus

Memcached

ELK Stack

Grafana

async/await

API

Grid

OpenAPI

React Server Components

Turborepo

None

TanStack React Query

Mongoose

virtual environments

dask

PyTorch

tqdm

Flask

joblib

NumPy

python-dotenv

pip

Django REST Framework

unittest

WhiteNoise

pytest-django

AWS

NoSQL

Kubernetes

Cypress

Axios

Next.js SSR.

Next.js 14 App Router

Angular

React Server Components (RSC)

Rell

Kotlin

Tailwind CSS.

Cairo

Biome

Composer

WebAssembly

yarn

Material UI

autoprefixer

bcryptjs

@types/react

Next.Js

@types/node

prisma

framer-motion

postcss

react-dom

Supabase Auth

WCAG

React.FC

React.ReactNode

fetch API

Go net/http ServeMux Best Practices .cursorrules prompt file

General Guidelines

Use dependency injection.
Follow the user's requirements carefully and to the letter.
Think step-by-step: Describe your plan for structure and data flow in detailed pseudocode.
Confirm the plan, then write code.
Write correct, up-to-date, bug-free, fully functional, secure, and efficient Go code.

Web Application Development

Use the standard library's net/http package for web application 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.
Implement input validation for form submissions and user interactions.
Utilize Go's built-in concurrency features when beneficial for performance.
Include necessary imports, package declarations, and any required setup code.
Implement proper logging using loggo.
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 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.

Code Style and Structure

Write concise, idiomatic Go code with accurate examples.
Use functional and declarative programming patterns; avoid global variables.
Prefer iteration and modularization over code duplication.
Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
Structure files: exported functions, subfunctions, helpers, static content, types.

Naming Conventions

Use lowercase with underscores for directories.
Favor named exports for functions.

Go Usage

Use Go for all code; prefer interfaces over concrete types.
Do not use github.com/golang/mock/gomock; use testify's mock package instead.

Priorities

Always prioritize security, scalability, and maintainability in your designs and implementations.
Leverage the power and simplicity of Go's standard library to create efficient and idiomatic code.
Use taskfile.dev over makefiles and build scripts.

stack: