apply
Set chaff up in the folder: chaff.yaml for the chosen genre, today's findings shelved in .chaff-baseline.json, and, when asked, a…
Create or choose the dev and production Firebase projects and put them on the Blaze plan.
$ npx -y skills add receptron/mulmoterminal --skill projects --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/projectsContext preview
The summary Claude sees to decide when to auto-load this skill.
Create or choose the dev and production Firebase projects and put them on the Blaze plan.
name: blueprint-firebase-projects description: "Create or choose the dev and production Firebase projects and put them on the Blaze plan."
Read `.blueprint/spec.md` for `existingProject`, `existingProjectId` and `region`.
1. Two projects: dev and production. If the user named an existing one, use it for production and create only dev. Project ids are global — propose `<app>-dev` / `<app>-prod` and ask if they are taken. 2. `firebase projects:create <id>` for each new one, then write `.firebaserc` with aliases `dev` and `prod` (`firebase use --add`). 3. **Billing is the gate for this step** and the executor has already had it approved. Linking a billing account (Blaze) is done by the user in the console: give them the exact URL `https://console.firebase.google.com/project/<id>/usage/details` and wait for them to confirm. Do not try to link billing from the CLI on their behalf. 4. Create Firestore in `region` for BOTH projects. The region cannot be changed later — read it back from the spec, never assume a default. 5. Each project needs a registered web app — Hosting serves its config at `/__/firebase/init.json`, which the app reads. `firebase apps:list WEB --project <id>`; if none, `firebase apps:create WEB <app name> --project <id>`. 6. Google sign-in must be switched on in each project. `sh <base pack>/checks/google-signin.sh dev` (and `prod`) reads it; for each that fails, give the user the URL it printed and wait — enabling it creates an OAuth client, which only the console can do.
Done when the check passes: `.firebaserc` has distinct `dev` and `prod` projects, both exist, both have billing enabled and both have a Firestore database.
user approved exactly that.
Run multiple coding-agent sessions in parallel — and see which one needs you. A browser terminal for parallel AI coding agents: several sessions side by side, each in its own cell, with the one that needs you marked in colour.
Set chaff up in the folder: chaff.yaml for the chosen genre, today's findings shelved in .chaff-baseline.json, and, when asked, a…
Measure what chaff reports on the named documents today, as the kind the person chose, and propose the setup — changing nothing…
Answer each question from the named documents only, quoting where the answer is written, or saying plainly that the documents do…
Add the approved answers to FAQ.md when the person chose to keep them, after what it already holds; change nothing otherwise.
Build the spec's operations as the Worker's API, with validation and tests.