Skip to content
Agent Orchestration
Skill

/projects

Create or choose the dev and production Firebase projects and put them on the Blaze plan.

BOOST
From plugin
mulmoterminal
24574 skills
Install
$ npx -y skills add receptron/mulmoterminal --skill projects --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/projects

Context 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.

SKILL.md

projects.SKILL.md
name: blueprint-firebase-projects
description: "Create or choose the dev and production Firebase projects and put them on the Blaze plan."

Dev and production projects

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.

Always

  • Read `.blueprint/spec.md` first. It is the agreed specification; do not widen it.
  • When you need a decision, ask it through the blueprint question tool and stop. Do not guess.
  • Never enable billing, deploy to production, delete data or handle a credential unless this step's gates say the

user approved exactly that.

  • Say you are done by stopping; the executor runs the check. Do not claim success yourself.
Read more
Ships withmulmoterminal

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.

Get the whole plugin
Stats
255
Stars
32
Forks
Active
Maintenance
TypeScript
Language
MIT
License
4h ago
Last commit
4mo ago
Created
18h ago
Added

Repo: receptron/mulmoterminal

Other skills on mulmoterminal.