This repository contains context rules (.mdc files) that guide AI systems in understanding, generating, and validating code when you're working with Neon technologies.
-
Neon Auth (
neon-auth.mdc)
Guidelines for implementing authentication in your application using both Stack Auth (frontend authentication system) and Neon Auth (database integration for user data). -
Neon Serverless (
neon-serverless.mdc)
Guidelines for connecting to and using Neon databases in serverless environments with approaches to connection pooling, environment configuration, and query optimization. -
Neon with Drizzle (
neon-drizzle.mdc)
Guidelines for integrating Neon databases with the Drizzle ORM framework, including setup, schema definition, and query patterns.
If you use the Cursor editor or any AI-based code assistant that supports custom rules:
- Open Cursor
- Create or navigate to the
.cursor/rulesfolder in your project - Copy any of the
.mdcfiles (e.g.neon-auth.mdc,neon-serverless.mdc,neon-drizzle.mdc) into.cursor/rules - (Optional) Re-index your project in Cursor so it automatically picks up the new rules
Example of file structure:
.cursor/
rules/
neon-auth.mdc
neon-serverless.mdc
neon-drizzle.mdc
When using the Cursor agent, it should automatically apply these rules when generating code related to Neon.
If it doesn't, you can manually append these rules to the agent's context by referencing the specific rule file directly in your prompt.
.mdc stands for Markdown Context files that provide guidance to AI tools. By splitting these guidelines into separate files, AI agents can automatically pull the relevant best practices when they see code related to Neon, Stack Auth, or Drizzle.
Yes! You can integrate .mdc files in any AI environment that supports custom context rules. The format is language-agnostic and designed to guide AI-assisted code generation.
Simply create a new .mdc file or edit an existing one. Your AI tool will use the content to guide its responses when you're working with the relevant technologies.