body-comp-dev

Modify and debug body-comp-tracker.html with Firebase integration and save-chain validation.

Updated Jan 3, 2026
One-click install
npx skills add https://github.com/suleman7-DMD/dental-quest --skill body-comp-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: body-comp-dev
Source: https://github.com/suleman7-DMD/dental-quest/tree/main/.claude/skills/body-comp-dev
Command: npx skills add https://github.com/suleman7-DMD/dental-quest --skill body-comp-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers modify and debug the Body Comp Tracker web app body-comp-tracker.html, enabling safe, structured edits and reliable reasoning for feature fixes and cross-app Firebase integration.

Core Features & Use Cases

  • Debug and implement changes to body-comp-tracker.html, including TDEE, mode, and targets calculations.
  • Validate the save chain and guards (mutate state -> saveState -> saveDayLog -> re-render) to prevent data loss.
  • Ensure correct data migrations (array to object) and maintain read-only ecosystem data during Firebase operations.

Quick Start

Open body-comp-tracker.html, locate the target function, implement the change, and validate using the saveState/saveDayLog flow.

Frequently Asked Questions about body-comp-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug the save chain in a Firebase-connected body tracker app?▼

To debug the body tracker save chain, validate the flow from mutate state to saveState, saveDayLog, and re-render. Ensure changes respect the 5 save guards and preserve state flags like _dataLoaded to prevent data loss across Firebase and localStorage.

What's the best way to migrate dailyLogs from an array to an object in a body composition tracker?▼

Migrating dailyLogs from an array to an object requires applying array-to-object migrations while keeping ecosystem data read-only. Verify state flags are preserved and validate the save chain to ensure Firebase integration and localStorage updates remain stable.

How do I safely modify TDEE and targets calculations without breaking app state?▼

Modifying TDEE and targets calculations safely requires implementing targeted code edits with guard validation. You must preserve state flags like _dataLoaded and verify the saveState and saveDayLog flow to prevent data loss during re-rendering.

Why does my body tracker app lose data when updating Firebase and localStorage?▼

Data loss during Firebase and localStorage updates often occurs when save guards are bypassed. Validate the complete save chain, ensure ecosystem data stays read-only, and verify that state flags like _dataLoaded are preserved during mutation and re-rendering.

Can I make surgical code edits to a body tracker HTML file without affecting read-only ecosystem data?▼

Yes, you can make surgical code edits to the body tracker HTML file while keeping ecosystem data read-only. Apply guard validation to changes, verify the save chain, and ensure state flags and data migrations are respected during Firebase operations.

What are the 5 save guards I need to check when debugging a body composition tracker?▼

The 5 save guards protect the mutation and save flow in the body composition tracker. When debugging, validate that each guard is respected during state changes, saveState, saveDayLog, and re-rendering to maintain data integrity across Firebase and localStorage.