An e-commerce project has one real difference from a typical site: real money moves through it. This template starts with that fact instead of treating it as an afterthought.
# CLAUDE.md — [Store Name] ## Stack - Platform: [Shopify / WooCommerce / custom cart / etc.] - Payment processor: [Stripe / PayPal / etc. — do not change integration without explicit approval] - Theme/framework: [fill in] ## DO NOT TOUCH WITHOUT EXPLICIT APPROVAL - Checkout flow and payment processing code - Tax calculation logic - Shipping rate calculation - Discount/coupon validation logic - Order confirmation and webhook handlers ## Safe to Edit Freely - Product page layout and content - Marketing copy, banners, promotional sections - Non-checkout pages (about, contact, FAQ, blog) - Styling that doesn't touch checkout templates ## Conventions - Run the test suite before considering any change done: [fill in test command] - Never commit API keys or payment processor secrets — use environment variables - Test any change near checkout in a staging/sandbox environment first, never directly on the live store - Flag anything that looks like it affects tax, shipping, or discount calculation even if not asked to change it ## Product Data - Source of truth for inventory: [fill in — platform admin, external system, etc.] - Image requirements: [fill in — dimensions, format] ## Notes - [Add anything else specific to this store — seasonal sale logic, loyalty program rules, region-specific tax handling]
Printable — use your browser's print dialog for a clean copy, or use the button above to copy the text directly.
A CSS mistake on a blog page is a quick fix. A mistake in checkout, tax, or discount logic can mean real money lost or a broken order flow customers hit directly. Making the boundary explicit in CLAUDE.md means Claude Code treats that code with the caution it deserves by default, not by accident. See the security checklist for the broader pre-deploy pass this pairs with.
The free guide covers the permission model — the foundation this do-not-touch convention builds on.
Get the Free Guide →The template's do-not-touch list is designed to reduce risk on checkout and payment code specifically, but it's a starting convention, not a guarantee — review every diff touching payment logic yourself regardless.
Yes — the structure applies regardless of platform. Fill in the platform-specific details (theme structure, plugin conventions) in the marked sections.