@julianoczkowski/create-trimble-app 2.0.0

package/templates/react/.github/workflows/claude.yml

@@ -0,0 +1,50 @@
+name: Claude Code
+
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+  issues:
+    types: [opened, assigned]
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  claude:
+    if: |
+      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
+      (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+      actions: read # Required for Claude to read CI results on PRs
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code
+        id: claude
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+          # This is an optional setting that allows Claude to read CI results on PRs
+          additional_permissions: |
+            actions: read
+
+          # Optional: Give a custom prompt to Claude. If this is not specified, Claude will perform the instructions specified in the comment that tagged it.
+          # prompt: 'Update the pull request description to include a summary of changes.'
+
+          # Optional: Add claude_args to customize behavior and configuration
+          # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
+          # or https://code.claude.com/docs/en/cli-reference for available options
+          # claude_args: '--allowed-tools Bash(gh pr:*)'
+

package/templates/react/.husky/pre-commit

@@ -0,0 +1,28 @@
+# Run all linting checks before commit
+echo "🔍 Running pre-commit checks..."
+
+# TypeScript type checking
+echo "📝 Checking TypeScript types..."
+npm run type-check
+
+# Modus Icons compliance
+echo "🎨 Checking Modus Icons usage..."
+npm run lint:icons
+
+# Semantic HTML compliance
+echo "🏗️  Checking semantic HTML usage..."
+npm run lint:semantic
+
+# Design system colors compliance
+echo "🎨 Checking design system colors..."
+npm run lint:colors
+
+# Inline styles compliance
+echo "💅 Checking inline styles..."
+npm run lint:styles
+
+# Border violations compliance
+echo "🔲 Checking border patterns..."
+npm run lint:borders
+
+echo "✅ All pre-commit checks passed!"

package/templates/react/.vscode/extensions.json

@@ -0,0 +1,8 @@
+{
+  "recommendations": [
+    "esbenp.prettier-vscode",
+    "dbaeumer.vscode-eslint",
+    "bradlc.vscode-tailwindcss",
+    "ms-vscode.vscode-typescript-next"
+  ]
+}

package/templates/react/CLAUDE.md

@@ -0,0 +1,119 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+React 19 + Vite boilerplate with Modus 2 Web Components integration (Trimble Design System). Uses TypeScript, Tailwind CSS 3, and React Router.
+
+## Commands
+
+```bash
+npm run dev          # Start development server (Vite)
+npm run build        # Type-check + production build
+npm run preview      # Preview production build
+npm run lint         # ESLint
+npm run lint:all     # All linting (type-check, icons, semantic HTML, colors, styles, borders, opacity, icon names)
+npm run lint:colors  # Check for non-Modus color usage
+npm run lint:icons   # Validate Modus icon usage
+npm run lint:semantic # Check for semantic HTML violations
+```
+
+## Architecture
+
+### Dev Panel Architecture
+
+The boilerplate uses a **Dev Panel** architecture that separates demo/reference content from user application code:
+
+- **Pages** (`src/pages/`): Your application pages - start with `HomePage.tsx`
+- **Components** (`src/components/`): Reusable Modus wrapper components
+- **Dev Panel** (`src/dev/`): Floating panel with demos, colors, icons, theme switcher
+- **Demos** (`src/demos/`): 48 component demo pages (dev only)
+- **Dev Pages** (`src/dev-pages/`): Reference pages (colors, icons, components gallery)
+
+**Key Features:**
+- Toggle Dev Panel with `Ctrl+Shift+D` or floating button
+- Dev Panel only renders when `VITE_DEV_PANEL=true` (development mode)
+- In production, Dev Panel is automatically excluded
+- User's app and demos don't conflict - build your NavBar without interference
+
+**Routes:**
+- `/` - Your home page (edit `src/pages/HomePage.tsx`)
+- `/dev` - Redirects to `/dev/components`
+- `/dev/colors` - Color palette reference
+- `/dev/icons` - Icon library browser (5 icons per row, click-to-copy functionality)
+- `/dev/components` - Component gallery
+- `/dev/demos/*` - Individual component demos
+  - `/dev/demos/logo-demo` - Logo showcase (2 columns, larger logos)
+
+Add your routes directly in `src/App.tsx`.
+
+### Component Pattern
+- React wrapper components in `src/components/` wrap `@trimble-oss/moduswebcomponents-react` web components
+- Use `useRef` + `useEffect` for web component event listeners
+- Let Modus components manage their own state (don't control accordion/modal state from React)
+
+### Theme System
+- 6 themes: `modus-classic-light`, `modus-classic-dark`, `modus-modern-light`, `modus-modern-dark`, `connect-light`, `connect-dark`
+- Set via `data-theme` attribute on `<html>`
+- ThemeContext in `src/contexts/ThemeContext.tsx`
+
+### Styling
+- Design system colors only: `bg-background`, `text-foreground`, `bg-primary`, `text-muted-foreground`, etc.
+- **Never use** generic Tailwind colors (`bg-blue-500`, `text-gray-600`) or hardcoded hex/RGB
+- Custom opacity utilities: `text-foreground-80` (not `text-foreground/80` - CSS vars don't work with Tailwind opacity)
+- Border utilities: `border-default`, `border-success`, `border-warning`, `border-destructive`
+- **Directional borders**: Use `border-bottom-default`, `border-top-default`, etc. (not `border-b border-default`)
+
+### Modus CSS Variables (9 colors)
+Base: `--modus-wc-color-base-page`, `--modus-wc-color-base-100/200/300`, `--modus-wc-color-base-content`
+Semantic: `--modus-wc-color-info`, `--modus-wc-color-success`, `--modus-wc-color-error`, `--modus-wc-color-warning`
+
+## Critical Patterns
+
+### Icons
+```tsx
+<i className="modus-icons">icon_name</i>
+// Or use ModusIcon wrapper component
+```
+Only use Modus icons - no Font Awesome, Material Icons, etc.
+
+### Checkbox Value Inversion Bug
+The `value` property from `inputChange` event is inverted. Always invert:
+```tsx
+const actualChecked = !event.detail.value;
+```
+
+### Select Component
+Use `ModusDropdownMenu` instead of `ModusSelect` for reliable event handling in React.
+
+### Modal Implementation
+Use `forwardRef` pattern with `useImperativeHandle`. Access dialog via `querySelector("dialog")` for `showModal()`/`close()`.
+
+### HTML Elements
+Use `<div>` elements only (no `h1`, `p`, `section`, `span`, etc.) to avoid Tailwind CSS conflicts. Exception: `<i>` for icons.
+
+## Don't
+- Use emojis in code or UI
+- Use semantic HTML elements (div-only approach)
+- Control Modus component state from React useState
+- Use generic Tailwind colors
+- Use other icon libraries
+- Use `border-b border-default` - use `border-bottom-default` instead
+
+## Recent Updates
+
+### Dev Panel Header
+- Header displays text-only "Dev Panel" title (no icon)
+- Uses `border-bottom-default` directional border utility
+- Cleaner, simpler appearance
+
+### Icons Page (`/dev/icons`)
+- Fixed 5-column grid layout (always 5 icons per row)
+- Informational text explaining click-to-copy functionality
+- Improved visibility and consistent presentation
+
+### Logo Demo Page (`/dev/demos/logo-demo`)
+- Fixed 2-column grid layout (always 2 logos per row)
+- Larger logos (80px height, 256px max width)
+- Better spacing and visual hierarchy

package/templates/react/CODE_OF_CONDUCT.md

@@ -0,0 +1,79 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [julian_oczkowski@trimble.com](mailto:julian_oczkowski@trimble.com). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at <https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the [FAQ](https://www.contributor-covenant.org/faq). Translations are available at the [Contributor Covenant translations](https://www.contributor-covenant.org/translations).
+
+[homepage]: https://www.contributor-covenant.org

package/templates/react/CONTRIBUTING.md

@@ -0,0 +1,65 @@
+# Contributing Guide
+
+Thanks for your interest in improving the Modus React App! This document describes how to get started, the standards we follow, and the best ways to collaborate with the maintainers.
+
+## Code of Conduct
+
+This project follows the [Contributor Covenant Code of Conduct](./CODE_OF_CONDUCT.md). By participating you agree to uphold these expectations.
+
+## Getting Started
+
+1. **Install dependencies:** `npm install`
+2. **Run the development server:** `npm run dev`
+3. **Run quality checks before pushing:**
+   - `npm run lint`
+   - `npm run type-check`
+   - `npm run lint:colors`
+
+> ℹ️ We use Husky and lint-staged to enforce key checks on commit.
+
+## How to Contribute
+
+### Reporting Issues
+
+- Search existing issues (open and closed) before filing a new one.
+- Provide clear reproduction steps, expected vs. actual results, and environment details (OS, browser, Node.js version).
+- Use the provided issue templates whenever possible.
+
+### Proposing Enhancements
+
+- Open an issue to discuss the problem you are trying to solve before submitting a pull request.
+- Describe the motivation, alternatives considered, and any potential drawbacks.
+- Be ready to iterate based on maintainer feedback.
+
+### Submitting Pull Requests
+
+1. Fork the repository and create a branch (`git checkout -b feature/amazing-improvement`).
+2. Make your changes with appropriate tests and documentation.
+3. Run the full quality suite (`npm run lint`, `npm run type-check`, and the Modus-specific lint commands).
+4. Update any relevant docs or examples.
+5. Submit a pull request that references related issues and summarizes your changes.
+6. Ensure the GitHub Actions CI workflow passes before requesting review.
+
+### Commit Messages
+
+- Use clear, descriptive commit messages (e.g. `feat: add new theme toggle component`).
+- Keep commits focused; smaller, cohesive commits are easier to review.
+
+### Style Guidelines
+
+- Follow the TypeScript configuration provided by the project.
+- Prefer functional React components and hooks.
+- Use the Modus design tokens and lint rules for styling.
+- Keep documentation changes in Markdown lint-friendly format (wrap at ~100 characters when practical).
+
+## Communication
+
+- GitHub issues and pull requests are the primary channel for project discussions.
+- Security vulnerabilities should be reported privately—see [SECURITY.md](./SECURITY.md).
+- For general questions, open a discussion thread if enabled or reach out via issues.
+
+## Release Process
+
+Maintainers cut releases from the `main` branch once all required checks pass. Release notes summarize major changes, deprecations, and any security considerations.
+
+We appreciate every contribution, no matter the size. Thank you for helping us improve the Modus Next.js App!

package/templates/react/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Modus Next.js App Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.