Netlify Official (.cursorrules)

{
    "prompt": "<ProviderContextOverrides> // Developers can override the content as needed, but it should all be placed in this section. </ProviderContextOverrides> ANY RULES IN THE ProviderContextOverrides SECTION CAN OVERRULE SPECIFIC RULES IN ProviderContext <ProviderContext version=\"1.0\" provider=\"netlify\"> ## General - the `.netlify` folder is not for user code. It should be added to the .gitignore list - avoid adding version numbers to imported code. (for example use `/functions` and never `/functions`) - *NEVER* add CORS headers (such as Access-Control-Allow-Origin) unless user EXPLICITLY asks for them. - prefer using `netlify dev` to start dev server unless another dev command is requested by the user # Guidelines - There are 4 types of compute systems you can write code for: - Serverless functions - usually used for transactional server/api requests. - Edge functions - usually used for code that must modify requests before hitting the server or modifying responses before returning to users. - Background functions - longer running functions for asynchronous work. - Scheduled functions - schedule logic to run on a CRON-based interval. - Netlify Blobs is a general object storage that can be used to accomplish state storage, data storage, etc. - Netlify Image CDN enables on-demand image transformations without affecting build times or optimizing images upon upload. It optimizes images dynamically based on client capabilities and caches transformations for performance improvements. Use this when optimizing images dynamically. Don't use this when you need to modify an image during the development/build process. - Environment variables are available for storing secrets, API keys, and other values that you want to control external to the code or are too sensitive to put in the code. ## Netlify compute - NEVER put any type of serverless or edge function in the public or publish directory - DO NOT change the default functions or edge functions directory unless explicitly asked to. - ALWAYS verify the correct directory to place functions or edge functions into ### Context object for serverless functions and edge functions Below are the available fields/functions from the context argument to serverless and edge functions. ``` { account: { id: string, // Unique ID of the Netlify team account associated with the site and function. }, cookies: { get: (name: string) => string | undefined, // Reads a cookie from the incoming request. set: (options: { name: string; value: string; path?: string; domain?: string; secure?: boolean; httpOnly?: boolean; expires?: Date }) => void, // Sets a cookie on the outgoing response following the web standard. delete: (nameOrOptions: string | { name: string; path?: string; domain?: string }) => void, // Deletes a cookie on the outgoing response, following the web standard. }, deploy: { context: string, // The deploy context (e.g., production, deploy-preview). id: string, // Unique ID of the deploy the function belongs to. published: boolean, // Indicates whether the function belongs to the currently published deploy. }, geo: { city: string, // City name of the client location. country: { code: string, // ISO 3166 country code. name: string, // Full country name. }, latitude: number, // Latitude c",
    "model": "Claude 3.7 Sonnet / Cursor",
    "aspect_ratio": "1:1",
    "category": "Coding Agents",
    "content_type": "text_prompt",
    "surface": "text_library",
    "quality_score": 83,
    "provenance": "SYSTEM_RULE"
}