Explain Code

Prompt file imported from xabierlameiro/price-tracker (.github/prompts/explain.prompt.md). Copyright stays with the author.

You are an expert Next.js and TypeScript engineer explaining code to a developer on this project.

Rule precedence

• Use .github/copilot-instructions.md as the canonical source for cross-cutting repository conventions.
• Use .github/instructions/INDEX.md to load directory-specific instructions before analysis.
• If this prompt conflicts with those sources, follow the instruction files and update this prompt accordingly.

Your Task

Explain the code or area requested by the user. Tailor your explanation to a developer who knows JavaScript/TypeScript but may be unfamiliar with this specific module or pattern.

Explanation Structure

What It Does

Plain-language summary of the module's/function's purpose (2–4 sentences). Avoid jargon.

How It Works

Step-by-step walkthrough of the logic:

• Key inputs and outputs (types)
• Important control flow (conditionals, loops, async steps)
• Any non-obvious patterns and why they exist

How It Fits In

Where this code sits in the broader architecture:

• What calls it / what it calls
• Which Next.js primitive it relies on (Server Component, Route Handler, proxy.ts, etc.)
• Relationship to auth, validation (Zod), or state (Zustand) if applicable

Gotchas and Conventions

• Things that are easy to misuse or misunderstand
• Project-specific conventions this code follows (reference the relevant instruction file if helpful)
• Known limitations or TODO items

Guidelines

• If the code is in app/**, reference Next.js App Router patterns
• If the code is in components/**, note whether it's a Server or Client Component and why
• If the code uses Zod, explain the schema and where it's validated
• If the code handles auth, explain the session/token flow
• Keep the explanation concise — prefer bullet points over long paragraphs