run-and-operate

Coordinate operational tasks for the Cambridge Beer Festival Flutter app.

2|3|Updated Nov 28, 2025
One-click install
npx skills add https://github.com/richardthe3rd/cambridge-beer-festival-app --skill run-and-operate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-and-operate
Source: https://github.com/richardthe3rd/cambridge-beer-festival-app/tree/main/.claude/skills/run-and-operate
Command: npx skills add https://github.com/richardthe3rd/cambridge-beer-festival-app --skill run-and-operate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of working with the Cambridge Beer Festival app's custom operational setup, which relies on specialized mise tasks, GitHub Actions CI/CD workflows, and Cloudflare deployment infrastructure that are not immediately obvious from the codebase alone. Without this guidance, developers would need to manually piece together commands, workflow triggers, and deployment topology from scattered documentation and configuration files.

Core Features & Use Cases

  • Local development and testing workflows: Provides exact, environment-aware commands for running the local dev server, building web and Android artifacts, serving release builds locally, and executing end-to-end Playwright test suites, including nuances for Claude Code Web environments.
  • Release and deployment orchestration: Covers the full CalVer release train process, deployment topology for staging, PR preview, and production environments, Android Play Store releases, and Cloudflare Worker deploys, plus documented traps and edge cases like CI not running on release PRs.
  • Operational checks and data management: Includes commands to verify worker health, update the festival data registry, and understand where build artifacts and logs are stored, with clear boundaries on what operational checks an agent can perform independently versus what requires human dashboard access. Use case example: If you need to test a bug fix locally, this Skill gives you the correct command to start the dev server for your environment; if you need to cut a production release, it walks you through the full release train process and warns you about common pitfalls like the festival freeze rule.

Quick Start

Use the run-and-operate skill to start the local development server for the Cambridge Beer Festival app and access it at http://localhost:8080 to verify your changes.

Frequently Asked Questions about run-and-operate

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

FAQPage Schema
How do I start the local development server for a Flutter app and run E2E Playwright tests?

To run the local dev server and execute E2E Playwright test suites for a Flutter app, use environment-aware commands tailored to your setup, such as accessing the local server at http://localhost:8080 to verify changes. It handles nuances for Claude Code Web environments automatically.

How do I build web and Android release artifacts for a Flutter application?

Building web and Android release artifacts involves using specialized mise tasks to compile platform-specific outputs. The process provides exact commands for generating builds and serving release builds locally to verify functionality before deployment.

What is the best way to cut a CalVer release and deploy to Cloudflare Workers?

Cutting a CalVer release and deploying to Cloudflare Workers follows a release train runbook that manages staging, PR preview, and production environments. It documents common traps like CI not running on release PRs and Android Play Store release steps.

Can I provision a Cloudflare D1 database and update festival data registries without manual dashboard access?

You can provision Cloudflare D1 databases and update festival data registries using automated commands, but certain operational checks require human dashboard access. The Skill clearly defines boundaries for what an agent can perform independently versus what needs manual intervention.

Why does CI not run on release PRs when managing Flutter deployment workflows?

CI does not run on release PRs due to specific GitHub Actions workflow configurations within the deployment topology. The release management process documents this edge case and warns about common pitfalls like the festival freeze rule during production cuts.

How do I verify Cloudflare Worker health endpoints after a production deployment?

Verifying deployment health endpoints after a production deploy involves running specific operational checks against the Cloudflare Worker. It provides commands to verify worker health and locate where build artifacts and logs are stored for auditing.