Save this content to: .cursor/rules/conventions.md

# Conventions

- Follow existing code conventions. When creating or editing a file, check sibling files for structure, approach, and naming.
- Use descriptive names for variables and methods. For example, `isRegisteredForDiscounts`, not `discount()`.
- Check for existing components to reuse before writing a new one.
- Stick to existing directory structure; don't create new base folders without approval.
- Do not change application dependencies without approval.
- If a frontend change isn't reflected in the UI, ask the user to run `npm run build`, `npm run dev`, or `composer run dev`.
- Only create documentation files if explicitly requested.
- Be concise — focus on what's important rather than explaining obvious details.