local-e2e

Runs end-to-end tests against a local Supabase, Workers, and frontend stack via the Claude CLI.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/aitit-inc/leadace --skill local-e2e-aitit-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-e2e
Source: https://github.com/aitit-inc/leadace/tree/main/.claude/skills/local-e2e
Command: npx skills add https://github.com/aitit-inc/leadace --skill local-e2e-aitit-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Testing an OAuth-driven, multi-service product locally is error-prone: you need Supabase, API and MCP Workers, and a frontend all running, real Google OAuth flows, and an isolated Claude CLI state. This Skill encodes the prerequisites, run procedure, and cleanup so E2E scenarios execute safely against the local stack without touching production. ## Core Features & Use Cases - Pre-flight validation: ./e2e/preflight.sh checks all five services (Supabase Auth, Postgres, API Worker, MCP Worker, Frontend) and reports failures. - Headless smoke test: ./e2e/smoke.sh drives the full /leadace onboarding chain through the Claude CLI with an isolated CLAUDE_CONFIG_DIR, then auto-cleans the created project. - Arbitrary scenario runs and DB inspection: ./e2e/run.sh "<prompt>" executes custom prompts, while local Postgres (localhost:54322) and Supabase Studio allow direct inspection and reset. - Use Case: After modifying the MCP Worker, run ./e2e/smoke.sh to verify the onboarding chain end-to-end against localhost, then inspect outreach_logs in the local database to confirm behavior. ## Quick Start Run the local E2E smoke test against my local stack and report whether the onboarding chain succeeded.

Frequently Asked Questions about local-e2e

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run E2E tests against a local Supabase and Cloudflare Workers stack?

Start Supabase, the API Worker, MCP Worker, and frontend, then run ./e2e/preflight.sh to verify all services. Use ./e2e/smoke.sh for the standard onboarding chain or ./e2e/run.sh "<prompt>" for custom scenarios.

How do I test OAuth flows locally without mocking them?

Create a Web OAuth client in Google Cloud Console with http://localhost:54321/auth/v1/callback as a redirect URI, export the client ID and secret, and run ./e2e/setup.sh. The skill runs real Google, Supabase Auth, and MCP OAuth flows with no test-only backdoors.

Why does the MCP OAuth grant stop working after restarting wrangler dev?

The local MCP Worker stores refresh tokens in an in-memory KV, which is lost on restart. Re-run ./e2e/setup.sh; only the /leadace overview MCP OAuth step needs to be redone since /login is a no-op.

Can I trigger Cloudflare cron scheduled handlers locally?

Yes. The API Worker starts with --test-scheduled, exposing a /__scheduled endpoint. Run ./e2e/trigger-cron.sh or curl 'http://localhost:8787/__scheduled?cron=0+3+*+*+*' to fire the scheduled handler on demand.

What are the limitations of this local E2E harness?

The daily-cycle full run and reaction detection automation are not yet implemented. The harness never touches production, requires a host Claude CLI with a subscription, and the reported cost is an API-equivalent reference rather than a real charge.