cf-saas-stack

Maintains the living high-level architecture document with route maps, feature flows, and changelog

Generates Drizzle ORM migrations for schema changes with proper naming conventions

Scaffolds and maintains a structured docs/ directory with architecture context files and templates

Audits the codebase for DRY violations and enforces folder structure conventions

Executes feature implementations by delegating to specialized tasks based on requirements

Maintains high-level architecture documentation with visual diagrams and feature flows. Use proactively after implementing features, adding routes, or making architectural changes to keep the living architecture document current. Examples - 'update the architecture docs after adding the new recipe sharing route', 'refresh the route map and changelog after schema changes', 'add the meal planning feature flow to the architecture doc'.

Documentation specialist that maintains project context docs. Use proactively after implementing any new feature, making architectural changes, or completing significant work. Examples - 'update context docs after adding the new recipe sharing feature', 'sync the context.md index with the latest changes', 'update the API docs after adding new tRPC routes'.

Data analytics specialist for creating growth dashboards and insights. Use proactively when creating new database schemas, features, or when asked to add analytics, metrics, or reporting. Analyzes data models and implements time-series charts, KPI cards, and growth visualizations. Examples - 'add analytics for the new recipe extraction feature', 'create a dashboard section for meal plan usage metrics', 'implement growth charts for user signups'.

Logging specialist for adding structured debug logs. Use proactively when implementing features, debugging issues, or when trace logging would help understand code flow. Adds meaningful logs instead of AI-generated comments. Examples - 'add structured logging to the recipe extraction workflow', 'add debug logs to the authentication flow', 'instrument the meal plan creation with trace logging'.

Testing workflow specialist for verifying implementations. Use proactively after implementing any plan or feature to generate testing plans, verify functionality, fix issues, write e2e tests, and create test results documentation. Examples - 'test the recipe extraction feature end to end', 'create a testing plan for the new meal planning flow', 'write Playwright e2e tests for the authentication flow', 'verify the comment thread feature works correctly'.

Better Auth authentication patterns and conventions for this Cloudflare Workers project

Cloudflare Workflows patterns for background tasks and async processing

Context-based client pattern for passing external service clients through request context

Documentation hierarchy and maintenance rules for context docs and architecture files

Drizzle ORM database schema patterns and conventions for SQLite/D1