climaybe 3.0.9 → 3.1.1

package/README.md

@@ -227,7 +227,7 @@ Enabled via `climaybe init` prompt (`Enable preview + cleanup workflows?`; defau
 
 | Workflow | Trigger | What it does |
 |----------|---------|-------------|
-| `pr-update.yml` | PR opened/synchronize/reopened (base: main, staging, develop, staging-*, live-*) | Shares draft theme, renames with `-PR<number>`, comments preview + customize URLs; uses default store for main/staging/develop, or the store for staging-&lt;alias&gt;/live-&lt;alias&gt; |
+| `pr-update.yml` | PR opened/synchronize/reopened (base: main, staging, develop, staging-*, live-*) | Shares draft theme, renames with `-PR<number>`, comments preview + customize URLs; uses default store for main/staging/develop, or the store for staging-&lt;alias&gt;/live-&lt;alias&gt;. **Path filter:** runs only when the PR changes theme paths (`assets/`, `blocks/`, `config/`, `layout/`, `locales/`, `sections/`, `snippets/`, `templates/`, `_scripts/`, `_styles/`, `shopify.theme.toml`, `stores/**`); docs-only or tooling-only PRs skip preview work. |
 | `pr-close.yml` | PR closed (same branch set) | Deletes matching preview themes and comments deleted count + names |
 | `reusable-share-theme.yml` | workflow_call | Shares Shopify draft theme and returns `theme_id` |
 | `reusable-rename-theme.yml` | workflow_call | Renames shared theme to include `PR<number>` (fails job on rename failure) |
@@ -250,8 +250,8 @@ Build workflows install deps with `npm ci` and run `npx --no-install climaybe bu
 
 | Workflow | Trigger | What it does |
 |----------|---------|-------------|
-| `build-pipeline.yml` | Push to any branch | Runs reusable build and Lighthouse checks (when required secrets exist) |
-| `reusable-build.yml` | workflow_call | Runs Node build + Tailwind compile, then commits compiled assets when changed |
+| `build-pipeline.yml` | Push to any branch (ignores docs-only/tooling-only paths; see CI/CD reference) | Runs reusable build; Lighthouse only on branch **`staging`**, when a build ran, and secrets allow |
+| `reusable-build.yml` | workflow_call | Path-filtered `build-scripts` / Tailwind (`climaybe build`), then commits compiled assets when changed |
 | `create-release.yml` | Push tag `v*`, or **workflow_run** after Post-Merge Tag / Nightly Hotfix Tag succeed on `main` | Builds release archive and creates GitHub Release notes from commits since the previous tag. It filters repetitive automation subjects (main→staging syncs, store/root sync chores, bot merge noise) before generating notes. If remaining subjects are low-signal and `GEMINI_API_KEY` exists, it uses Gemini to generate cleaner merchant-facing notes. Also covers tags created by workflows with `GITHUB_TOKEN`, which may not trigger tag-push workflows. |
 
 ### Optional theme dev kit package
@@ -270,6 +270,59 @@ You can create optional build entrypoints later with:
 
 If these files already exist, `init` warns that they will be replaced.
 
+### Section schema builder
+
+Build Shopify section schemas dynamically from JavaScript or JSON files using `climaybe build-schemas`. Works directly in `sections/` — no separate source folder, no sync issues with the theme editor.
+
+**How it works:** Add an inline-comment marker at the end of any `sections/*.liquid` or `blocks/*.liquid` file. Shopify treats `{% # ... %}` as a comment and ignores it. The builder finds the marker, resolves the schema from `_schemas/`, and writes the generated `{% schema %}...{% endschema %}` block below it. The marker is never removed, so rebuilds always work — even after Shopify theme editor edits.
+
+```liquid
+<section class="hero">{{ section.settings.title }}</section>
+
+{% # schema 'hero-banner' %}
+{% schema %}
+{
+  "name": "Hero Banner",
+  "settings": [...]
+}
+{% endschema %}
+```
+
+On rebuild, only the generated `{% schema %}` block is replaced. Everything above the marker (including theme editor changes) is preserved.
+
+**Supported patterns:**
+
+- **Shared schemas** — one schema file reused across multiple sections
+- **Partials** — `require()` shared settings arrays into multiple schemas
+- **Common fieldsets** — spread partial arrays into settings (`...linkSettings`)
+- **Looping fieldsets** — factory functions that generate repeated field groups
+- **Section-specific overrides** — export a function receiving `(filename, inlineContent)` to customise per section
+- **Inline JSON overrides** — add `{% # { "name": "Custom" } %}` below the marker
+
+```bash
+npx climaybe build-schemas              # generate schemas in sections/
+npx climaybe build-schemas --dry-run    # preview without writing files
+npx climaybe build-schemas --list       # list schema files and markers
+```
+
+Schemas also rebuild automatically during `climaybe serve` and `climaybe serve:assets` — the watcher monitors `_schemas/` for changes and rebuilds on save, tagged `[schema]` in green. `climaybe build` includes schemas alongside scripts and Tailwind.
+
+Example `_schemas/hero-banner.js`:
+
+```js
+const createLinks = require('./partials/create-links');
+
+module.exports = {
+  name: 'Hero Banner',
+  settings: [
+    { label: 'Title', id: 'title', type: 'text' },
+    ...createLinks(2)
+  ]
+};
+```
+
+**Full examples:** See **[Schema Builder Examples](docs/SCHEMA_BUILDER_EXAMPLES.md)** for working code covering every pattern.
+
 You can install/update this later with:
 
 `climaybe add-dev-kit` (or `climaybe theme add-dev-kit`)
@@ -342,6 +395,10 @@ Add the following secrets to your GitHub repository (or use **GitLab CI/CD varia
 │       ├── config/settings_data.json
 │       ├── templates/*.json
 │       └── sections/*.json
+├── _schemas/            (optional: JS/JSON schema definitions for build-schemas)
+│   ├── hero-banner.js
+│   └── partials/
+│       └── link.js
 ├── package.json
 └── .github/workflows/
 ```

package/bin/version.txt

@@ -1 +1 @@
-3.0.9
+3.1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "climaybe",
-  "version": "3.0.9",
+  "version": "3.1.1",
   "description": "Shopify CLI by Electric Maybe for theme CI/CD workflows, branch orchestration, app setup, and dev tooling",
   "type": "module",
   "bin": {
@@ -82,7 +82,7 @@
     "@tailwindcss/cli": "^4.1.17",
     "@tailwindcss/typography": "^0.5.16",
     "commander": "^14.0.3",
-    "eslint": "^9.11.0",
+    "eslint": "^10.1.0",
     "picocolors": "^1.1.1",
     "prettier": "^3.4.2",
     "prompts": "^2.4.2",

package/src/commands/build-schemas.js

@@ -0,0 +1,74 @@
+import pc from 'picocolors';
+import { requireThemeProject } from '../lib/theme-guard.js';
+import { buildSchemas, listSchemaFiles, listSectionsWithSchemaRefs } from '../lib/schema-builder.js';
+
+export async function buildSchemasCommand(opts = {}) {
+  console.log(pc.bold('\n  climaybe — Build schemas\n'));
+  if (!requireThemeProject()) return;
+
+  try {
+    const dryRun = opts.dryRun === true;
+    const list = opts.list === true;
+
+    if (list) {
+      const schemas = listSchemaFiles(process.cwd());
+      const refs = listSectionsWithSchemaRefs(process.cwd());
+
+      if (schemas.length === 0 && refs.length === 0) {
+        console.log(pc.yellow('  No _schemas/ files or schema markers found.'));
+        return;
+      }
+
+      if (schemas.length > 0) {
+        console.log(pc.cyan('  Schema source files (_schemas/):'));
+        for (const s of schemas) {
+          console.log(pc.dim(`    - ${s}`));
+        }
+      }
+
+      if (refs.length > 0) {
+        console.log(pc.cyan('\n  Files with schema markers:'));
+        for (const { section, schemas: names } of refs) {
+          console.log(`    ${pc.white(section)} → ${names.map((r) => pc.green(r)).join(', ')}`);
+        }
+      }
+      return;
+    }
+
+    if (dryRun) {
+      console.log(pc.dim('  Dry run — no files will be written.\n'));
+    }
+
+    const { processed, skipped, errors } = buildSchemas({ cwd: process.cwd(), dryRun });
+
+    if (processed.length === 0 && errors.length === 0 && skipped.length === 0) {
+      console.log(pc.yellow('  No sections/ or blocks/ directory found. Nothing to build.'));
+      return;
+    }
+
+    if (processed.length === 0 && errors.length === 0) {
+      console.log(pc.yellow('  No schema markers found in sections/ or blocks/.'));
+      console.log(pc.dim("  Add a marker to a liquid file:  {% # schema 'name' %}"));
+      return;
+    }
+
+    if (processed.length > 0) {
+      const verb = dryRun ? 'Would generate' : 'Generated';
+      console.log(pc.green(`  ${verb} schemas for ${processed.length} file(s):`));
+      for (const { section, schemaName } of processed) {
+        console.log(pc.dim(`    - ${section} ← _schemas/${schemaName}`));
+      }
+    }
+
+    if (errors.length > 0) {
+      console.log(pc.red(`\n  ${errors.length} error(s):`));
+      for (const { section, schema, error } of errors) {
+        console.log(pc.red(`    ${section} (schema: ${schema}): ${error}`));
+      }
+      process.exitCode = 1;
+    }
+  } catch (err) {
+    console.log(pc.red(`  Build error: ${err.message}`));
+    process.exitCode = 1;
+  }
+}

package/src/cursor/rules/00-rule-index.mdc

@@ -15,7 +15,7 @@ When you perform any of the following, **read and apply** the corresponding rule
 - **Liquid syntax and usage** → `liquid.mdc`
 - **Section files (sections/*.liquid)** → `sections.mdc`
 - **Snippets (snippets/*.liquid)** → `snippets.mdc`
-- **Schema definitions (section/layout schemas)** → `schemas.mdc`
+- **Schema definitions (section/layout schemas), _schemas/ builder** → `schemas.mdc`
 - **Liquid documentation comments** → `liquid-doc-rules.mdc`
 - **JS refactor tasks / current refactoring work** → `js-refactor-tasks.mdc`
 - **Adding or editing Cursor rules** → `cursor-rule-template.mdc`

package/src/cursor/rules/commit-rules.mdc

@@ -1,5 +1,5 @@
 ---
-description: Git commit conventions for Shopify theme projects (emoji + type + description)
+description: Git commit conventions for Shopify theme projects (type + description)
 globs:
   - "**/*"
 alwaysApply: false
@@ -8,75 +8,75 @@ alwaysApply: false
 
 ## Commit Convention
 
-Follow conventional commit format with emoji prefixes for all commits:
+Follow conventional commit format for all commits:
 
 ```
-<emoji> <type>: <description>
+<type>: <description>
 ```
 
 ## Commit Types
 
-### 🔨 `fix:` - Bug Fixes
+### `fix:` - Bug Fixes
 - Fixes for broken functionality
 - Bug patches and error corrections
 - Performance fixes
 
 **Examples:**
 ```
-🔨 fix: modal close button not working
-🔨 fix: cart total calculation error
-🔨 fix: mobile navigation menu overlap
+fix: modal close button not working
+fix: cart total calculation error
+fix: mobile navigation menu overlap
 ```
 
-### 🚀 `feat:` - New Features
+### `feat:` - New Features
 - New functionality additions
 - Feature implementations
 - New components or sections
 
 **Examples:**
 ```
-🚀 feat: add product quick view functionality
-🚀 feat: implement infinite scroll for collections
-🚀 feat: add newsletter signup modal
+feat: add product quick view functionality
+feat: implement infinite scroll for collections
+feat: add newsletter signup modal
 ```
 
-### ♻️ `refactor:` - Code Refactoring
+### `refactor:` - Code Refactoring
 - Code restructuring without changing functionality
 - Performance improvements
 - Code cleanup and optimization
 
 **Examples:**
 ```
-♻️ refactor: optimize product card rendering
-♻️ refactor: restructure JavaScript build system
-♻️ refactor: improve web component lifecycle management
+refactor: optimize product card rendering
+refactor: restructure JavaScript build system
+refactor: improve web component lifecycle management
 ```
 
-### 🎨 `style:` - UI/Styling Changes
+### `style:` - UI/Styling Changes
 - Visual design updates
 - CSS/styling modifications
 - Layout adjustments
 
 **Examples:**
 ```
-🎨 style: update button hover states
-🎨 style: improve mobile responsive design
-🎨 style: adjust typography spacing
+style: update button hover states
+style: improve mobile responsive design
+style: adjust typography spacing
 ```
 
-### 🗑️ `remove:` - Code Removal
+### `remove:` - Code Removal
 - Removing unused code
 - Deleting deprecated features
 - Cleaning up legacy code
 
 **Examples:**
 ```
-🗑️ remove: unused JavaScript functions
-🗑️ remove: deprecated Liquid snippets
-🗑️ remove: old CSS classes
+remove: unused JavaScript functions
+remove: deprecated Liquid snippets
+remove: old CSS classes
 ```
 
-### 🚧 `wip:` - Work in Progress
+### `wip:` - Work in Progress
 - Incomplete features
 - Experimental code
 - Development in progress
@@ -84,12 +84,12 @@ Follow conventional commit format with emoji prefixes for all commits:
 
 **Examples:**
 ```
-🚧 wip: product quick view modal (incomplete)
-🚧 wip: experimental infinite scroll implementation
-🚧 wip: temporary mobile navigation solution
+wip: product quick view modal (incomplete)
+wip: experimental infinite scroll implementation
+wip: temporary mobile navigation solution
 ```
 
-### 📝 `docs:` - Documentation
+### `docs:` - Documentation
 - README updates
 - Code documentation
 - Comment additions
@@ -97,12 +97,12 @@ Follow conventional commit format with emoji prefixes for all commits:
 
 **Examples:**
 ```
-📝 docs: update installation instructions
-📝 docs: add component usage examples
-📝 docs: improve code comments
+docs: update installation instructions
+docs: add component usage examples
+docs: improve code comments
 ```
 
-### ✨ `ai:` - AI Rules & Automation
+### `ai:` - AI Rules & Automation
 - AI-generated code improvements
 - Automated refactoring
 - Code optimization rules
@@ -110,12 +110,12 @@ Follow conventional commit format with emoji prefixes for all commits:
 
 **Examples:**
 ```
-✨ ai: implement automated code formatting rules
-✨ ai: optimize web component performance with AI suggestions
-✨ ai: add intelligent error handling patterns
+ai: implement automated code formatting rules
+ai: optimize web component performance with AI suggestions
+ai: add intelligent error handling patterns
 ```
 
-### 🔧 `chore:` - Maintenance Tasks
+### `chore:` - Maintenance Tasks
 - Build system updates
 - Configuration changes
 - Dependency management
@@ -123,21 +123,21 @@ Follow conventional commit format with emoji prefixes for all commits:
 
 **Examples:**
 ```
-🔧 chore: update Tailwind CSS to v4
-🔧 chore: add new npm scripts
-🔧 chore: update Shopify CLI version
+chore: update Tailwind CSS to v4
+chore: add new npm scripts
+chore: update Shopify CLI version
 ```
 
-### ⬆️ `upgrade:` - Dependencies
+### `upgrade:` - Dependencies
 - Package updates
 - Version upgrades
 - Security patches
 
 **Examples:**
 ```
-⬆️ upgrade: update Shopify CLI to latest version
-⬆️ upgrade: bump Tailwind CSS dependencies
-⬆️ upgrade: security patch for npm packages
+upgrade: update Shopify CLI to latest version
+upgrade: bump Tailwind CSS dependencies
+upgrade: security patch for npm packages
 ```
 
 ## Commit Message Guidelines
@@ -150,18 +150,18 @@ Follow conventional commit format with emoji prefixes for all commits:
 
 ### Good Examples
 ```
-🔨 fix: resolve cart total calculation error
-🚀 feat: implement product quick view modal
-♻️ refactor: optimize web component performance
-🎨 style: improve mobile navigation layout
+fix: resolve cart total calculation error
+feat: implement product quick view modal
+refactor: optimize web component performance
+style: improve mobile navigation layout
 ```
 
 ### Bad Examples
 ```
-🔨 fix: fixed the bug
-🚀 feat: Added new feature
-♻️ refactor: Refactored code for better performance.
-🎨 style: Updated styling
+fix: fixed the bug
+feat: Added new feature
+refactor: Refactored code for better performance.
+style: Updated styling
 ```
 
 ## Multi-line Commit Messages
@@ -169,7 +169,7 @@ Follow conventional commit format with emoji prefixes for all commits:
 For complex changes, use multi-line format:
 
 ```
-🔨 fix: resolve cart total calculation error
+fix: resolve cart total calculation error
 
 - Fix floating point precision issues
 - Add proper error handling for invalid prices
@@ -183,7 +183,7 @@ Closes #123
 For breaking changes, use `!` after the type and include migration notes:
 
 ```
-♻️ refactor!: restructure web component API
+refactor!: restructure web component API
 
 BREAKING CHANGE: Component initialization now requires config object
 Migration: Update component calls to use new API format
@@ -197,9 +197,9 @@ Migration: Update component calls to use new API format
 You can add scope to specify the area of change:
 
 ```
-🔨 fix(web-components): resolve event listener memory leak
-🚀 feat(sections): add new product grid layout
-🎨 style(header): improve mobile navigation
+fix(web-components): resolve event listener memory leak
+feat(sections): add new product grid layout
+style(header): improve mobile navigation
 ```
 
 ## File-specific Commits
@@ -207,9 +207,9 @@ You can add scope to specify the area of change:
 When committing changes to specific file types, include context:
 
 ```
-🔨 fix(liquid): resolve template rendering error in product page
-🚀 feat(js): add new utility functions for DOM manipulation
-🎨 style(css): update button component styling
+fix(liquid): resolve template rendering error in product page
+feat(js): add new utility functions for DOM manipulation
+style(css): update button component styling
 ```
 
 ## Commit Frequency
@@ -250,37 +250,37 @@ When creating pull requests:
 
 ### Web Components
 ```
-🔨 fix: resolve web component memory leak in disconnectedCallback
-🚀 feat: add new electric-slider component with touch support
-♻️ refactor: optimize web component event handling
+fix: resolve web component memory leak in disconnectedCallback
+feat: add new electric-slider component with touch support
+refactor: optimize web component event handling
 ```
 
 ### Shopify Sections
 ```
-🔨 fix: resolve section rendering error in collection page
-🚀 feat: add new product recommendations section
-🎨 style: improve section spacing and layout
+fix: resolve section rendering error in collection page
+feat: add new product recommendations section
+style: improve section spacing and layout
 ```
 
 ### JavaScript
 ```
-🔨 fix: resolve async/await error in cart API
-🚀 feat: add utility functions for DOM manipulation
-♻️ refactor: optimize JavaScript build system
+fix: resolve async/await error in cart API
+feat: add utility functions for DOM manipulation
+refactor: optimize JavaScript build system
 ```
 
 ### CSS/Styling
 ```
-🎨 style: update button component design system
-🎨 style: improve mobile responsive breakpoints
-🎨 style: add new color palette variables
+style: update button component design system
+style: improve mobile responsive breakpoints
+style: add new color palette variables
 ```
 
 ### Liquid Templates
 ```
-🔨 fix: resolve Liquid syntax error in product template
-🚀 feat: add new product variant selector
-♻️ refactor: optimize Liquid template performance
+fix: resolve Liquid syntax error in product template
+feat: add new product variant selector
+refactor: optimize Liquid template performance
 ```
 
 This commit convention ensures clear, consistent, and informative commit messages that help track project progress and facilitate collaboration.