lanesawyer

Scaffold a web repo with pnpm, Astro, and astro-bulma — plus Drizzle when the site needs a database — including package.json scripts for build/lint/test/fmt (and db:migrate when db-backed). Use when: setting up a new Astro project, scaffolding a web repo, initializing the standard web stack. Building block for create-website.

Add a GitHub Actions CI workflow running build, lint, test, and fmt checks with pnpm. Use when: adding CI, setting up GitHub Actions checks, adding a build/lint/test workflow. Building block for create-website.

Create a new website end-to-end: Astro repo with pnpm/astro-bulma; GitHub Pages for static sites, or Turso + Fly.io when the site needs a database; GitHub Actions for CI and deploy. Use when: creating a new website, spinning up a new web project, new site, scaffolding a static or full-stack Astro project.

Create a new app on Fly.io for the current project without deploying it, generating fly.toml and a Dockerfile. Use when: creating a Fly.io app, setting up Fly hosting, fly launch. Building block for create-website.

Add a GitHub Actions workflow that builds a static site and deploys it to GitHub Pages, with an optional custom domain. Use when: deploying a static site, GitHub Pages hosting, static site with a custom domain. Building block for create-website.

Add a GitHub Actions workflow that deploys to Fly.io on merge to main, with db migrations run as a Fly release_command. Use when: adding a deploy workflow, deploying on merge, setting up continuous deployment to Fly.io. Building block for create-website.

Add a GitHub Actions workflow that spins up a temporary Fly.io preview app per pull request, backed by a fork of the production Turso database, and destroys both on close. Use when: adding PR previews, review apps, per-PR deploy environments.

Create a new database on Turso, asking whether it goes in a new or existing database group, and wire credentials into .env. Use when: creating a Turso database, setting up libSQL storage, new turso db. Building block for create-website.

Use when implementing any new feature in dicebag. Enforces the full implementation checklist: core Rust logic first, then WASM bindings, CLI command, webapp action, UI, and TypeScript interface sync. Invoke whenever the user asks to add, build, or implement something new.

Use when reviewing webapp actions for logic that belongs in Rust core instead of TypeScript. Invoke before opening a PR, when asked to review the webapp actions, or when you notice potential business logic in TypeScript while working.

Use when verifying that CLI commands and webapp actions are in sync. Invoke before opening a PR, when adding a new feature, or when asked to check parity between the CLI and webapp.

Scaffolds a full-stack feature for tutti-belli — lib functions, actions, and an optional page — following the project's established patterns

Writes and runs tests for a tutti-belli feature — integration tests for lib functions and an e2e test for the happy-path form flow

Verify astro-bulma component changes by driving them in a real browser — docs site for MPA behavior, a throwaway fixture app for ClientRouter behavior.

Add a new component to astro-bulma or update an existing one — Bulma wrappers and larger composite components alike. Use when creating, extending, or refactoring an astro-bulma component.