Next.js Full-Stack Development Rules
Best practices for App Router, Server Actions, and strict TypeScript.
Browse copy-ready AI coding assets for Cursor. Find practical rules, roles, skills, hooks and workflows for building, debugging, reviewing, refactoring, testing and deploying software with AI.
Persistent instructions for Cursor Agent and Chat. Place project Cursor rules in .cursor/rules/ as .mdc or Markdown files at your repo root — for example .cursor/rules/*.mdc. Use AI coding roles and AI coding skills as copy-ready prompts, and AI coding hooks for short pre-task instructions. Cursor applies them automatically in Agent and Chat.
Open any asset page and click Copy to paste into your project. Combine Cursor prompts with Cursor workflows for multi-step tasks. See Cursor Agent & Skills rules for workflow tips.
Narrow Cursor assets by development category and framework.
Best practices for App Router, Server Actions, and strict TypeScript.
Row Level Security, Edge Functions, and Postgres best practices.
Modern UI design systems, motion, and accessibility guidelines.
Memory safety, concurrency, and Cargo ecosystem best practices.
Composition API, Nuxt 3 SSR, and Pinia state management patterns.
Multi-stage builds, image optimization, and docker-compose local development.
Build Model Context Protocol servers with typed tools, resources, and secure transport.
Guide Cursor Agent behavior, Skills usage, and safe autonomous coding workflows.
Streaming chat UIs, tool calling, and server-side AI routes with Vercel AI SDK.
Reliable end-to-end tests with Playwright — selectors, fixtures, and CI patterns.
Modern React patterns — hooks, composition, performance, and accessible components.
Schema design, migrations, typed queries, and Prisma Client best practices.
Reusable workflows, caching, matrix builds, and secure CI pipelines.
Authentication with Auth.js — providers, sessions, middleware, and RBAC.
SvelteKit routing, load functions, forms, and progressive enhancement.
K8s manifests, Helm, health probes, resources limits, and GitOps.
Monorepo structure, turbo pipelines, shared packages, and caching.
Accessible UI components with shadcn/ui, Radix primitives, and Tailwind.
Rules for building clean, scalable Next.js App Router projects with TypeScript, server components, API routes, and reusable architecture.
Rules for writing maintainable React components with TypeScript, clear props, reusable hooks, and clean component structure.
Rules for building secure Supabase apps with authentication, row level security, policies, and safe database access.
Rules for creating clean Expo React Native apps with reusable screens, navigation, state management, and mobile-friendly structure.
Rules for asking AI coding agents to review code for bugs, security risks, maintainability, performance, and edge cases.
A senior engineering role prompt for building production-ready full-stack features with clear planning, clean architecture, and safe implementation.
A Next.js architecture role for App Router, server components, API routes, and production-ready structure.
A frontend role for building clean, reusable, accessible React UI.
A TypeScript role for safer types, better interfaces, and fewer runtime errors.
A code review role for finding bugs, maintainability issues, security risks, and edge cases.
A debugging role that focuses on root cause analysis before changing code.
A security role for authentication, authorization, validation, secrets, and data exposure.
A product-focused engineering role for building SaaS MVP features quickly and safely.
A DevOps role for preparing projects for deployment.
A testing role for unit tests, integration tests, and E2E coverage.
Build a simple SaaS MVP with authentication, dashboard, database, and clean structure.
Debug a problem systematically instead of making random changes.
Review a PR like a senior engineer.
Refactor old code safely without changing behavior.
Generate useful unit tests for important business logic.
Add browser tests for core user journeys.
Improve the interface so it looks like a modern SaaS product.
Improve frontend or full-stack performance safely.
Review and improve authentication and authorization logic.
Generate clear project documentation.
A short hook that forces planning before implementation.
A debugging hook that prevents random code changes.
A safe refactoring hook.
A code review hook.
A hook for feature development.
A hook for practical testing.
A hook for understanding a new project.
A hook for UI polish.
A hook for security review.
A hook for production readiness.
Cursor assets are copy-ready instructions that shape how Cursor Agent and Chat write, review, and refactor code. Rules encode team conventions in .cursor/rules/. Roles, skills and hooks are paste-ready prompts for specific tasks and personas.
Save project rules as .mdc or Markdown files in .cursor/rules/ at your repo root — for example .cursor/rules/*.mdc. Cursor applies them automatically in Agent and Chat.
Put project rules in .cursor/rules/ at your repo root. Use .mdc files (recommended) or Markdown — for example .cursor/rules/*.mdc. Cursor applies them automatically in Agent and Chat. See our Cursor Agent & Skills rules for workflow tips.
Browse the Cursor Assets Directory, open an asset detail page, and click the copy button (Copy Rule, Copy Role, Copy Skill, or Copy Hook depending on asset type). For rules, paste into .cursor/rules/; for roles, skills and hooks, paste into Agent or Chat. Each asset has a permanent URL (e.g. /rules/nextjs-fullstack).
Yes. Assets are starting templates — remove sections you do not need, add project-specific conventions, and keep total length reasonable so you do not overrun the AI context window.
Yes. Most assets on this site are MIT-licensed unless noted otherwise on the detail page. Check the License line on each card or detail page.
Visit Submit an AI Coding Asset for guidelines, then send your asset by email.
Windsurf rules go in .devin/rules/*.md (preferred) or legacy .windsurf/rules/*.md. Browse the Windsurf Assets Directory or see Also explore in the sidebar.