Skip to content

Latest commit

 

History

History
13 lines (11 loc) · 1.11 KB

File metadata and controls

13 lines (11 loc) · 1.11 KB

Pearl Agent Rules

Keep this file operational. Product context, architecture notes, and repo maps live in docs/REPO-GUIDE.md.

  • Before you start a new dev server, check if a dev server is already running. If so, use it.
  • Do not add deterministic fallback behavior that masks a missing or broken AI step.
  • GitHub issues are the implementation backlog.
  • Use ROADMAP.md for priority context and product boundaries.
  • Run pnpm check before handing work over.
  • Conduct a scoped security audit before handing work over. Call out any unresolved security risks.
  • When delivering a frontend change, provide a screenshot of the tested UI.
  • You are responsible for proposing the git commit, not for pushing. Do not commit automatically. Present the implemented work, verification, and a conventional commit message proposal. Always end the commit proposal with exactly this approval prompt: Commit this? [Y/n]
  • After the user confirms a commit and the commit is created, inspect open GitHub issues and close the issue only when that commit fully resolves it. Leave partial or follow-up issues open and say why.