Firebase RS

Workflow

Use this skill for firebase-rs, the Rust crate exposed as firebase_rs, when implementing Firebase Realtime Database access through its REST API wrapper.

1. Inspect the project first: confirm async runtime, error handling style, config/env conventions, and whether serde models already exist.
2. Add dependencies conservatively. Typical app dependencies are firebase-rs, serde with derive, and an async runtime such as tokio.
3. Keep Firebase database URLs and auth tokens in config or environment variables. Do not hardcode secrets in examples or committed code.
4. Build paths with chained .at("segment") calls instead of manual URL string concatenation.
5. Prefer typed get::<T>(), set(&value), and update(&value) over raw strings unless the caller explicitly wants raw JSON/text.
6. Match existing project error style. Avoid .unwrap() in production code unless nearby code uses panics for setup failures.
7. Run the Rust formatter and the relevant tests/checks after edits.

Project Setup

Check the latest crate version before pinning if the user asks for current dependencies. The crate name in Cargo.toml is firebase-rs; the Rust module path is firebase_rs.

Typical dependency shape: