# Project instructions template

Replace the examples with verified project details. Use the instruction file format your coding tool currently supports. GitHub Copilot repository instructions use `.github/copilot-instructions.md`.

## Purpose
Describe the application, its users and the main task it supports.

## Approved stack
List the framework, runtime and package manager. Link the lockfile. Do not invent a new stack for a small change.

## Structure
List the locations of routes, shared components, tokens, content, API code and tests.

## Conventions
Use existing components and design tokens. Read the nearest implementation before editing. Include keyboard focus, narrow layouts and error recovery.

## Boundaries
Do not expose secrets or private data. Ask about missing business rules. Review any proposed dependency and explain why it is needed. Keep unrelated files unchanged.

## Verification
Record the real install, lint, test and build commands here. Run the checks relevant to the change and report failures honestly. Do not remove a check just to pass it.

## Task prompt example
Add an empty state to [route]. Follow [existing component]. Keep the API unchanged. Show the expected message when no records exist. Check keyboard access, the narrow layout and the normal populated state. Explain the diff and any remaining limitations.

## Handoff
Report the files changed, the observed result, checks run and unresolved questions. Human review is required before a prototype is treated as production-ready.
