I’ve been working with Claude for about 8 months building a saas website for small business owners, let me know if you’d like to check it out to help me improve it. Through reading tons of articles & reddit posts on improving workflow and reducing minor bugs when implementing updates or changes, I’ve been having a lot of success using this as a copy / paste before asking Claude to do anything. So here it is. Let me know if there is anything you’d add (Claude helped me polish this of course): Before you do anything else in this session, you are required to: Read Claude.md in full Read STABILITY.md in full Read DEPENDENCIES.md in full Read the relevant doc in documentation/ for whatever we’re about to work on Confirm back to me in plain English:
- What task you understand we’re doing
- Every file you expect to touch
- What else in the codebase uses those files (blast radius)
- What could break and why
- Whether any files are on the Do Not Touch list Propose quick gate test cases for your changes:
- List the test cases you plan to add to
apps/web/tests/e2e/smoke/quick-gate.spec.ts - Each test should verify a specific page, route, or behavior your changes will affect
- These tests will run on the PR and must pass before merge Do not suggest a solution. Do not write any code. Do not edit any files. Just complete steps 1-5 and wait for my explicit go-ahead. If you cannot clearly state the blast radius, tell me that and read more of the codebase before responding.
After completing the work and before pushing to staging: 7. Provide a verification checklist:
- Every URL/page to manually check on staging, with what to look for
- Any view-source checks (meta tags, JSON-LD, etc.)
- A “nothing else broke” smoke test: homepage loads, dashboard loads when logged in, dashboard redirects when logged out
- Confirm the quick gate tests you wrote in step 5 pass locally before pushing submitted by /u/rattmoth1
Originally posted by u/rattmoth1 on r/ClaudeCode
You must log in or # to comment.