animation fixed in section
This commit is contained in:
225
AGENTS.md
225
AGENTS.md
@@ -1,13 +1,216 @@
|
||||
# Nearle Project Guide
|
||||
|
||||
# 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:
|
||||
## Project
|
||||
|
||||
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.
|
||||
Nearle is a premium hyperlocal commerce platform connecting
|
||||
|
||||
- Customers
|
||||
- Local Merchants
|
||||
- Delivery Partners
|
||||
- Brands
|
||||
|
||||
The experience should feel:
|
||||
|
||||
- Premium
|
||||
- Modern
|
||||
- Minimal
|
||||
- Community-first
|
||||
- Human
|
||||
- Trustworthy
|
||||
|
||||
Avoid generic SaaS designs.
|
||||
|
||||
---
|
||||
|
||||
# Tech Stack
|
||||
|
||||
- Next.js 16 App Router
|
||||
- React
|
||||
- TypeScript
|
||||
- Tailwind CSS
|
||||
- MaterialIcon component
|
||||
|
||||
IMPORTANT
|
||||
|
||||
This project uses the latest Next.js version.
|
||||
|
||||
Before changing framework APIs, read
|
||||
|
||||
node_modules/next/dist/docs/
|
||||
|
||||
Follow the latest conventions.
|
||||
|
||||
---
|
||||
|
||||
# Design System
|
||||
|
||||
Preserve the existing Nearle identity.
|
||||
|
||||
Never change unless explicitly requested:
|
||||
|
||||
- Brand colors
|
||||
- Typography
|
||||
- Border radius
|
||||
- Layout hierarchy
|
||||
- Section order
|
||||
- Existing content
|
||||
- Existing illustrations
|
||||
|
||||
Always extend the current design instead of redesigning it.
|
||||
|
||||
---
|
||||
|
||||
# UI Rules
|
||||
|
||||
Always match existing Nearle pages.
|
||||
|
||||
Reuse:
|
||||
|
||||
- Hero layouts
|
||||
- CTA buttons
|
||||
- Card styles
|
||||
- Section spacing
|
||||
- Grid system
|
||||
- Shadows
|
||||
- Glass effects
|
||||
- Gradients
|
||||
|
||||
Avoid Bootstrap-style layouts.
|
||||
|
||||
---
|
||||
|
||||
# Motion Rules
|
||||
|
||||
Use:
|
||||
|
||||
- Framer Motion
|
||||
- CSS transitions
|
||||
|
||||
Avoid:
|
||||
|
||||
- Heavy GSAP
|
||||
- Layout animations
|
||||
- Flashy effects
|
||||
|
||||
Animation style:
|
||||
|
||||
- Apple
|
||||
- Linear
|
||||
- Stripe
|
||||
- Vercel
|
||||
|
||||
Use only:
|
||||
|
||||
- opacity
|
||||
- transform
|
||||
- scale
|
||||
- translate
|
||||
|
||||
Respect prefers-reduced-motion.
|
||||
|
||||
---
|
||||
|
||||
# Code Rules
|
||||
|
||||
Never rewrite files unnecessarily.
|
||||
|
||||
Only modify required code.
|
||||
|
||||
Preserve formatting.
|
||||
|
||||
Do not rename components unless necessary.
|
||||
|
||||
Reuse existing components before creating new ones.
|
||||
|
||||
Create reusable components when repeated more than twice.
|
||||
|
||||
---
|
||||
|
||||
# Performance
|
||||
|
||||
Maintain 60 FPS.
|
||||
|
||||
Avoid unnecessary re-renders.
|
||||
|
||||
Avoid layout shift.
|
||||
|
||||
Prefer GPU-friendly animations.
|
||||
|
||||
Optimize images.
|
||||
|
||||
---
|
||||
|
||||
# SEO
|
||||
|
||||
Every new page should include:
|
||||
|
||||
- Metadata
|
||||
- Title
|
||||
- Description
|
||||
- OpenGraph
|
||||
- Semantic HTML
|
||||
|
||||
---
|
||||
|
||||
# Content Rules
|
||||
|
||||
Write content specifically for Nearle.
|
||||
|
||||
Tone:
|
||||
|
||||
- Friendly
|
||||
- Premium
|
||||
- Community-first
|
||||
- Local
|
||||
- Trustworthy
|
||||
|
||||
Avoid AI-sounding or generic marketing copy.
|
||||
|
||||
Prefer real examples involving:
|
||||
|
||||
- neighbourhood stores
|
||||
- customers
|
||||
- delivery partners
|
||||
- local commerce
|
||||
- digital catalogues
|
||||
- QR ordering
|
||||
|
||||
---
|
||||
|
||||
# Execution Rules
|
||||
|
||||
Frontend Tasks
|
||||
|
||||
- You MAY run npm run dev.
|
||||
- Inspect localhost before reporting visual fixes.
|
||||
- Use screenshots only for major UI changes.
|
||||
|
||||
Build
|
||||
|
||||
- npm run build only verifies compilation.
|
||||
- Never claim visual fixes based only on build success.
|
||||
|
||||
---
|
||||
|
||||
# Workflow
|
||||
|
||||
Before editing
|
||||
|
||||
1. Read the target file.
|
||||
2. Understand existing implementation.
|
||||
3. Modify only the required code.
|
||||
4. Avoid unrelated refactoring.
|
||||
5. Keep code production ready.
|
||||
6. Return concise summaries.
|
||||
|
||||
---
|
||||
|
||||
# Response Rules
|
||||
|
||||
Do not explain obvious code.
|
||||
|
||||
Do not rewrite unchanged code.
|
||||
|
||||
Do not introduce unnecessary abstractions.
|
||||
|
||||
Focus only on the requested task.
|
||||
Reference in New Issue
Block a user