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.
-
Every Unity project is linked to a Firebase project.
firebase.projectIdin the links file is the proof. None exists yet: create one (studio conventiontheone-<game>, display nameTheOne-<Game>, under the studio org, no billing). The SessionStartproject-links-checkhook names the exact steps whenfirebaseorfirebase-threadis missing; do not re-derive them. Config files (google-services.json,GoogleService-Info.plist) enter the repo only by PR and are never printed. -
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.threadIdDiscord thread: what changed, the console link, how to undo it, and<@discord.tagUserId>(read both ids from the links file, never hardcode). Follow thet1k-discord-messagelayout contract. NothreadIdyet: create the “Firebase changes” thread first, record it, then post. A change that is not announced is unfinished work. -
Every Unity project records its Figma file.
figma.fileKey+figma.urlin the links file; the hook’sfigmatoken tells you to ask the user for the figma.com URL viaAskUserQuestion. 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.