Firebase Hosting Basics · firebase/agent-skills · Skills Docs

Skills

Chapter 9 of 12

Firebase Hosting Basics

Deploys and configures classic Firebase Hosting for static websites, single-page apps (SPAs), and microservices.

1 minute · 247 words · 7 sections

hosting-basics

This skill provides instructions and references for working with Firebase Hosting, a fast and secure hosting service for your web app, static and dynamic content, and microservices.

Firebase Hosting provides production-grade web content hosting for developers. With a single command, you can deploy web apps and serve both static and dynamic content to a global CDN (content delivery network).

Key Features:

Fast Content Delivery: Files are cached on SSDs at CDN edges around the world.
Secure by Default: Zero-configuration SSL is built-in.
Preview Channels: View and test changes on temporary preview URLs before deploying live.
GitHub Integration: Automate previews and deploys with GitHub Actions.
Dynamic Content: Serve dynamic content and microservices using Cloud Functions or Cloud Run.

Hosting vs App Hosting

Choose Firebase Hosting if:

You are deploying a static site (HTML/CSS/JS).
You are deploying a simple SPA (React, Vue, etc. without SSR).
You want full control over the build and deploy process via CLI.

Choose Firebase App Hosting if:

You are using a supported full-stack framework like Next.js or Angular.
You need Server-Side Rendering (SSR) or ISR.
You want an automated “git push to deploy” workflow with zero configuration.

Instructions

1. Configuration (`firebase.json`)

For details on configuring Hosting behavior, including public directories, redirects, rewrites, and headers, see configuration.md (opens in a new tab).

2. Deploying

For instructions on deploying your site, using preview channels, and managing releases, see deploying.md (opens in a new tab).

3. Emulation

To test your app locally:

npx -y firebase-tools@latest emulators:start --only hosting

This serves your app at http://localhost:5000 by default.

Appendix 9.1–9.2

2 files · 3 KB

Everything this skill ships beside its prose. All of it is set here, as subchapters of chapter 9.

ReferencesMarkdown · 2 files

Documentation the agent loads on demand, rather than up front.

Install this repository

$ npx skills add firebase/agent-skills

» /plugin marketplace add firebase/agent-skills

Skills install per repository, not per chapter — the CLI has no documented per-skill form, so we do not print one.

About this skill

Trigger

Deploys and configures classic Firebase Hosting for static websites, single-page apps (SPAs), and microservices. Use when deploying static sites/SPAs, setting up custom domains, configuring firebase.json hosting settings (redirects, rewrites, headers, multi-site), or managing preview channels. Don't use for Firebase App Hosting (Next.js/SSR), Auth, Firestore queries/rules, Data Connect, or Crashlytics.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/firebase/agent-skills, branch main, last pushed 6 August 2026.

Licence

Apache-2.0 — the text of every chapter is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

12 chapters found by walking the repository tree for SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.

Issue colours

Resolved from a curated brand profile — hue 88°, chroma 0.168. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this chapter so the document has one h1 and no skipped levels:

Shifted “7 headings” from h1 to h2 so the chapter title is the only h1.

Spec compliance

1 editorial note across 1 of 12 chapters. They are printed in the margin of each chapter rather than as errors here.

Firebase Data Connect — 1 note

Images

Images inside a chapter come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Firebase, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

hosting-basics

Overview

Hosting vs App Hosting

Instructions

1. Configuration (firebase.json)

2. Deploying

3. Emulation

Appendix 9.1–9.2

ReferencesMarkdown · 2 files

About this skill

Trigger

Colophon

Appendix 9.1–9.2

ReferencesMarkdown · 2 files

1. Configuration (`firebase.json`)