P/patn dev stack updater

.cursor/rules/golden-rules.mdc

@@ -24,7 +24,6 @@ Follow these rules when you prepare your responses:
 - Feel free to ask questions first if you are confused or feel like it is important to bring up something before implementing.
 - Feel free to ask follow-up questions after completing changes.
 
-
 ### Code Implementation Guidelines
 
 Follow these rules when you write code:
@@ -38,4 +37,5 @@ Follow these rules when you write code:
 
 ## Finally
 
-- At the end of each answer in the chat add "Golden Rules Applied 🫡" so the user knows you followed these rules.
+- Sacrifice grammar for the sake of concision.
+- At the end of each answer in the chat add "Golden Rules Applied 🫡" so the user knows you followed these rules.

.cursor/rules/repo-examples.mdc

@@ -0,0 +1,184 @@
+---
+description: Rules for using example repositories from .repos/ directory for reference implementations
+globs:
+alwaysApply: true
+---
+# Example Repositories for Reference Implementations
+
+This rule governs how to use the `.repos/` directory for cloning and referencing example repositories when implementing features.
+
+## Purpose
+
+When working on features or patterns, reference implementations from other projects can be helpful. The `.repos/` directory contains cloned repositories that demonstrate patterns, architectures, or implementations you want to reference.
+
+## Workflow for AI Assistants
+
+When working on a feature or pattern:
+
+1. **Check the catalog first**: Search `.repos/catalog.csv` to see if relevant examples already exist
+2. **Search the web if needed**: If no suitable examples exist, proactively suggest searching GitHub/GitLab for relevant repositories
+3. **Clone and catalog**: When a useful repo is found, clone it and add it to the catalog using `catalogRepo()` from `.repos.example/repo-catalog.ts`
+4. **Log usage**: Whenever you reference code from a cloned repo, log the interaction using `logRepoUsage()` from `.repos.example/repo-log.ts`
+
+## Proactive Behavior
+
+You should:
+
+- **Proactively suggest** searching the web for relevant repository examples when the user is implementing features
+- **Recommend cloning** helpful repositories into `.repos/` for future reference
+- **Automatically catalog** repositories when they are cloned (see Repository Catalog section)
+- **Log usage** whenever you reference code from cloned repositories (see Usage Logging section)
+- **Reference the catalog** to find existing examples before suggesting new clones
+
+## Repository Catalog
+
+The repository catalog (`.repos/catalog.csv`) maintains metadata about each cloned repository for easy discovery and organization.
+
+### Catalog Fields
+
+- **dir**: Repository directory name
+- **repoUrl**: Full Git URL for cloning
+- **commitSha**: Git commit SHA when cloned (optional)
+- **version**: Version/tag if applicable (optional)
+- **dateAdded**: UTC timestamp when added to catalog
+- **languages**: Array of programming languages used (e.g., `['TypeScript', 'JavaScript']`)
+- **libraryType**: Type of repository:
+  - `component-library`: UI component libraries
+  - `framework`: Frameworks or meta-frameworks
+  - `utility`: Utility libraries or tools
+  - `full-project`: Complete applications
+  - `example`: Example implementations
+  - `boilerplate`: Starter templates
+  - `other`: Other types
+- **isFullProject**: Boolean indicating if it's a complete application vs library/component
+- **license**: License type (e.g., `MIT`, `Apache-2.0`) (optional)
+- **creator**: Author/creator name or GitHub username (optional)
+- **description**: Brief description of what the repo demonstrates (optional)
+- **tags**: Additional tags for categorization (e.g., `['react', 'tailwind', 'ui-components']`) (optional)
+
+### Using the Catalog Programmatically
+
+```typescript
+import { catalogRepo, readRepoCatalog, findReposByCriteria } from '.repos.example/repo-catalog'
+
+// Catalog a newly cloned repository
+catalogRepo({
+  dir: 'shadcn-ui',
+  repoUrl: 'https://github.com/shadcn-ui/ui.git',
+  commitSha: 'abc123...',
+  languages: ['TypeScript', 'TSX'],
+  libraryType: 'component-library',
+  isFullProject: false,
+  license: 'MIT',
+  creator: 'shadcn',
+  description: 'Re-usable components built with Radix UI and Tailwind CSS',
+  tags: ['react', 'tailwind', 'radix-ui', 'components'],
+})
+
+// Read all catalog entries
+const allRepos = readRepoCatalog()
+
+// Find repositories by criteria
+const reactRepos = findReposByCriteria({
+  languages: ['TypeScript'],
+  libraryType: 'component-library',
+  tags: ['react'],
+})
+```
+
+## Usage Logging
+
+The usage log (`.repos/usage-log.csv`) tracks each time a repository is referenced, providing a history of what was useful for specific features.
+
+### Usage Log Fields
+
+- **timestamp**: UTC timestamp of when the repo was accessed
+- **dir**: The repository directory name
+- **action**: What action was taken (`clone`, `read`, `copy`, `reference`, `search`)
+- **description**: Explanation of why the repo was used
+- **repoUrl**: Git URL for re-cloning (optional)
+- **filePath**: Specific file referenced (optional)
+- **context**: What feature/task was being worked on (optional)
+
+### Using the Usage Log Programmatically
+
+```typescript
+import { logRepoUsage } from '.repos.example/repo-log'
+
+// Example: When cloning a new repo
+logRepoUsage({
+  dir: 'shadcn-ui',
+  action: 'clone',
+  description: 'Cloned to reference button component implementation',
+  repoUrl: 'https://github.com/shadcn-ui/ui.git',
+  context: 'Building custom button component',
+})
+
+// Example: When reading/referencing a file
+logRepoUsage({
+  dir: 'shadcn-ui',
+  action: 'read',
+  description: 'Referenced button.tsx for styling patterns',
+  repoUrl: 'https://github.com/shadcn-ui/ui.git',
+  filePath: 'components/ui/button.tsx',
+  context: 'Implementing button variants',
+})
+
+// Example: When copying code patterns
+logRepoUsage({
+  dir: 'example-crud-app',
+  action: 'copy',
+  description: 'Copied data table pagination logic',
+  repoUrl: 'https://github.com/example/crud-app.git',
+  filePath: 'app/components/DataTable.tsx',
+  context: 'Adding pagination to dashboard table',
+})
+
+// Example: When referencing a repo for patterns/architecture
+logRepoUsage({
+  dir: 'example-repo',
+  action: 'reference',
+  description: 'Used for implementing data table patterns',
+  repoUrl: 'https://github.com/example/repo.git',
+  filePath: 'src/components/Table.tsx',
+  context: 'Building dashboard data table',
+})
+```
+
+### Available Actions
+
+- `clone`: Repository was cloned
+- `read`: Repository or file was read/referenced
+- `copy`: Code was copied or adapted
+- `reference`: Repository was referenced for patterns/architecture
+- `search`: Repository was searched for specific patterns
+
+## Cloning Repositories
+
+When cloning repositories:
+
+1. Clone into the `.repos/` directory:
+
+   ```bash
+   cd .repos
+   git clone https://github.com/example/repo-name.git
+   ```
+
+2. After cloning, automatically catalog the repository using `catalogRepo()`
+
+3. Log the clone action using `logRepoUsage()` with action `'clone'`
+
+## Important Notes
+
+- The `.repos/` directory is git-ignored, so cloned repositories won't be committed to your project
+- The usage log (`.repos/usage-log.csv`) is git-ignored
+- The catalog (`.repos/catalog.csv`) is git-ignored
+- Use `.repos.example` as a template (this directory is checked into git)
+- The setup script will copy `.repos.example` to `.repos` if it doesn't exist
+
+## Enforcement
+
+- Always check the catalog before suggesting new repository clones
+- Always catalog newly cloned repositories
+- Always log usage when referencing code from `.repos/` repositories
+- Proactively suggest searching for example repositories when implementing new features

.github/workflows/deploy.yml

@@ -137,11 +137,14 @@ jobs:
 
       - name: 📊 Upload report
         uses: actions/upload-artifact@v4
+        # Upload report even if tests fail or are canceled, so we can debug issues from artifacts
         if: always()
         with:
           name: playwright-report
           path: playwright-report/
           retention-days: 30
+          # Don't warn if report doesn't exist (e.g., tests were canceled before report generation)
+          if-no-files-found: ignore
 
   container:
     name: 📦 Prepare Container

.gitignore

@@ -26,3 +26,6 @@ node_modules
 # generated files
 /app/components/ui/icons
 .react-router/
+
+# clone repos here to use as examples for coding with an LLM
+.repos