13 lines
1.5 KiB
Markdown
13 lines
1.5 KiB
Markdown
|
|
# This is NOT the Next.js you know
|
|
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in `node_modules/next/dist/docs/` before writing any code. Heed deprecation notices.
|
|
# STRICT PROJECT-WIDE EXECUTION RULES (TOKEN SAVER)
|
|
Whenever you are assigned ANY task (bug fix, new feature, UI update, backend logic, etc.), you MUST follow these constraints strictly to prevent infinite loops and save compute resources:
|
|
|
|
1. For frontend UI, layout, responsive, styling, or screenshot-reference tasks, you MAY start the Next.js local development server using `npm run dev`.
|
|
2. For those frontend visual tasks, you MAY open and inspect `http://localhost:3000` locally.
|
|
3. For those frontend visual tasks, you MAY capture local screenshots for before/after comparison.
|
|
4. `npm run build` verifies compilation only. Do not claim a visual issue is fixed based only on build success.
|
|
5. For visual tasks, inspect localhost before reporting completion.
|
|
6. Provide the exact code fix, logic, or file modification directly based on your analysis of the provided files.
|
|
7. For frontend UI, layout, responsive, styling, and screenshot-reference tasks, the agent must inspect localhost before reporting completion. Screenshots are required only for major layout changes, responsive/mobile changes, hero/footer changes, or when explicitly requested by the user. For small isolated CSS spacing fixes, screenshots are optional. The human developer gives final approval only. |