Aravind/nearle-next-new
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix hero section layout in homepage

Browse Source
This commit is contained in:
Aravind
2026-06-24 12:53:36 +05:30
parent 230be11899
commit 6ddfc57217
18 changed files with 514 additions and 454 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
AGENTS.md
View File

@@ -4,9 +4,10 @@ This version has breaking changes — APIs, conventions, and file structure may
# 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. DO NOT start the Next.js dev server or any local server.
2. DO NOT use curl, browser tools, Puppeteer, or any network request to test localhost or any local API endpoints.
3. DO NOT attempt to take screenshots, scrape pages, or self-verify visual/functional changes locally.
4. DO NOT write "VERIFICATION REQUIRED" or attempt to run integration tests unless explicitly asked.
5. Provide the exact code fix, logic, or file modification directly based on your analysis of the provided files.
6. The human developer will always be responsible for running the server, executing the code, and verifying it locally.
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.