Add CLAUDE.md with project instructions - #8
Conversation
Documents build & deploy workflow, theme structure, SYNC convention, and workspace deployment process for Claude Code sessions. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Code Review
This pull request introduces CLAUDE.md, which provides instructions for Claude Code, covering the project overview, build and deployment steps, theme structure, sync conventions, and workspace deployment. The review feedback suggests renaming the "Theme structure" section to "Project structure" and nesting the theme-specific directories under themes/demo-store-headless/ to accurately reflect the repository layout, especially since mu-plugins/ is located at the repository root.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| ## Theme structure | ||
|
|
||
| - `src/` — React source (JSX, CSS modules) | ||
| - `src/pages/` — route-level components (Home, Shop, ProductDetail, Cart, Checkout, OrderConfirmation) | ||
| - `src/components/` — shared components (Header, Footer, ProductList, ProductCard, PriceSlider) | ||
| - `src/api/` — WooCommerce Store API clients (storeApi, products, cart, checkout) | ||
| - `src/styles/` — CSS files including design tokens (`tokens.css`) | ||
| - `src/data/` — demo product fixtures for offline/demo mode | ||
| - `dist/` — Vite production build output (committed) | ||
| - `inc/` — PHP server-side rendering helpers (SSR router, SEO data, schema) | ||
| - `mu-plugins/` — WP-CLI seed scripts for demo data |
There was a problem hiding this comment.
The section is titled "Theme structure", but it includes mu-plugins/ which is typically located at the repository root (or under wp-content/mu-plugins/) rather than inside the theme directory (themes/demo-store-headless/). Renaming this to "Project structure" and nesting the theme-specific directories under themes/demo-store-headless/ clarifies the actual layout of the repository.
| ## Theme structure | |
| - `src/` — React source (JSX, CSS modules) | |
| - `src/pages/` — route-level components (Home, Shop, ProductDetail, Cart, Checkout, OrderConfirmation) | |
| - `src/components/` — shared components (Header, Footer, ProductList, ProductCard, PriceSlider) | |
| - `src/api/` — WooCommerce Store API clients (storeApi, products, cart, checkout) | |
| - `src/styles/` — CSS files including design tokens (`tokens.css`) | |
| - `src/data/` — demo product fixtures for offline/demo mode | |
| - `dist/` — Vite production build output (committed) | |
| - `inc/` — PHP server-side rendering helpers (SSR router, SEO data, schema) | |
| - `mu-plugins/` — WP-CLI seed scripts for demo data | |
| ## Project structure | |
| - `themes/demo-store-headless/` — Headless theme directory | |
| - `src/` — React source (JSX, CSS modules) | |
| - `src/pages/` — route-level components (Home, Shop, ProductDetail, Cart, Checkout, OrderConfirmation) | |
| - `src/components/` — shared components (Header, Footer, ProductList, ProductCard, PriceSlider) | |
| - `src/api/` — WooCommerce Store API clients (storeApi, products, cart, checkout) | |
| - `src/styles/` — CSS files including design tokens (`tokens.css`) | |
| - `src/data/` — demo product fixtures for offline/demo mode | |
| - `dist/` — Vite production build output (committed) | |
| - `inc/` — PHP server-side rendering helpers (SSR router, SEO data, schema) | |
| - `mu-plugins/` — WP-CLI seed scripts for demo data (located at the repository root) |
Adds SCP example with absolute paths (required for SCP) and corrects the SSH home/theme path details based on real workspace testing. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Summary
Test plan
🤖 Generated with Claude Code