bsmnt 0.2.0 → 0.2.5

package/src/templates/next-experiments/.github/workflows/lighthouse-to-slack.yml

@@ -1,136 +0,0 @@
-# Lighthouse Performance Reports
-#
-# Runs Lighthouse on Vercel deployments and posts results as commit comments.
-# Our GitHub → Slack integration forwards these to Slack automatically.
-#
-# Required GitHub Secrets:
-#   VERCEL_TOKEN - Vercel API token (Settings → Tokens)
-
-name: Lighthouse
-
-on:
-  push:
-    branches: [main]
-  pull_request:
-    types: [opened, synchronize]
-    branches: [main]
-    paths:
-      # Only runs when relevant files change
-      - 'app/**'
-      - 'components/**'
-      - 'lib/**'
-      - 'public/**'
-      - 'package.json'
-      - 'package-lock.json'
-      - 'next.config.**'
-
-permissions:
-  contents: write
-  pull-requests: write
-  actions: read
-
-jobs:
-  lighthouse:
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-
-    steps:
-      - name: Discover Vercel Project
-        id: vercel_info
-        env:
-          VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}
-        run: |
-          project_name="${GITHUB_REPOSITORY##*/}"
-          echo "Looking for Vercel project: $project_name"
-
-          # Get team ID for basement.studio
-          teams=$(curl -s -H "Authorization: Bearer $VERCEL_TOKEN" "https://api.vercel.com/v2/teams")
-          team_id=$(echo "$teams" | jq -r '.teams[] | select(.slug=="basement") | .id')
-          echo "Team ID: $team_id"
-
-          # Get project ID by matching repo name
-          projects=$(curl -s -H "Authorization: Bearer $VERCEL_TOKEN" "https://api.vercel.com/v9/projects?teamId=$team_id")
-          project_id=$(echo "$projects" | jq -r ".projects[] | select(.name==\"$project_name\") | .id")
-          echo "Project ID: $project_id"
-
-          echo "team_id=$team_id" >> $GITHUB_OUTPUT
-          echo "project_id=$project_id" >> $GITHUB_OUTPUT
-
-      - name: Get Vercel Preview URL
-        id: vercel_url
-        uses: zentered/vercel-preview-url@v1.4.0
-        env:
-          VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}
-        with:
-          vercel_team_id: ${{ steps.vercel_info.outputs.team_id }}
-          vercel_project_id: ${{ steps.vercel_info.outputs.project_id }}
-
-      - name: Wait for Deployment
-        id: await
-        uses: UnlyEd/github-action-await-vercel@v2.0.0
-        env:
-          VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}
-        with:
-          deployment-url: ${{ steps.vercel_url.outputs.preview_url }}
-          timeout: 300
-          poll-interval: 10
-        continue-on-error: true
-
-      - name: Run Lighthouse
-        if: steps.await.outcome == 'success'
-        id: lighthouse
-        uses: treosh/lighthouse-ci-action@v12
-        env:
-          LHCI_BUILD_CONTEXT__CURRENT_HASH: ${{ github.sha }}
-        with:
-          urls: https://${{ steps.vercel_url.outputs.preview_url }}
-          uploadArtifacts: true
-          temporaryPublicStorage: true
-
-      - name: Format Results
-        id: format
-        uses: actions/github-script@v8
-        env:
-          DEPLOYMENT_FAILED: ${{ steps.await.outcome != 'success' }}
-          PREVIEW_URL: ${{ steps.vercel_url.outputs.preview_url }}
-          MANIFEST: ${{ steps.lighthouse.outputs.manifest }}
-          LINKS: ${{ steps.lighthouse.outputs.links }}
-        with:
-          script: |
-            if (process.env.DEPLOYMENT_FAILED === 'true') {
-              core.setOutput('comment', '⚠️ Vercel deployment failed or timed out. Lighthouse audit skipped.');
-              return;
-            }
-
-            try {
-              const manifest = JSON.parse(process.env.MANIFEST);
-              const links = JSON.parse(process.env.LINKS);
-              const previewUrl = process.env.PREVIEW_URL;
-
-              const scores = manifest[0].summary;
-              const reportUrl = Object.values(links)[0];
-
-              const emoji = (score) => score >= 0.9 ? '🟢' : score >= 0.5 ? '🟠' : '🔴';
-              const format = (score) => Math.round(score * 100);
-
-              const comment = [
-                `⚡️ [Lighthouse report](${reportUrl}) for this commit:`,
-                '',
-                `${emoji(scores.performance)} Performance: ${format(scores.performance)}`,
-                `${emoji(scores.accessibility)} Accessibility: ${format(scores.accessibility)}`,
-                `${emoji(scores['best-practices'])} Best Practices: ${format(scores['best-practices'])}`,
-                `${emoji(scores.seo)} SEO: ${format(scores.seo)}`,
-                '',
-                `*Tested on [${previewUrl}](https://${previewUrl})*`
-              ].join('\n');
-
-              core.setOutput('comment', comment);
-            } catch (error) {
-              console.error('Error:', error);
-              core.setOutput('comment', '⚠️ Failed to generate Lighthouse report. Check workflow logs.');
-            }
-
-      - name: Post Commit Comment
-        uses: peter-evans/commit-comment@v4
-        with:
-          body: ${{ steps.format.outputs.comment }}

package/src/templates/next-webgl/.cursor/rules/README.md

@@ -1,184 +0,0 @@
-# Cursor Rules Documentation
-
-This directory contains consolidated Cursor AI rules for the Satus project. The rules are organized into 5 focused files for easy maintenance and efficient AI context loading.
-
-## 📁 File Structure
-
-### 1. `main.mdc` - Project Overview & Cross-Cutting Concerns
-**Purpose**: High-level overview and concerns that apply across the entire project
-
-**Contents**:
-- Technology stack (Next.js 16+, React 19+, Tailwind v4, Biome, Bun)
-- React 19+ new features (`<Activity />`, `useEffectEvent`, `cacheSignal`)
-- Next.js 16 Cache Components gotchas and best practices
-- File organization
-- React Compiler & memoization guidelines (single source of truth)
-- Image optimization guidelines (single source of truth)
-- Development vs production guidelines (single source of truth)
-- Core utility libraries (`@/utils`)
-
-**When to reference**: Starting a new project, understanding the tech stack, cross-cutting concerns
-
----
-
-### 2. `components.mdc` - React Component Patterns & WebGL
-**Purpose**: All React component patterns including standard components and WebGL/Three.js
-
-**Contents**:
-- Component structure and imports
-- Props interfaces and React 19 ref handling
-- Forms and responsive design
-- Performance best practices (code splitting)
-- Error handling
-- WebGL/Three.js setup and patterns
-- React Three Fiber
-- Drei components
-- Custom shaders
-- Animation and interaction
-- Post-processing
-
-**When to reference**: Building React components, creating WebGL experiences, working with Three.js
-
----
-
-### 3. `styling.mdc` - CSS Modules & Tailwind CSS v4
-**Purpose**: All styling approaches including CSS Modules and Tailwind CSS v4
-
-**Contents**:
-- CSS Modules (file naming, class naming, imports)
-- Responsive design (viewport functions, breakpoints, grid system)
-- Typography and colors
-- Animations and transitions
-- Tailwind CSS v4 (CSS-first configuration, theme variables, new features)
-- 3D transforms, gradients, shadows
-- New variants (composable, `starting`, `not-*`, `nth-*`)
-- Custom extensions (`@utility`, `@variant`, `@plugin`)
-- Breaking changes and migration
-- Project-specific custom utilities (`b-*` classes)
-- PostCSS functions
-
-**When to reference**: Styling components, using Tailwind, creating responsive designs
-
----
-
-### 4. `integrations.mdc` - Third-Party Integrations
-**Purpose**: Guidelines for all third-party service integrations
-
-**Contents**:
-- **Sanity CMS**: Configuration, schema management, GROQ queries, visual editing, TypeScript generation, cacheSignal integration
-- **Shopify**: API configuration, product management, cart operations, cacheSignal integration
-- General best practices (environment variables, API resilience, error handling)
-- Cache Components gotchas for integrations (user-specific data, real-time data)
-- Type safety and performance
-- Security and integration management
-- Webhook handling
-
-**When to reference**: Integrating with Sanity, Shopify, or other third-party services
-
----
-
-### 5. `architecture.mdc` - Architecture Patterns & Best Practices
-**Purpose**: Architectural patterns, state management, routing, and code quality guidelines
-
-**Contents**:
-- Type safety (TypeScript configuration)
-- State management (React state, Zustand)
-- Routing & navigation (Next.js App Router, Link component)
-- Metadata & SEO
-- Performance (server components, code splitting, caching)
-- Cache Components (Next.js 16) - Suspense, invalidation, gotchas
-- Security (environment variables, input validation, authentication)
-- Testing & debugging (unit tests, debugging tools, error boundaries)
-- Code quality (linting, formatting, code organization)
-- Development workflow (package manager, git workflow, client/server boundaries)
-
-**When to reference**: Architectural decisions, state management, routing patterns, code quality
-
----
-
-## 🎯 Quick Reference Guide
-
-### I want to...
-
-- **Start a new feature** → Read `main.mdc` for overview, then `architecture.mdc` for patterns
-- **Build a React component** → `components.mdc`
-- **Add WebGL/Three.js** → `components.mdc` § WebGL Components & Activity Integration
-- **Style with CSS Modules** → `styling.mdc` § CSS Modules
-- **Style with Tailwind** → `styling.mdc` § Tailwind CSS v4
-- **Use custom utilities** → `styling.mdc` § Project-Specific Custom Utilities
-- **Integrate Sanity CMS** → `integrations.mdc` § Sanity CMS Integration
-- **Integrate Shopify** → `integrations.mdc` § Shopify Integration
-- **Manage state** → `architecture.mdc` § State Management
-- **Add routing** → `architecture.mdc` § Routing & Navigation
-- **Optimize performance** → `architecture.mdc` § Performance
-- **Handle security** → `architecture.mdc` § Security
-- **Debug issues** → `architecture.mdc` § Testing & Debugging
-- **Understand React Compiler** → `main.mdc` § React Compiler & Memoization
-- **Handle images** → `main.mdc` § Image Optimization (`@/components/ui/image`)
-- **Dev vs prod differences** → `main.mdc` § Development vs Production
-- **Use utility functions** → `main.mdc` § Core Utility Libraries (`@/utils`)
-
----
-
-## 📝 Maintenance Guidelines
-
-### When Editing Rules
-
-1. **Avoid Duplication**: If content applies to multiple areas, put it in `main.mdc` and reference it
-2. **Use Cross-References**: Link to other sections instead of duplicating content
-3. **Keep It Focused**: Each file should maintain its specific purpose
-4. **Update Dates**: Update the "Last updated" date when making changes
-5. **Check Dependencies**: When updating one file, check if related files need updates
-
-### Example Cross-Reference Pattern
-
-```markdown
-<!-- In components.mdc -->
-## Performance Optimization
-See main.mdc § React Compiler & Memoization for optimization guidelines.
-```
-
-### Adding New Content
-
-**Ask yourself**:
-- Is this component-specific? → `components.mdc`
-- Is this styling-related? → `styling.mdc`
-- Is this an integration? → `integrations.mdc`
-- Is this architectural? → `architecture.mdc`
-- Is this cross-cutting? → `main.mdc`
-
----
-
-## 🚀 For Developers
-
-### Quick Setup
-1. These rules are automatically loaded by Cursor AI
-2. All files have `alwaysApply: true` in frontmatter
-3. Files apply to: `*.tsx, *.jsx, *.css, *.js, *.ts`
-
-### Contributing
-When adding new guidelines:
-1. Choose the appropriate file
-2. Follow existing formatting patterns
-3. Add clear examples
-4. Update this README if needed
-5. Keep content focused and actionable
-
----
-
-## 📊 File Statistics
-
-| File | Purpose | Key Topics |
-|------|---------|------------|
-| `main.mdc` | Overview & Cross-cutting | Tech stack, React 19+ features, Cache Components, React Compiler, Images, Dev/Prod |
-| `components.mdc` | React & WebGL | Components, Forms, WebGL, Three.js, Shaders, Activity |
-| `styling.mdc` | All Styling | CSS Modules, Tailwind v4, Responsive, Custom utilities |
-| `integrations.mdc` | Third-party Services | Sanity, Shopify, Cache Components, cacheSignal |
-| `architecture.mdc` | Patterns & Quality | State, Routing, Performance, Cache Components, Security, Testing |
-
----
-
-Last updated: 2026-01-26
-
-For questions or suggestions about these rules, contact the development team.
-