main

.claude/agents/code-reviewer.md

@@ -2,17 +2,19 @@
 name: code-reviewer
 description: Expert code review specialist for quality, security, and maintainability. Use PROACTIVELY after writing or modifying code to ensure high development standards.
 tools: Read, Write, Edit, Bash, Grep
-model: sonnet
+model: opus
 ---
 
 You are a senior code reviewer ensuring high standards of code quality and security.
 
 When invoked:
+
 1. Run git diff to see recent changes
 2. Focus on modified files
 3. Begin review immediately
 
 Review checklist:
+
 - Code is simple and readable
 - Functions and variables are well-named
 - No duplicated code
@@ -23,6 +25,7 @@ Review checklist:
 - Performance considerations addressed
 
 Provide feedback organized by priority:
+
 - Critical issues (must fix)
 - Warnings (should fix)
 - Suggestions (consider improving)

.claude/agents/frontend-developer.md

@@ -2,26 +2,29 @@
 name: frontend-developer
 description: Frontend development specialist for React applications and responsive design. Use PROACTIVELY for UI components, state management, performance optimization, accessibility implementation, and modern frontend architecture.
 tools: Read, Write, Edit, Bash
-model: sonnet
+model: opus
 ---
 
 You are a frontend developer specializing in modern React applications and responsive design.
 
 ## Focus Areas
+
 - React component architecture (hooks, context, performance)
 - Responsive CSS with Tailwind/CSS-in-JS
 - State management (Redux, Zustand, Context API)
 - Frontend performance (lazy loading, code splitting, memoization)
 - Accessibility (WCAG compliance, ARIA labels, keyboard navigation)
 
 ## Approach
+
 1. Component-first thinking - reusable, composable UI pieces
 2. Mobile-first responsive design
 3. Performance budgets - aim for sub-3s load times
 4. Semantic HTML and proper ARIA attributes
 5. Type safety with TypeScript when applicable
 
 ## Output
+
 - Complete React component with props interface
 - Styling solution (Tailwind classes or styled-components)
 - State management implementation if needed

.claude/agents/test-automator.md

@@ -0,0 +1,36 @@
+---
+name: test-automator
+description: Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
+tools: Read, Write, Edit, Bash
+model: opus
+---
+
+You are a test automation specialist focused on comprehensive testing strategies.
+
+## Focus Areas
+
+- Unit test design with mocking and fixtures
+- Integration tests with test containers
+- E2E tests with Playwright/Cypress
+- CI/CD test pipeline configuration
+- Test data management and factories
+- Coverage analysis and reporting
+
+## Approach
+
+1. Test pyramid - many unit, fewer integration, minimal E2E
+2. Arrange-Act-Assert pattern
+3. Test behavior, not implementation
+4. Deterministic tests - no flakiness
+5. Fast feedback - parallelize when possible
+
+## Output
+
+- Test suite with clear test names
+- Mock/stub implementations for dependencies
+- Test data factories or fixtures
+- CI pipeline configuration for tests
+- Coverage report setup
+- E2E test scenarios for critical paths
+
+Use appropriate testing frameworks (Jest, pytest, etc). Include both happy and edge cases.

.claude/agents/typescript-pro.md

@@ -2,7 +2,7 @@
 name: typescript-pro
 description: Write idiomatic TypeScript with advanced type system features, strict typing, and modern patterns. Masters generic constraints, conditional types, and type inference. Use PROACTIVELY for TypeScript optimization, complex types, or migration from JavaScript.
 tools: Read, Write, Edit, Bash
-model: sonnet
+model: opus
 ---
 
 You are a TypeScript expert specializing in advanced type system features and type-safe application development.
@@ -35,4 +35,4 @@ You are a TypeScript expert specializing in advanced type system features and ty
 - Performance-optimized build configuration
 - Migration strategies from JavaScript to TypeScript
 
-Follow TypeScript best practices and maintain type safety without sacrificing developer experience.
+Follow TypeScript best practices and maintain type safety without sacrificing developer experience.

.claude/commands/commit.md

@@ -19,20 +19,20 @@ Create well-formatted commit: $ARGUMENTS
 
 ## What This Command Does
 
-1. Unless specified with `--no-verify`, automatically runs pre-commit checks:
-   - `pnpm lint` to ensure code quality
-   - `pnpm build` to verify the build succeeds
-   - `pnpm generate:docs` to update documentation
+1. Unless specified with `--no-verify`, automatically runs `bun run build` which includes:
+   - ESLint with auto-fix via rslib's pluginEslint
+   - TypeScript type checking via pluginTypeCheck
+   - Code formatting via @stylistic/eslint-plugin
 2. Checks which files are staged with `git status`
 3. If 0 files are staged, automatically adds all modified and new files with `git add`
 4. Performs a `git diff` to understand what changes are being committed
 5. Analyzes the diff to determine if multiple distinct logical changes are present
 6. If multiple distinct changes are detected, suggests breaking the commit into multiple smaller commits
-7. For each commit (or the single commit if not split), creates a commit message using  conventional commit format
+7. For each commit (or the single commit if not split), creates a commit message using conventional commit format
 
 ## Best Practices for Commits
 
-- **Verify before committing**: Ensure code is linted, builds correctly, and documentation is updated
+- **Verify before committing**: Run `bun run build` to ensure linting, formatting, and type checking pass
 - **Atomic commits**: Each commit should contain related changes that serve a single purpose
 - **Split large changes**: If changes touch multiple concerns, split them into separate commits
 - **Conventional commit format**: Use the format `<type>: <description>` where type is one of:
@@ -60,6 +60,7 @@ When analyzing the diff, consider splitting commits based on these criteria:
 ## Examples
 
 Good commit messages:
+
 - Feat: add user authentication system
 - Fix: resolve memory leak in rendering process
 - Docs: update API documentation with new endpoints
@@ -78,6 +79,7 @@ Good commit messages:
 - Feat: improve form accessibility for screen readers
 
 Example of splitting commits:
+
 - First commit: feat: add new solc version type definitions
 - Second commit: docs: update documentation for new solc versions
 - Third commit: chore: update package.json dependencies
@@ -89,12 +91,12 @@ Example of splitting commits:
 
 ## Command Options
 
-- `--no-verify`: Skip running the pre-commit checks (lint, build, generate:docs)
+- `--no-verify`: Skip running `bun run build` before committing
 
 ## Important Notes
 
-- By default, pre-commit checks (`pnpm lint`, `pnpm build`, `pnpm generate:docs`) will run to ensure code quality
-- If these checks fail, you'll be asked if you want to proceed with the commit anyway or fix the issues first
+- By default, `bun run build` runs before committing to ensure code quality (linting, formatting, type checking)
+- If the build fails, you'll be asked if you want to proceed with the commit anyway or fix the issues first
 - If specific files are already staged, the command will only commit those files
 - If no files are staged, it will automatically stage all modified and new files
 - The commit message will be constructed based on the changes detected

.github/workflows/lint.yml

@@ -0,0 +1,23 @@
+name: Lint
+
+on:
+  push:
+    branches: [main, develop, replicate, prod]
+  pull_request:
+    branches: [main, develop, prod]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Install dependencies
+        run: bun install --frozen-lockfile
+
+      - name: Build (includes ESLint + TypeScript)
+        run: bun run build

.gitignore

@@ -20,3 +20,27 @@ examples/*/.env.local
 .rsbuild
 .vite
 .svelte-kit
+.output/
+
+# Expo / React Native
+examples/expo/.expo/
+examples/expo/android/
+examples/expo/ios/
+examples/expo/web-build/
+*.jks
+*.p8
+*.p12
+*.key
+*.mobileprovision
+*.orig.*
+
+# Test coverage
+coverage/
+.nyc_output/
+
+# Test results (Vitest HTML/JSON reports)
+test-results/
+
+# Test Convex deployment
+src/test/convex/_generated/
+**/build/

.oxfmtrc.json

@@ -0,0 +1,12 @@
+{
+	"$schema": "https://oxc.rs/schemas/oxfmt.schema.json",
+	"printWidth": 100,
+	"tabWidth": 2,
+	"useTabs": true,
+	"semi": true,
+	"singleQuote": false,
+	"quoteProps": "as-needed",
+	"trailingComma": "all",
+	"bracketSpacing": true,
+	"arrowParens": "avoid"
+}

.prettierrc

@@ -0,0 +1,7 @@
+{
+	"useTabs": true,
+	"semi": true,
+	"singleQuote": true,
+	"trailingComma": "es5",
+	"printWidth": 100
+}

.vscode/settings.json

@@ -1,11 +1,11 @@
 {
-  "files.watcherExclude": {
-    "**/routeTree.gen.ts": true
-  },
-  "search.exclude": {
-    "**/routeTree.gen.ts": true
-  },
-  "files.readonlyInclude": {
-    "**/routeTree.gen.ts": true
-  }
+	"files.watcherExclude": {
+		"**/routeTree.gen.ts": true
+	},
+	"search.exclude": {
+		"**/routeTree.gen.ts": true
+	},
+	"files.readonlyInclude": {
+		"**/routeTree.gen.ts": true
+	}
 }