blueprint-firebase-deploy-production SKILL.md skillA

blueprint-firebase-deploy-production from receptron/mulmoterminal is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add receptron/mulmoterminal/blueprint-firebase-deploy-production@git:20260929.f3ad1d7

Pins git:20260929.f3ad1d7 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
receptron/mulmoterminal
Path
blueprints/firebase/skills/deploy-production/SKILL.md
Versions recorded
3
Latest version
git:20260929.f3ad1d7, committed Sep 29, 2026
First version recorded
Sep 25, 2026
Size
2,316 bytes
Repository stars
261
License
MIT

Deploy the same build to the production project.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Publish to production

This is the **deploy-production** gate: the user has approved it. Deploy the same source that was verified on dev — do not change anything between the two.

1. `yarn build`, then give this build an id and ship it with the site:
   `node -e 'console.log(require("crypto").randomUUID())' > .blueprint/build-id && cp .blueprint/build-id dist/blueprint-build.txt`,
   then `firebase deploy --project prod`. The check compares the served id with `.blueprint/build-id`, so it
   proves THIS build is live. Git is not needed for this.
2. Tell the user the URL and that the next change should go through dev first.
3. Write `.blueprint/start-here.md`, in the spec's language. It is what the person sees the moment the build
   finishes, so it answers "now what?" in the order they will need it:
   - **Open it** — the production URL (`https://<prod-project-id>.web.app`) and who can sign in, and how.
   - **Check that it works** — one checkbox per must-have in the spec, each an action and what should happen
     (`- [ ] 申請を 1 件出す → 承認者の一覧に出る`), using the app's real screen and button names; one for
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add receptron/mulmoterminal/blueprint-firebase-deploy-production@sha256:3b364a07e4706c45

The line at the top of this page pins the label git:20260929.f3ad1d7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_uqo2z74xvqozpr4t.svg)](https://markdownregistry.com/a/art_uqo2z74xvqozpr4t)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 3 versions of this file, between Sep 25, 2026 and Sep 29, 2026, about one every 2 days.

versioncommittedcommitsizeaudit
git:20260929.f3ad1d7 latest2026-09-29 f3ad1d7 2,316 BA view · diff
git:20260925.24473822026-09-25 2447382 1,284 BA view · diff
git:20260925.6ec93262026-09-25 6ec9326 1,057 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (2316 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

receptron/mulmoterminal · 261 stars · license MIT · pushed 2026-11-05 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_uqo2z74xvqozpr4t
GET https://markdownregistry.com/api/v1/resolve?ref=receptron/mulmoterminal/blueprint-firebase-deploy-production
GET https://markdownregistry.com/api/v1/blob/3b364a07e4706c457e9e78841be95fe4029d069a38d8fb63391fc9205e2bb755

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from receptron/mulmoterminal

CLAUDE.md CLAUDE.md file
receptron/mulmoterminal · CLAUDE.md
git:20261021.10c7ccc · audit A · 261 stars
blueprint-adopt-apply SKILL.md skill
receptron/mulmoterminal · blueprints/adopt/skills/apply/SKILL.md · Set chaff up in the folder: chaff.yaml for the chosen genre, today's findings shelved in .chaff-baseline.json, and…
git:20260930.96c1fe0 · audit A · 261 stars
blueprint-adopt-survey SKILL.md skill
receptron/mulmoterminal · blueprints/adopt/skills/survey/SKILL.md · Measure what chaff reports on the named documents today, as the kind the person chose, and propose the setup — changing…
git:20260930.64b76e6 · audit A · 261 stars
blueprint-ask-answer SKILL.md skill
receptron/mulmoterminal · blueprints/ask/skills/answer/SKILL.md · Answer each question from the named documents only, quoting where the answer is written, or saying plainly that the…
git:20260929.67b68f6 · audit A · 261 stars
blueprint-ask-keep SKILL.md skill
receptron/mulmoterminal · blueprints/ask/skills/keep/SKILL.md · Add the approved answers to FAQ.md when the person chose to keep them, after what it already holds; change nothing…
git:20260929.101e6ff · audit A · 261 stars
blueprint-cloudflare-api SKILL.md skill
receptron/mulmoterminal · blueprints/cloudflare/skills/api/SKILL.md · Build the spec's operations as the Worker's API, with validation and tests.
git:20260929.eb2c293 · audit A · 261 stars
blueprint-cloudflare-auth SKILL.md skill
receptron/mulmoterminal · blueprints/cloudflare/skills/auth/SKILL.md · Put in the sign-in the spec chose; a published Worker is open to anyone.
git:20260929.eb2c293 · audit A · 261 stars
blueprint-cloudflare-data SKILL.md skill
receptron/mulmoterminal · blueprints/cloudflare/skills/data/SKILL.md · Turn the spec's tables into D1 migrations with tests.
git:20260929.eb2c293 · audit A · 261 stars
blueprint-cloudflare-deploy SKILL.md skill
receptron/mulmoterminal · blueprints/cloudflare/skills/deploy/SKILL.md · With approval, create the D1 database, apply the migrations, and publish with wrangler deploy.
git:20260929.f6706c8 · audit A · 261 stars
blueprint-cloudflare-handover SKILL.md skill
receptron/mulmoterminal · blueprints/cloudflare/skills/handover/SKILL.md · Write the README and the first page: where the app is, how to run and publish it, and how to back up its data.
git:20260929.eb2c293 · audit A · 261 stars
blueprint-cloudflare-prerequisites SKILL.md skill
receptron/mulmoterminal · blueprints/cloudflare/skills/prerequisites/SKILL.md · Check Node and yarn; wrangler comes with the project, and signing in to Cloudflare waits for the publish step.
git:20260929.eb2c293 · audit A · 261 stars
blueprint-cloudflare-run-check SKILL.md skill
receptron/mulmoterminal · blueprints/cloudflare/skills/run-check/SKILL.md · Build, run it with wrangler dev, and make sure the screen and the API answer.
git:20260929.eb2c293 · audit A · 261 stars

Every file in receptron/mulmoterminal

Browse by kind, by grade A, or by owner.