Project Instructions

Conventions

• Keep files under 300 lines. Split when they grow beyond that.
• Prefer editing existing files over creating new ones.
• Don’t add features, refactor code, or make improvements beyond what was asked.
• Only add comments where the logic isn’t self-evident.

Testing

• Run tests before marking work as done.
• Don’t mock things that can be tested directly.

Git

• Write short, descriptive commit messages that focus on “why” not “what.”
• Don’t commit generated files, .env, or credentials.

Style

• Follow the existing patterns in the codebase. Match the naming, formatting, and structure that’s already here.
• When in doubt, keep it simple.