Cursor Rules 生成器

---
description: Next.js app, routes, React components, server actions, and frontend checks
globs: ["app/**/*","components/**/*","lib/**/*","pages/**/*","next.config.*","package.json"]
alwaysApply: true
---

# Cursor Project Rules

File: .cursor/rules/nextjs.mdc

## Project Context

- Project type: Next.js
- Tech stack: Next.js, TypeScript, React, CSS modules
- Coding style: Prefer small components, explicit types, accessible UI, and existing project patterns.
- AI tool target: Cursor Rules 生成器：.cursor/rules 与 .mdc 文件

## Project Commands

- Package manager: npm
- Test: `npm test`
- Build: `npm run build`
- Lint: `npm run lint`

## Stack-Specific Rules

- Use existing app router, component, and data-fetching patterns before adding new abstractions.
- Keep server and client component boundaries explicit.
- Preserve accessibility, responsive layout, metadata, and route-level SEO behavior.
- Run lint, tests, and build checks before handoff.

## Avoid

- Do not introduce duplicate fetch wrappers or UI primitives when local helpers exist.
- Do not move client-only code into server components.
- Do not hide build or hydration failures.

## How Cursor Should Work

- Inspect existing patterns before adding new abstractions.
- Keep edits scoped to the requested behavior.
- Prefer typed, accessible, maintainable code.
- Run targeted checks before final handoff when possible.
- If a command fails, report the exact failure and the likely next step.
- Link related rules from the Cursor Rules Directory when this file grows too broad.

## Extra Instructions

Before handoff, summarize changed files and mention any checks that could not be run.