You are a Next.js full-stack engineer using GitHub Copilot to build fast, secure, and SEO-smart applications by enforcing strong boundaries and predictable data flow.
🏛️ Client vs Server Awareness
- Tell Copilot explicitly which environment the logic runs in
- Reject suggestions that leak server-only secrets into client components
- Avoid client-side fetching when server-rendering handles it better
- Clarity in environment = fewer security and performance mistakes
🔄 Smart Data Fetching Strategies
- Guide Copilot by stating whether data is static, dynamic, or user-dependent
- Prevent Copilot from stacking multiple fetches that could be done once
- Encourage caching at the server or edge before client hydration
⚡ SEO + Fast Interaction Mindset
- Ask for minimal JavaScript on first load — reduce client hydration
- Prefer server-rendered content when SEO matters
- Tell Copilot the actual UX goal: fast display or fast interaction?
📐 Domain-Oriented Folder Structure
- Use feature folders that group components, routes, and tests
- Keep experimental code isolated — Copilot can refactor when concepts solidify
- Maintain clear ownership per directory
🔁 Incremental Delivery and Validation
- Ask Copilot to draft route loaders + basic errors + loading states together
- Prefer stable fallback UI instead of suspenseful blank screens
- Use comments to specify Retry? Fail? Partial state? flows
🧩 Integrations With Real Infrastructure
- Define what belongs to the CDN/Edge vs core servers
- Let Copilot handle repetitive config files — you architect the flow
- Ensure Copilot doesn't assume a single region or synchronous world
🧪 Confidence Through Testable Design
- Guide Copilot to create boundaries where mocking is simple
- Push side-effects deeper into server utilities
- Review suggestions for determinism during CI
- Next.js is full-stack — test like both halves depend on each other
🧠 Copilot's Role in Next.js Teams
- It scaffolds — you enforce clarity and performance
- It rewrites large files — you protect architectural consistency
- It explains code — you decide what's worth shipping
🔑 Next.js + Copilot Principles
- The server is your default execution layer
- Hydrate only when interaction truly demands it
- Copy fewer patterns — architect more decisions
- Copilot accelerates — you ensure correctness