@nebulit/embuilder 0.1.39

package/templates/README.md

@@ -0,0 +1,178 @@
+# Event Model Project
+
+This project uses event-model driven development with Claude Code and EMBuilder.
+
+## Quick Start
+
+### Available Commands
+
+Use these commands in Claude Code to generate slices from your event model:
+
+**Event Model Skills:**
+```
+/state-change-slice   # Generate a command handler slice
+/state-view-slice     # Generate a read model/projection slice
+/automation-slice     # Generate a background automation slice
+```
+
+**Configuration:**
+```
+/fetch-config         # Fetch config.json from event model app (localhost:3001)
+```
+
+**Yeoman Generator Skills:**
+```
+/gen-skeleton         # Generate Supabase backend skeleton app
+/gen-state-change     # Generate state change slices from config.json
+/gen-state-view       # Generate state view slices from config.json
+/gen-automation       # Generate automation slices from config.json
+/gen-ui               # Set up React UI with shadcn/ui and Supabase
+```
+
+## How to Invoke
+
+### Using Event Model Skills
+
+1. **Generate a State Change Slice (Command Handler)**
+   ```
+   In Claude Code, type: /state-change-slice
+   ```
+   Claude will:
+   - Find your event model file
+   - Ask you which command to implement
+   - Generate CommandHandler.ts with business logic
+   - Create routes.ts for HTTP endpoints
+   - Generate tests
+   - Run the tests automatically
+
+2. **Generate a State View Slice (Read Model)**
+   ```
+   In Claude Code, type: /state-view-slice
+   ```
+   Claude will:
+   - Find your event model
+   - Ask which read model to implement
+   - Generate Projection.ts with event handlers
+   - Create query endpoints
+   - Generate tests
+   - Run the tests
+
+3. **Generate an Automation Slice (Background Process)**
+   ```
+   In Claude Code, type: /automation-slice
+   ```
+   Claude will:
+   - Find your event model
+   - Ask which automation to implement
+   - Generate processor.ts with CRON logic
+   - Create background job handlers
+   - Generate tests
+   - Run the tests
+
+### Using Yeoman Generator Skills
+
+1. **Fetch Configuration from Event Model App**
+   ```
+   In Claude Code, type: /fetch-config
+   ```
+   This will start a server and fetch config.json from your running event model app.
+
+2. **Generate Multiple Slices from Config**
+   ```
+   In Claude Code, type: /gen-state-change
+   ```
+   Or use `/gen-state-view` or `/gen-automation` to generate slices based on your config.json.
+
+3. **Bootstrap a New Project**
+   ```
+   In Claude Code, type: /gen-skeleton
+   ```
+   This will create a complete Supabase backend skeleton.
+
+4. **Set Up UI**
+   ```
+   In Claude Code, type: /gen-ui
+   ```
+   This will scaffold a React UI with shadcn/ui and Supabase integration.
+
+## Project Structure
+
+Your generated slices will follow this structure:
+
+```
+src/slices/{slice-name}/
+├── CommandHandler.ts    # Business logic (state-change slices)
+├── Projection.ts        # Read model (state-view slices)
+├── processor.ts         # CRON automation (automation slices)
+├── routes.ts            # HTTP API endpoints
+├── {SliceName}.test.ts  # Automated tests
+└── ui/                  # UI components (optional)
+```
+
+## Event Model Location
+
+Make sure your event model JSON files are in one of these locations:
+- `src/events/`
+- `events/`
+- Root directory
+
+Claude Code will automatically find and read your event model.
+
+## Template Files
+
+This project includes the following template files:
+
+- **`Claude.md`** - Project-specific configuration for Claude Code
+- **`AGENTS.md`** - Track learnings and patterns from development
+- **`ralph.sh`** - Autonomous agent loop for continuous development
+- **`prompt.md`** - Agent instructions for automated development
+
+## Development Workflow
+
+1. **Define your event model** in JSON format
+2. **Run a Claude skill** (e.g., `/state-change-slice`)
+3. **Claude generates the code** with tests
+4. **Tests run automatically** to verify correctness
+5. **Iterate** - modify the model and regenerate as needed
+
+## Autonomous Development with ralph.sh
+
+Run the autonomous agent loop:
+
+```bash
+./ralph.sh
+```
+
+This will:
+- Read instructions from `prompt.md`
+- Execute development tasks automatically
+- Track learnings in `AGENTS.md`
+- Continue until the task is complete
+
+## Need Help?
+
+- Check the main EMBuilder documentation: https://github.com/dilgerma/embuilder
+- Review the event model specifications in `src/events/`
+- Ask Claude Code for guidance on any command
+
+## EMBuilder Commands
+
+If you need to reinstall or update EMBuilder:
+
+```bash
+# Install/update skills
+npx @dilgerma/embuilder install
+
+# Install with template files
+npx @dilgerma/embuilder install --with-templates
+
+# Check installation status
+npx @dilgerma/embuilder status
+
+# Uninstall
+npx @dilgerma/embuilder uninstall
+```
+
+---
+
+Generated by EMBuilder - Event-Model driven development for Claude Code

package/templates/backend/.env

@@ -0,0 +1,9 @@
+SUPABASE_URL=https://<project-id>.supabase.co
+SUPABASE_PUBLISHABLE_KEY=<supabase-publishable-key>
+SUPABASE_DB_URL=postgresql://postgres.<project-id>:<database.password>@aws-1-eu-central-1.pooler.supabase.com:5432/postgres?prepareThreshold=0
+SUPABASE_SECRET_KEY=<supabase-secret-key>
+
+# Flyway configuration
+FLYWAY_URL=jdbc:postgresql://aws-1-eu-central-1.pooler.supabase.com:6543/postgres?prepareThreshold=0
+FLYWAY_USER=postgres.<project-id>
+FLYWAY_PASSWORD=<database.password>

package/templates/backend/BACKEND_AUTH_SETUP.md

@@ -0,0 +1,183 @@
+# Backend JWT Authentication Setup - Summary
+
+## What Was Done
+
+Your Express.js backend has been configured to use **JWT token authentication** instead of cookie-based sessions.
+
+### Changes Made
+
+#### 1. **Removed Cookie-Based Auth**
+
+- Removed `cookie-parser` from server.ts
+- Removed OAuth callback route (`/api/auth/confirm`)
+- Removed old cookie-based Supabase client setup
+
+#### 2. **Added JWT Token Verification**
+
+- **`src/supabase/api.ts`**: Stateless Supabase client for JWT verification
+- **`src/supabase/requireUser.ts`**: Extracts and verifies JWT from `Authorization` header
+- **`src/supabase/authMiddleware.ts`**: Express middleware for protecting routes
+- **`src/supabase/component.ts`**: Browser client for test login page
+
+#### 3. **Updated API Endpoints**
+
+- **`GET /api/user`**: Now requires `Authorization: Bearer <token>` header
+- Returns user info: `userId`, `email`, `metadata`
+
+#### 4. **Frontend Cleanup**
+
+- **Removed**: `register.tsx`, `reset-password.tsx`
+- **Updated**: `login.tsx` → Simple test page that displays JWT token
+- Access at: http://localhost:3000/auth/login
+
+---
+
+## How to Use
+
+### 1. Get a JWT Token
+
+**Option A: Use Test Login Page**
+
+1. Start server: `npm run dev`
+2. Visit: http://localhost:3000/auth/login
+3. Create account or login
+4. Copy the JWT token displayed
+
+**Option B: Get Token from Client**
+
+```javascript
+const { data } = await supabase.auth.signInWithPassword({ email, password })
+const token = data.session.access_token
+```
+
+### 2. Make Authenticated Requests
+
+**Using cURL:**
+
+```bash
+curl -H "Authorization: Bearer YOUR_JWT_TOKEN" \
+     http://localhost:3000/api/user
+```
+
+**Using JavaScript fetch:**
+
+```javascript
+fetch('/api/user', {
+    headers: {
+        'Authorization': `Bearer ${token}`
+    }
+})
+    .then(res => res.json())
+    .then(data => console.log(data))
+```
+
+### 3. Protect Your Routes
+
+**Method 1: Using authMiddleware**
+
+```typescript
+import {authMiddleware} from './src/supabase/authMiddleware'
+
+app.get('/api/protected', authMiddleware, (req, res) => {
+    const user = (req as any).user
+    res.json({user})
+})
+```
+
+**Method 2: Using requireUser function**
+
+```typescript
+import {requireUser} from './src/supabase/requireUser'
+
+app.get('/api/protected', async (req, res) => {
+    const result = await requireUser(req, res, false)
+
+    if (result.error) {
+        return res.status(401).json({error: result.error})
+    }
+
+    const user = result.user
+    res.json({user})
+})
+```
+
+---
+
+## File Structure
+
+```
+src/supabase/
+├── api.ts              # Supabase client creation
+├── requireUser.ts      # JWT verification function
+├── authMiddleware.ts   # Express middleware
+├── component.ts        # Browser client (for test page)
+├── supabaseClient.ts   # Environment constants
+└── README.md           # Complete documentation
+
+src/pages/auth/
+└── login.tsx           # Test login page with JWT display
+```
+
+---
+
+## Environment Variables
+
+Add to `.env.local`:
+
+```env
+NEXT_PUBLIC_SUPABASE_URL=http://127.0.0.1:54321
+NEXT_PUBLIC_SUPABASE_ANON_KEY=your-anon-key-here
+```
+
+---
+
+## API Responses
+
+### Success (200)
+
+```json
+{
+    "userId": "550e8400-e29b-41d4-a716-446655440000",
+    "email": "user@example.com",
+    "metadata": {
+        "name": "John Doe"
+    }
+}
+```
+
+### Unauthorized (401)
+
+```json
+{
+    "error": "Missing authorization token"
+}
+```
+
+or
+
+```json
+{
+    "error": "Invalid or expired token"
+}
+```
+
+---
+
+## Security Notes
+
+✅ JWT tokens are verified with Supabase on every request
+✅ No session storage on backend (stateless)
+✅ Tokens expire automatically
+⚠️ Always use HTTPS in production
+⚠️ Keep environment variables secure
+
+---
+
+## Next Steps
+
+1. Add your Supabase anon key to `.env.local`
+2. Use `authMiddleware` or `requireUser` in your slice routes
+3. Remove test login page in production if not needed
+4. Consider adding role-based authorization if needed
+
+For complete documentation, see: `src/supabase/README.md`

package/templates/backend/SWAGGER.md

@@ -0,0 +1,213 @@
+# Swagger UI & OpenAPI Documentation
+
+## Overview
+
+This project includes Swagger UI for interactive API documentation and OpenAPI specification generation.
+
+## Quick Start
+
+1. Start the development server:
+
+```bash
+npm run dev
+```
+
+2. Open Swagger UI in your browser:
+
+```
+http://localhost:3000/api-docs
+```
+
+3. View the OpenAPI JSON specification:
+
+```
+http://localhost:3000/swagger.json
+```
+
+## Documentation
+
+The API documentation is automatically generated from JSDoc comments in your route files using `swagger-jsdoc`.
+
+### Adding Documentation to Routes
+
+Add JSDoc comments above your route handlers with OpenAPI/Swagger syntax:
+
+```typescript
+/**
+ * @swagger
+ * /api/query/shifts-collection:
+ *   get:
+ *     summary: Get shifts collection
+ *     description: Retrieve all shifts or a specific shift by ID
+ *     tags:
+ *       - Shifts
+ *     parameters:
+ *       - in: query
+ *         name: _id
+ *         schema:
+ *           type: string
+ *         description: Optional shift ID to fetch a specific shift
+ *     responses:
+ *       200:
+ *         description: Successfully retrieved shifts
+ *         content:
+ *           application/json:
+ *             schema:
+ *               type: array
+ *               items:
+ *                 type: object
+ *       500:
+ *         description: Server error
+ */
+router.get('/api/query/shifts-collection', async (req, res) => {
+    // route implementation
+});
+```
+
+### Common Swagger Components
+
+#### Authentication (Bearer Token)
+
+```typescript
+/**
+ * @swagger
+ * /api/protected-route:
+ *   get:
+ *     summary: Protected endpoint
+ *     security:
+ *       - bearerAuth: []
+ *     responses:
+ *       200:
+ *         description: Success
+ *       401:
+ *         description: Unauthorized
+ */
+router.get('/api/protected-route', (req, res) => {
+    // implementation
+});
+```
+
+#### POST Request with Body
+
+```typescript
+/**
+ * @swagger
+ * /api/shifts:
+ *   post:
+ *     summary: Create a new shift
+ *     tags:
+ *       - Shifts
+ *     requestBody:
+ *       required: true
+ *       content:
+ *         application/json:
+ *           schema:
+ *             type: object
+ *             properties:
+ *               name:
+ *                 type: string
+ *               start_time:
+ *                 type: string
+ *                 format: date-time
+ *               end_time:
+ *                 type: string
+ *                 format: date-time
+ *     responses:
+ *       201:
+ *         description: Shift created successfully
+ *       400:
+ *         description: Bad request
+ */
+router.post('/api/shifts', (req, res) => {
+    // implementation
+});
+```
+
+#### Path Parameters
+
+```typescript
+/**
+ * @swagger
+ * /api/shifts/{id}:
+ *   get:
+ *     summary: Get a specific shift
+ *     parameters:
+ *       - in: path
+ *         name: id
+ *         required: true
+ *         schema:
+ *           type: string
+ *         description: Shift ID
+ *     responses:
+ *       200:
+ *         description: Shift found
+ *       404:
+ *         description: Shift not found
+ */
+router.get('/api/shifts/:id', (req, res) => {
+    // implementation
+});
+```
+
+## File Locations
+
+- **Swagger Configuration**: `src/swagger.ts`
+- **Server Integration**: `server.ts` (lines 81-97)
+- **Route Documentation**: Add to any route file in `src/slices/*/routes.ts`
+
+## Configuration
+
+The Swagger configuration is in `src/swagger.ts`:
+
+```typescript
+const options = {
+    definition: {
+        openapi: '3.0.0',
+        info: {
+            title: 'Context API',
+            version: '1.0.0',
+            description: 'Event-driven API...',
+        },
+        servers: [
+            {
+                url: 'http://localhost:3000',
+                description: 'Development server',
+            },
+        ],
+    },
+    apis: ['./src/slices/**/routes.ts'], // Auto-discovers routes
+};
+```
+
+## Testing Your API
+
+1. **In Swagger UI**: Click "Try it out" button to test endpoints
+2. **With cURL**:
+
+```bash
+curl http://localhost:3000/api/query/shifts-collection
+```
+
+3. **With Postman**: Import the OpenAPI spec from `/swagger.json`
+
+## OpenAPI Spec Export
+
+Download the full OpenAPI specification:
+
+```bash
+curl http://localhost:3000/swagger.json > openapi.json
+```
+
+Use it with:
+
+- [Swagger Editor](https://editor.swagger.io/)
+- [OpenAPI Tools](https://openapi.tools/)
+- [Postman](https://www.postman.com/)
+- [ReDoc](https://redoc.ly/)
+
+## Resources
+
+- [Swagger/OpenAPI Documentation](https://swagger.io/specification/)
+- [swagger-jsdoc](https://github.com/Surnet/swagger-jsdoc)
+- [swagger-ui-express](https://github.com/scottie1984/swagger-ui-express)
+- [OpenAPI 3.0 Specification](https://spec.openapis.org/oas/v3.0.3)

package/templates/backend/eslint.config.mjs

@@ -0,0 +1,31 @@
+import {dirname} from "path";
+import {fileURLToPath} from "url";
+import {FlatCompat} from "@eslint/eslintrc";
+
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+
+const compat = new FlatCompat({
+    baseDirectory: __dirname,
+});
+
+const eslintConfig = [
+    ...compat.extends("next/core-web-vitals", "next/typescript"),
+    {
+        rules: {
+            "no-unused-vars": "off", // Disable unused variable warnings
+            "@typescript-eslint/no-unused-vars": "off", // Also disable the TypeScript-specific version
+            "@typescript-eslint/no-restricted-types": [
+                "error",
+                {
+                    "extendDefaults": true,
+                    "types": {
+                        "{}": false
+                    }
+                }
+            ]
+        },
+    },
+];
+
+export default eslintConfig;

package/templates/backend/flyway.conf

@@ -0,0 +1,17 @@
+# Flyway configuration file
+# Database connection from .env file
+flyway.url=${FLYWAY_URL}
+flyway.user=${FLYWAY_USER}
+flyway.password=${FLYWAY_PASSWORD}
+
+# Migration files location
+flyway.locations=filesystem:./supabase/migrations
+
+# Default schema (Flyway will create flyway_schema_history table here)
+flyway.schemas=public
+
+# Placeholder replacement
+flyway.placeholderReplacement=false
+
+# Validate on migrate
+flyway.validateOnMigrate=true

package/templates/backend/package.json

@@ -0,0 +1,44 @@
+{
+  "name": "project",
+  "version": "0.1.0",
+  "private": true,
+  "scripts": {
+    "flyway:migrate": "dotenv flyway migrate",
+    "dev": "node --env-file=.env --require ts-node/register server.ts",
+    "build": "tsc",
+    "start": "NODE_ENV=production node --env-file=.env --require ts-node/register server.ts",
+    "test": "tsx --test 'src/**/*.test.ts'"
+  },
+  "dependencies": {
+    "@event-driven-io/emmett": "^0.41.0",
+    "@event-driven-io/emmett-expressjs": "^0.41.0",
+    "@event-driven-io/emmett-postgresql": "^0.41.0",
+    "@supabase/ssr": "^0.6.1",
+    "@supabase/supabase-js": "^2.50.0",
+    "cookie-parser": "^1.4.7",
+    "cors": "^2.8.6",
+    "express": "^4.18.2",
+    "glob": "^11.0.3",
+    "knex": "^3.1.0",
+    "node-cron": "^4.2.1",
+    "pg": "^8.17.2",
+    "swagger-jsdoc": "^6.2.8",
+    "swagger-ui-express": "^5.0.1",
+    "url": "^0.11.4"
+  },
+  "devDependencies": {
+    "@eslint/eslintrc": "^3",
+    "@testcontainers/postgresql": "^11.0.3",
+    "@types/cors": "^2.8.19",
+    "@types/express": "^4.17.21",
+    "@types/node": "^20",
+    "@types/swagger-jsdoc": "^6.0.4",
+    "@types/swagger-ui-express": "^4.1.8",
+    "dotenv-cli": "^11.0.0",
+    "eslint": "^9",
+    "sql-formatter": "^15.7.0",
+    "ts-node": "^10.9.2",
+    "tsx": "^4.20.3",
+    "typescript": "^5"
+  }
+}