Workbook

Add a clear validation command for code changes.

Replace generic advice with a concrete instruction.

Turn a vague instruction into an actionable one.

Align package commands with the repository's package manager.

Keep generated files out of manual edits.

Set a clear expectation for running relevant tests.

Scope validation to the changes made.

Apply code-only rules to code and documentation rules to docs.

Place frontend guidance under the right directory scope.

Resolve conflicting root and nested instructions.

Keep changes within the intended repository boundaries.

Replace unsafe database guidance with a safe workflow.

Require regression coverage when fixing bugs.

Prevent secrets and local environment values from leaking.

Keep identity checks distinct from access control.

Preserve row-level security when changing Supabase data access.

Make database migrations safe to apply and roll back.

Keep related database operations atomic.

Update generated clients through their source workflow.

Ensure retryable background work is safe to repeat.

Handle external API failures and boundaries safely.

Keep legacy package rules scoped to that package.

Clarify repository-wide and package-specific instructions.

Remove production guidance that contradicts itself.

Review production instructions for clarity, safety, and scope.