AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Firebase Game Backend

skill-furkantokkan-agent-foundry-firebase-game-backend · by furkantokkan

Use when building or reviewing Firebase-backed game features for Unity or JavaScript, including Firebase Auth, Cloud Firestore, Realtime Database, Cloud Functions Gen2, Express.js HTTP APIs, Unity request/response clients, Cloud Storage, Remote Config, Analytics, App Check, security rules, local emulators, deployment, data modeling, and client/server boundaries.

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-furkantokkan-agent-foundry-firebase-game-backend

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-furkantokkan-agent-foundry-firebase-game-backend)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● yesterday

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Firebase Game Backend? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Firebase Game Backend

Use this skill for Firebase features that support a Unity game, web dashboard, companion app, or JavaScript service.

First Read

Inspect whichever files exist:

  • firebase.json
  • .firebaserc
  • firestore.rules
  • firestore.indexes.json
  • storage.rules
  • functions/package.json
  • functions/src/ or functions/index.js
  • Web app Firebase config files
  • Unity Firebase wrapper code under Assets/

Core Rules

  • Client SDKs are untrusted. Security rules and Cloud Functions enforce policy.
  • Do not put privileged operations in Unity or browser code.
  • Keep Firestore rules restrictive by default.
  • Rules are not filters: queries must match the rule constraints.
  • Use Firebase Auth UID as the primary ownership boundary.
  • Validate writes in security rules and again in trusted server code.
  • Use Cloud Functions or another trusted backend for economy mutations,

anti-cheat-sensitive rewards, purchases, inventory grants, and leaderboards.

  • Use Firebase Emulator Suite for rules and function testing when available.
  • Keep Firebase code behind interfaces in Unity.
  • For this game backend style, prefer Firebase Functions Gen2 with JavaScript

and Express.js HTTP routes. Unity should call those routes through typed request/response client wrappers, not by scattering raw HTTP calls through gameplay code.

  • New or changed game API behavior needs focused unit tests for the expected

success path and important failure paths. Emulator/Newman coverage complements handler unit tests; it does not replace them.

Workflow

  1. Identify the feature: auth, save, leaderboard, inventory, economy, matchmaking,

remote config, analytics, storage, or admin tooling.

  1. Decide which operations are safe on the client and which require trusted code.
  2. Check data model, indexes, rules, and Cloud Functions together.
  3. Add unit tests for expected behavior when changing routes, authorization,

validation, response contracts, or write behavior.

  1. For Unity, expose Firebase through game-facing interfaces.
  2. For JavaScript, use the modular Web SDK for browser code and Admin SDK only

in trusted server environments.

  1. For Functions HTTP APIs, keep Express routing, request validation, auth/App

Check guards, response envelopes, and Unity DTO alignment together.

Reference Loading

  • Data modeling and products: references/firebase-stack.md
  • Functions Gen2 + Express + Unity request/response:

references/functions-express-unity.md

  • Security rules: references/security-rules.md
  • Unity integration: references/unity-firebase.md

Official docs to verify current setup details:

  • Unity SDK: https://firebase.google.com/docs/unity/setup
  • Web SDK: https://firebase.google.com/docs/web/setup
  • Security Rules: https://firebase.google.com/docs/rules/
  • Firestore Rules: https://firebase.google.com/docs/firestore/security/get-started

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Databases