Skip to content

firebase-link-and-change-notice-unity

Firebase: Every Unity Game Is Linked, Every Change Is Announced

Section titled “Firebase: Every Unity Game Is Linked, Every Change Is Announced”

Always-loaded, Unity-specific. Two Firebase duties plus the Figma link; the link record lives in .claude/t1k-project-links.json.

  1. Every Unity project is linked to a Firebase project. firebase.projectId in the links file is the proof. None exists yet: create one (studio convention theone-<game>, display name TheOne-<Game>, under the studio org, no billing). The SessionStart project-links-check hook names the exact steps when firebase or firebase-thread is missing; do not re-derive them. Config files (google-services.json, GoogleService-Info.plist) enter the repo only by PR and are never printed.

  2. Announce every Firebase change before the turn ends. Remote Config parameters or conditions, A/B tests or experiments, config-file swaps, project or app creation or deletion, and Analytics/Crashlytics toggles each get one post in the game’s firebase.threadId Discord thread: what changed, the console link, how to undo it, and <@discord.tagUserId> (read both ids from the links file, never hardcode). Follow the t1k-discord-message layout contract. No threadId yet: create the “Firebase changes” thread first, record it, then post. A change that is not announced is unfinished work.

  3. Every Unity project records its Figma file. figma.fileKey + figma.url in the links file; the hook’s figma token tells you to ask the user for the figma.com URL via AskUserQuestion. Never invent one. Opt-out: "figma": {"optOut": true}.

Firebase opt-out is "firebase": {"optOut": true} in the links file. Rationale and schema: docs/project-links-check.md (theonekit-core). Bootstrap step: t1k:unity:base:template-bootstrap § 5.