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…
Turn on App Check for the app and put a budget alert on the production project.
$ npx -y skills add receptron/mulmoterminal --skill protect --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/protectContext preview
The summary Claude sees to decide when to auto-load this skill.
Turn on App Check for the app and put a budget alert on the production project.
name: blueprint-firebase-protect description: "Turn on App Check for the app and put a budget alert on the production project."
1. App Check with reCAPTCHA Enterprise for the web app. Register the site key in both projects; call `initializeAppCheck` in the app. Every callable function is declared `onCall({ enforceAppCheck: true }, …)`. Turn on enforcement for Firestore and Functions in the console — give the user the URL and wait for them. 2. Budget alert (the **billing** gate, already approved): `gcloud billing budgets create` on the production project's billing account at the amount in the spec, alerting at 50%, 90% and 100%, with `--filter-projects=projects/<prod-project-id>` so it watches this project and not the whole account.
Done when the check passes: App Check is ENFORCED for Firestore on production, every callable enforces it, and a budget is scoped to the production project.
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.