gsd-trae 1.0.1 → 1.0.2

package/refs/vbenchmark/tasks/saas-core/billing/usage-metering/task.yaml

@@ -1,27 +0,0 @@
-name: Usage-Based Metering System
-category: saas-core
-subcategory: billing
-description: Implement API usage tracking and metered billing with Go
-difficulty: hard
-stack: go
-timeout: 900
-tokenLimit: 200000
-
-tests:
-  functional: tests/metering_test.go
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - go
-  - metering
-  - billing
-  - api
-  - usage-tracking
-
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/crud/dashboard-table/PROMPT.md

@@ -1,48 +0,0 @@
-# Data Table Dashboard
-
-Build a full-featured data table component with the following requirements:
-
-## Features
-
-1. **Sortable columns** - Click column header to sort ascending/descending
-2. **Search/filter** - Global search and per-column filters
-3. **Pagination** - Show 10/25/50/100 items per page with navigation
-4. **Bulk actions** - Select multiple rows, delete/export selected
-5. **Responsive** - Works on mobile with horizontal scroll
-
-## Data Schema
-
-```typescript
-interface User {
-  id: string;
-  name: string;
-  email: string;
-  role: 'admin' | 'user' | 'guest';
-  status: 'active' | 'inactive' | 'pending';
-  createdAt: string;
-  lastLogin: string;
-}
-```
-
-## API Endpoints
-
-- `GET /api/users?page=1&limit=10&sort=name&order=asc&search=john`
-- `DELETE /api/users` with body `{ ids: string[] }`
-- `GET /api/users/export?ids=1,2,3` returns CSV
-
-## Requirements
-
-1. Use React with TypeScript
-2. Use Tailwind CSS for styling
-3. Handle loading states and errors
-4. Debounce search input (300ms)
-5. Persist page size preference in localStorage
-
-## Acceptance Criteria
-
-- [ ] Table displays data from API
-- [ ] All columns are sortable
-- [ ] Search filters results in real-time
-- [ ] Pagination works correctly
-- [ ] Can select and delete multiple rows
-- [ ] Mobile responsive

package/refs/vbenchmark/tasks/saas-core/crud/dashboard-table/task.yaml

@@ -1,28 +0,0 @@
-name: Data Table Dashboard
-category: saas-core
-subcategory: crud
-description: Build a sortable, filterable data table with pagination, search, and bulk actions
-difficulty: medium
-stack: nextjs
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/table.test.ts
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - crud
-  - datatable
-  - pagination
-  - filtering
-  - sorting
-
-evaluation:
-  functional: 0.4
-  visual: 0.2
-  quality: 0.2
-  cost: 0.1
-  speed: 0.1

package/refs/vbenchmark/tasks/saas-core/multi-tenant/org-isolation/PROMPT.md

@@ -1,50 +0,0 @@
-# Task: Multi-Tenant Organization Isolation
-
-## Objective
-Implement database-per-tenant isolation with dynamic connection routing for a multi-tenant SaaS application.
-
-## Requirements
-
-1. **Tenant Database Management**
-   - Create new database per organization on signup
-   - Run migrations automatically on new tenant DBs
-   - Connection pooling per tenant
-   - Lazy connection initialization
-
-2. **Request Routing**
-   - Extract tenant from JWT or subdomain
-   - Route to correct tenant database
-   - Middleware to inject tenant context
-   - Prevent cross-tenant data access
-
-3. **Tenant Lifecycle**
-   - `POST /tenants` - Provision new tenant
-   - `DELETE /tenants/{id}` - Deprovision (soft delete + archive)
-   - `POST /tenants/{id}/export` - Export all tenant data
-   - `POST /tenants/{id}/migrate` - Run pending migrations
-
-4. **Connection Management**
-   - Connection pool per tenant
-   - Idle connection timeout
-   - Max connections per tenant limit
-   - Health check per tenant DB
-
-## Technical Stack
-- TypeScript/Node.js
-- Express or Fastify
-- PostgreSQL (one DB per tenant)
-- Prisma with dynamic datasource
-
-## Files to Create
-- `src/middleware/tenant.ts` - Tenant resolution
-- `src/services/tenant-manager.ts` - Tenant provisioning
-- `src/db/connection-pool.ts` - Dynamic connections
-- `src/db/migrations.ts` - Migration runner
-- `src/routes/tenants.ts` - Admin endpoints
-
-## Success Criteria
-- [ ] New tenant DB created on signup
-- [ ] Requests route to correct tenant DB
-- [ ] Cross-tenant access is impossible
-- [ ] Connection pools are properly managed
-- [ ] Migrations run on all tenant DBs

package/refs/vbenchmark/tasks/saas-core/multi-tenant/org-isolation/task.yaml

@@ -1,27 +0,0 @@
-name: Multi-Tenant Organization Isolation
-category: saas-core
-subcategory: multi-tenant
-description: Implement database-per-tenant isolation with dynamic connection routing
-difficulty: hard
-stack: nodejs
-timeout: 900
-tokenLimit: 200000
-
-tests:
-  functional: tests/isolation.test.ts
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - typescript
-  - multi-tenancy
-  - database
-  - isolation
-  - saas
-
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/multi-tenant/subdomain-routing/PROMPT.md

@@ -1,50 +0,0 @@
-# Task: Subdomain-Based Tenant Routing
-
-## Objective
-Implement subdomain-based tenant routing that maps subdomains to tenant contexts in a Go application.
-
-## Requirements
-
-1. **Subdomain Parsing**
-   - Extract tenant slug from subdomain (acme.app.com → acme)
-   - Support custom domains (acme.com → acme tenant)
-   - Handle apex domain (app.com → public/landing)
-   - Validate tenant exists and is active
-
-2. **Custom Domain Mapping**
-   - Store custom domain → tenant mappings
-   - SSL certificate management hints
-   - Domain verification (DNS TXT record)
-   - `POST /tenants/{id}/domains` - Add custom domain
-   - `DELETE /tenants/{id}/domains/{domain}` - Remove domain
-
-3. **Middleware**
-   - Inject tenant context into request
-   - 404 for unknown subdomains
-   - Redirect inactive tenants to suspended page
-   - Cache tenant lookups
-
-4. **URL Generation**
-   - Generate tenant-specific URLs
-   - Support both subdomain and custom domain
-   - Email links point to correct tenant URL
-
-## Technical Stack
-- Go 1.21+
-- Chi or Gin router
-- PostgreSQL
-- Redis for caching
-
-## Files to Create
-- `internal/middleware/tenant.go` - Tenant middleware
-- `internal/services/domain.go` - Domain management
-- `internal/services/tenant.go` - Tenant service
-- `internal/handlers/domains.go` - Domain endpoints
-- `internal/cache/tenant.go` - Tenant cache
-
-## Success Criteria
-- [ ] Subdomain correctly maps to tenant
-- [ ] Custom domains work with verification
-- [ ] Unknown subdomains return 404
-- [ ] Tenant context available in handlers
-- [ ] Domain lookups are cached

package/refs/vbenchmark/tasks/saas-core/multi-tenant/subdomain-routing/task.yaml

@@ -1,27 +0,0 @@
-name: Subdomain-Based Tenant Routing
-category: saas-core
-subcategory: multi-tenant
-description: Implement subdomain routing for multi-tenant applications in Go
-difficulty: medium
-stack: go
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/routing_test.go
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - go
-  - multi-tenancy
-  - routing
-  - subdomains
-  - middleware
-
-evaluation:
-  functional: 0.5
-  quality: 0.2
-  cost: 0.15
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/notifications/email-queue/PROMPT.md

@@ -1,53 +0,0 @@
-# Task: Async Email Notification Queue
-
-## Objective
-Build an asynchronous email notification system using Celery that handles templated emails with retry logic and delivery tracking.
-
-## Requirements
-
-1. **Email Templates**
-   - Welcome email
-   - Password reset
-   - Invoice notification
-   - Weekly digest
-   - Store templates in database or filesystem
-
-2. **Queue Processing**
-   - Async task execution with Celery
-   - Priority queues (transactional > marketing)
-   - Retry with exponential backoff
-   - Dead letter queue for failed emails
-
-3. **Delivery Tracking**
-   - Log all email sends
-   - Track delivery status via webhooks
-   - Handle bounces and complaints
-   - Unsubscribe management
-
-4. **API Endpoints**
-   - `POST /notifications/email` - Queue email
-   - `GET /notifications/email/{id}` - Get delivery status
-   - `POST /notifications/email/batch` - Queue batch emails
-   - `GET /notifications/logs` - Email logs
-
-## Technical Stack
-- Python 3.11+
-- FastAPI
-- Celery with Redis broker
-- Resend or SendGrid
-- PostgreSQL
-
-## Files to Create
-- `app/tasks/email.py` - Celery email tasks
-- `app/services/email_sender.py` - Email sending logic
-- `app/services/template_renderer.py` - Template rendering
-- `app/routers/notifications.py` - API endpoints
-- `app/models/email_log.py` - Email log model
-- `app/templates/emails/` - Email templates
-
-## Success Criteria
-- [ ] Emails queued and sent asynchronously
-- [ ] Failed emails retry with backoff
-- [ ] Delivery status tracked
-- [ ] Batch sending works efficiently
-- [ ] Unsubscribe links work

package/refs/vbenchmark/tasks/saas-core/notifications/email-queue/task.yaml

@@ -1,27 +0,0 @@
-name: Async Email Notification Queue
-category: saas-core
-subcategory: notifications
-description: Implement async email notification system with queue processing in Python
-difficulty: medium
-stack: python
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/test_email_queue.py
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - python
-  - celery
-  - email
-  - queue
-  - notifications
-
-evaluation:
-  functional: 0.5
-  quality: 0.2
-  cost: 0.15
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/notifications/in-app-alerts/PROMPT.md

@@ -1,51 +0,0 @@
-# Task: Real-time In-App Notifications
-
-## Objective
-Build a real-time in-app notification system using WebSockets with Spring Boot.
-
-## Requirements
-
-1. **Notification Types**
-   - System announcements
-   - User mentions
-   - Task assignments
-   - Comment replies
-   - Each type has icon, color, priority
-
-2. **Real-time Delivery**
-   - WebSocket connection per user
-   - Deliver notifications instantly
-   - Queue for offline users
-   - Deliver queued on reconnect
-
-3. **Notification Center**
-   - `GET /notifications` - List notifications (paginated)
-   - `PUT /notifications/{id}/read` - Mark as read
-   - `PUT /notifications/read-all` - Mark all read
-   - `GET /notifications/unread-count` - Unread count
-
-4. **Preferences**
-   - Per-type enable/disable
-   - Quiet hours
-   - Channel preferences (in-app, email, push)
-
-## Technical Stack
-- Java 17+
-- Spring Boot 3.x
-- Spring WebSocket (STOMP)
-- PostgreSQL
-- Redis for pub/sub
-
-## Files to Create
-- `src/main/java/config/WebSocketConfig.java`
-- `src/main/java/services/NotificationService.java`
-- `src/main/java/controllers/NotificationController.java`
-- `src/main/java/models/Notification.java`
-- `src/main/java/websocket/NotificationHandler.java`
-
-## Success Criteria
-- [ ] Notifications delivered in real-time via WebSocket
-- [ ] Offline notifications queued and delivered
-- [ ] Read/unread status tracked
-- [ ] Unread count updates in real-time
-- [ ] User preferences respected

package/refs/vbenchmark/tasks/saas-core/notifications/in-app-alerts/task.yaml

@@ -1,27 +0,0 @@
-name: Real-time In-App Notifications
-category: saas-core
-subcategory: notifications
-description: Build real-time in-app notification system with Java Spring
-difficulty: medium
-stack: java
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/NotificationTest.java
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - java
-  - spring-boot
-  - websocket
-  - notifications
-  - real-time
-
-evaluation:
-  functional: 0.5
-  quality: 0.2
-  cost: 0.15
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/notifications/push-notifications/PROMPT.md

@@ -1,51 +0,0 @@
-# Task: Web Push Notifications
-
-## Objective
-Implement web push notifications using the Web Push API with service worker support.
-
-## Requirements
-
-1. **Subscription Management**
-   - Prompt user for notification permission
-   - Generate VAPID keys for push service
-   - Store push subscriptions in database
-   - Handle subscription changes/revocations
-
-2. **Service Worker**
-   - Register service worker for push events
-   - Handle push event and show notification
-   - Handle notification click (open URL)
-   - Background sync for offline queuing
-
-3. **Sending Notifications**
-   - `POST /push/subscribe` - Save subscription
-   - `DELETE /push/subscribe` - Remove subscription
-   - `POST /push/send` - Send to specific user
-   - `POST /push/broadcast` - Send to all subscribers
-
-4. **Notification Types**
-   - Simple text notification
-   - With image/icon
-   - With action buttons
-   - Silent push (data only)
-
-## Technical Stack
-- TypeScript/Node.js
-- Express
-- web-push library
-- PostgreSQL
-- Service Worker API
-
-## Files to Create
-- `src/routes/push.ts` - Push API endpoints
-- `src/services/push.ts` - Push notification logic
-- `public/sw.js` - Service worker
-- `public/push-client.js` - Client subscription
-- `src/models/subscription.ts` - Subscription model
-
-## Success Criteria
-- [ ] Users can subscribe to push
-- [ ] Notifications delivered to subscribed users
-- [ ] Service worker shows notifications
-- [ ] Click handling opens correct URL
-- [ ] Subscriptions persist across sessions

package/refs/vbenchmark/tasks/saas-core/notifications/push-notifications/task.yaml

@@ -1,27 +0,0 @@
-name: Web Push Notifications
-category: saas-core
-subcategory: notifications
-description: Implement web push notifications with service workers
-difficulty: medium
-stack: nodejs
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/push.test.ts
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - typescript
-  - web-push
-  - service-worker
-  - notifications
-  - pwa
-
-evaluation:
-  functional: 0.5
-  quality: 0.2
-  cost: 0.15
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/realtime/websocket-chat/PROMPT.md

@@ -1,80 +0,0 @@
-# Real-time WebSocket Chat
-
-Build a real-time chat application using WebSocket with the following features.
-
-## Features
-
-### Core Messaging
-- Send and receive messages in real-time
-- Message history (last 100 messages)
-- Message timestamps
-- Support multiple chat rooms
-
-### Presence System
-- Show online/offline status
-- Display list of users in room
-- Join/leave notifications
-
-### Typing Indicators
-- Show when users are typing
-- Debounced typing events (stop after 2s idle)
-- Multiple users typing support
-
-## Technical Requirements
-
-### WebSocket Server
-```typescript
-interface Message {
-  id: string;
-  roomId: string;
-  userId: string;
-  content: string;
-  timestamp: Date;
-}
-
-interface PresenceEvent {
-  type: 'join' | 'leave' | 'typing';
-  userId: string;
-  roomId: string;
-}
-```
-
-### Events
-```
-Client -> Server:
-- join_room { roomId }
-- leave_room { roomId }
-- send_message { roomId, content }
-- typing { roomId, isTyping }
-
-Server -> Client:
-- room_joined { roomId, users, history }
-- user_joined { userId }
-- user_left { userId }
-- new_message { message }
-- typing_update { roomId, users[] }
-```
-
-### API Endpoints
-```
-GET  /api/rooms          - List available rooms
-POST /api/rooms          - Create room
-GET  /api/rooms/:id/messages - Get message history
-```
-
-## Requirements
-
-1. Use `ws` or `socket.io` for WebSocket
-2. Handle reconnection gracefully
-3. Implement heartbeat/ping-pong
-4. Scale-ready (Redis pub/sub adapter optional)
-5. Rate limit messages (max 10/second per user)
-
-## Acceptance Criteria
-
-- [ ] Messages delivered in real-time
-- [ ] Presence updates work correctly
-- [ ] Typing indicators debounced
-- [ ] Reconnection restores state
-- [ ] Message history loads on join
-- [ ] Handles 100+ concurrent connections

package/refs/vbenchmark/tasks/saas-core/realtime/websocket-chat/task.yaml

@@ -1,27 +0,0 @@
-name: Real-time WebSocket Chat
-category: saas-core
-subcategory: realtime
-description: Build a real-time chat system using WebSocket with presence and typing indicators
-difficulty: hard
-stack: nodejs
-timeout: 900
-tokenLimit: 200000
-
-tests:
-  functional: tests/websocket.test.ts
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - websocket
-  - realtime
-  - chat
-  - presence
-  - nodejs
-
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/search/full-text-search/PROMPT.md

@@ -1,51 +0,0 @@
-# Task: Full-Text Search with Elasticsearch
-
-## Objective
-Implement a full-text search system using Elasticsearch that searches across users, documents, and comments.
-
-## Requirements
-
-1. **Index Management**
-   - Create indices for: users, documents, comments
-   - Define mappings with proper analyzers
-   - Handle index versioning for schema changes
-   - Reindex on mapping changes
-
-2. **Data Sync**
-   - Sync database changes to Elasticsearch
-   - Handle creates, updates, deletes
-   - Bulk indexing for initial load
-   - Near real-time sync (< 1 second)
-
-3. **Search Features**
-   - Full-text search across fields
-   - Fuzzy matching for typos
-   - Highlighting matched terms
-   - Faceted search (filter by type, date, author)
-   - Pagination with cursor
-
-4. **API Endpoints**
-   - `GET /search?q=term` - Global search
-   - `GET /search/users?q=term` - Search users
-   - `GET /search/documents?q=term` - Search docs
-   - `POST /search/reindex` - Trigger reindex
-
-## Technical Stack
-- TypeScript/Node.js
-- Express or Hono
-- Elasticsearch 8.x
-- PostgreSQL (source of truth)
-
-## Files to Create
-- `src/services/elasticsearch.ts` - ES client wrapper
-- `src/services/indexer.ts` - Data sync logic
-- `src/services/search.ts` - Search logic
-- `src/routes/search.ts` - Search endpoints
-- `src/mappings/` - Index mappings
-
-## Success Criteria
-- [ ] Search returns relevant results
-- [ ] Fuzzy matching handles typos
-- [ ] Results highlight matched terms
-- [ ] Facets filter correctly
-- [ ] DB changes sync to ES quickly

package/refs/vbenchmark/tasks/saas-core/search/full-text-search/task.yaml

@@ -1,27 +0,0 @@
-name: Full-Text Search with Elasticsearch
-category: saas-core
-subcategory: search
-description: Implement full-text search across multiple entities with Elasticsearch
-difficulty: medium
-stack: nodejs
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/search.test.ts
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - typescript
-  - elasticsearch
-  - search
-  - indexing
-  - full-text
-
-evaluation:
-  functional: 0.5
-  quality: 0.2
-  cost: 0.15
-  speed: 0.15