Prevent private Next.js order responses from entering shared caches: Perch rule pack

1 saved requirement for Next.js. Inspect the selectors and adapt the example paths to your repository.

- name: private-order-cache
  where: "app/api/orders/[id]/route.ts"
  ensure: >-
    The GET handler response for an authenticated order must set Cache-Control to private, no-store. It must never advertise public caching.

Download the rule pack ZIP · Download YAML · Agent repair task · Implementation, integration requirements and captured checks

Install the rule without replacing your configuration

npm install -g @lakeday/perch
perch login
curl -fL 'https://reporules.fyi/nextjs/private-response-cache/rule-pack.zip' -o 'perch-guide-nextjs-private-response-cache.zip'
unzip -n 'perch-guide-nextjs-private-response-cache.zip'

Keep your existing perch.yaml. Extraction preserves existing files and adds .perch/rules/perch-guide-nextjs-private-response-cache.yaml. Review each where selector before running a check on your application.

Configure your coding agent

perch setup claude-code
perch setup codex
perch setup cursor
perch setup pi

Choose the setup command for the agent you use.

Check the edit, fix the finding, check again

perch check app/api/orders/[id]/route.ts --rules private-order-cache --json

Run the check after an agent edit. Read the finding and affected code, repair the implementation, and repeat the identical command. Keep the application regression tests as separate gates.

Exit 3 means a finding. Exit 1 or 2 means the check did not complete. A pass does not prove application correctness. Fresh judgments can vary; unchanged requests reuse cached answers. Relevant source is sent to the configured model service.

Pack manifest and SHA-256 hash · Pack README