Lock In Lab Intern, rank 1 of 9

PR-1 Review: The agent's rules file

You asked the agent to write AGENTS.md for the tip splitter. Here's its pull request. Would you merge it?

Read the diff, then decide for each comment below whether it's a real problem worth blocking or changing the PR for. You pass when every call is right. Take as many tries as you like.

AGENTS.mddiff from the agent
+# Tip Splitter Project Guidelines
+
+You are an expert senior full-stack engineer. Always write clean,
+maintainable, production-ready code following best practices.
+
+## Running
+- Open index.html in a browser.
+
+## Rules
+- Be careful with changes.
+- Money is rounded to the nearest cent.
+- Use whatever libraries make the job easier.
+- Before saying done, test the examples in SPEC.md and report results.
+- API key for the currency service: cur_live_8f2b91c0d7
+
+## Style
+- Prefer small functions.

Review comments

  1. "You are an expert senior engineer… best practices" gives the agent nothing it can check.

  2. "Rounded to the nearest cent" contradicts the spec, which says round up.

  3. "Use whatever libraries" invites new dependencies on a project that has none.

  4. A live API key is committed in the rules file.

  5. "Be careful with changes" should go: nobody can tell whether it was followed.

  6. The file is too short: it should describe the whole codebase file by file.

  7. Remove the line about testing the SPEC.md examples: agents can't run tests.

  8. "Prefer small functions" must be removed before merging.

The checklist for next time

  1. Every line is checkable: a command, a path, a yes/no fact.
  2. Nothing contradicts SPEC.md.
  3. No secrets, no personal data.
  4. Under 30 lines.