agentleFS
ea-toolkitea-toolkit/architecture-catalog/.claude/skills/deploy/SKILL.md

deploy

Skill38 starsChanged 9 months agoMITView on GitHub

Build and deploy static sites (catalog-ui, docs-site) to Firebase Hosting. Supports dry-run preview, selective target deployment, and automatic build detection.

  • Installs packages

159 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pm-discovery, qa-phase and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ww-w-aiSkill

    pm-discovery

    PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.

    Also in 3 projects that use this

  • ww-w-aiSkill

    qa-phase

    Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.

    Also in 3 projects that use this

  • +10 more from ww-w-ai

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 141 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No arguments = build and deploy all targets

    line 20
  2. Very specific:

    Check for --dry-run flag

    line 27
  3. Very specific:

    Check for --target <value> (default: all)

    line 28
  4. Distinctive:

    Run these checks before proceeding:

    line 32
  5. Distinctive:

    If any check fails, report the error and stop.

    line 45
  6. Distinctive:

    If targeting a specific site:

    line 69
  7. Distinctive:

    If build fails, show the error output and stop.

    line 104
  8. Very specific:

    If deploy fails, show the Firebase error.

    line 105
  9. Very specific:

    If node_modules/ is missing, npm ci handles it automatically.

    line 106

“Common” is measured: kept by at least 6 in 10 of the 141 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deploy to Firebase Hosting

Build and deploy the catalog UI and/or docs site to Firebase Hosting.

Arguments

  • $ARGUMENTS may contain:
    • --dry-run — Build only, skip deploy. Show what would be deployed.
    • --target catalog — Deploy only the catalog UI
    • --target docs — Deploy only the docs site
    • --target all — Deploy both (default)
    • No arguments = build and deploy all targets

Workflow

1. Parse Arguments

Extract flags from $ARGUMENTS:

  • Check for --dry-run flag
  • Check for --target <value> (default: all)

2. Validate Prerequisites

Run these checks before proceeding:

# Check Firebase CLI is installed
which firebase || echo "ERROR: Firebase CLI not installed. Run: npm install -g firebase-tools"

# Check Firebase auth
firebase projects:list --limit 1 2>&1 || echo "ERROR: Not authenticated. Run: firebase login"

# Check firebase.json exists
test -f firebase.json || echo "ERROR: firebase.json not found in project root"

If any check fails, report the error and stop.

3. Build

Based on --target:

Catalog UI (target = catalog or all):

cd catalog-ui && npm ci && npm run build

Report build output size: du -sh catalog-ui/dist

Docs Site (target = docs or all):

cd docs-site && npm ci && npm run build

Report build output size: du -sh docs-site/dist

4. Deploy (skip if --dry-run)

firebase deploy --only hosting

If targeting a specific site:

firebase deploy --only hosting:catalog
# or
firebase deploy --only hosting:docs

5. Report

On dry-run:

**Dry Run Complete**

| Target | Build | Size |
|--------|-------|------|
| Catalog UI | OK | X MB |
| Docs Site | OK | X MB |

Ready to deploy. Run `/deploy` (without --dry-run) to push to Firebase.

On deploy:

**Deployed Successfully**

| Target | URL |
|--------|-----|
| Catalog UI | https://architecture-catalog.web.app |
| Docs Site | https://docs-architecture-catalog.web.app |

Firebase project: ea-toolkit-demo-ac513

Error Handling

  • If build fails, show the error output and stop. Do not deploy a broken build.
  • If deploy fails, show the Firebase error. Common fix: firebase login to re-authenticate.
  • If node_modules/ is missing, npm ci handles it automatically.

Notes

  • The CI/CD pipeline (.github/workflows/deploy.yml) auto-deploys on push to main. This skill is for manual/preview deployments.
  • Firebase project ID: ea-toolkit-demo-ac513 (from .firebaserc)
  • Hosting targets: catalog → architecture-catalog, docs → docs-architecture-catalog

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.