# Debug Firebase Development Issues

Firebase development failures can be hard to isolate across emulators, rules, functions, auth, and deployment. This skill guides a structured debugging workflow with focused checks and repeatable fixes.

## Install

```bash
npx skillstore add 2389-research/firebase-development-debug
```

## Metadata

- - Slug: 2389-research-firebase-development-debug
- - Version: 1.0.0
- - Author: 2389-research
- - GitHub username: 2389-research
- - License: MIT
- - Repository: https://github.com/2389-research/claude-plugins/tree/main/firebase-development/skills/debug
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: external\_commands, network, filesystem, env\_access
- - Quality score: 50
- - Quality tier: warning
- - Public page: https://skillstore.pages.dev/skills/2389-research-firebase-development-debug
- - Manifest: https://skillstore.pages.dev/api/skills/2389-research-firebase-development-debug/manifest

## Capabilities

- Classifies Firebase errors by emulator, rules, functions, auth, or deployment area.
- Guides checks for emulator logs, port conflicts, and Emulator UI diagnostics.
- Recommends Firestore Rules Playground tests for permission failures.
- Helps inspect Cloud Functions errors with targeted logging and reproduction steps.
- Reviews Firebase deployment configuration and predeploy build checks.
- Prompts documentation of symptoms, root cause, fix, and prevention.

## Use Cases

- Resolve Emulator Startup Failures: Diagnose port conflicts, emulator initialization errors, and lost local emulator state.
- Debug Rules and Auth Errors: Trace permission denied errors through auth context, request data, and Rules Playground simulation.
- Investigate Deployment Breakages: Check Firebase deployment logs, project configuration, targets, and predeploy build steps.

## Prompt Templates

### Classify My Firebase Error

```
I have a Firebase development error. Help me classify whether it is emulator, rules, functions, auth, or deployment related.
```

### Debug Emulator Startup

```
My Firebase emulators do not start. Walk me through safe checks for ports, logs, and emulator state before restarting.
```

### Trace Permission Denied

```
A Firestore request returns PERMISSION_DENIED. Help me test auth context, request data, and rules evaluation.
```

### Investigate Deployment Failure

```
My Firebase deploy fails with unclear output. Build a diagnosis plan covering logs, firebase.json, targets, and predeploy hooks.
```

## Limitations

- It provides diagnostic guidance, not automatic fixes for every Firebase issue.
- It may ask to inspect local environment files that can contain secrets.
- It assumes the Firebase CLI and emulator tools are already available.
- It does not replace production incident response or cloud security review.

## Best Practices

- Confirm the issue category before running commands or changing configuration.
- Redact secrets before sharing environment file contents or debug logs.
- Export emulator state before restarts that could remove local test data.

## Anti Patterns

- Killing processes without confirming the process owner and project context.
- Pasting full .env contents into chat or issue trackers without redaction.
- Changing rules, auth, and function code at the same time during diagnosis.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-27T15:28:45.561\+00:00
- - Summary: Static analysis found shell commands, localhost network access, and environment-file inspection guidance. Review confirms these are mostly legitimate Firebase debugging instructions, but reading .env files and killing processes creates elevated operational risk. No evidence found of malicious exfiltration, prompt injection, or hidden executable payloads.

## Stats

- - Views: 200
- - Downloads: 12
- - Favorites: 0
- - Popularity score: 0