Actualizador del inspector de componentes
HabilidadAudita y sincroniza un inspector de desarrollo de componentes aislados existente cuando cambian las propiedades, el estado, el comportamiento o los paquetes de pruebas del componente de React subyacente. Concilia las tres categorías de estado (Editable, Props, Computed), actualiza los dispositivos de verificación de pruebas en lenguaje natural, avanza el chip de marca de tiempo "Última actualización" y verifica la integridad de la eliminación de código muerto en producción.
Accede para usar esta habilidad
Accede con tu Perfil del desarrollador de Google para ver y copiar la habilidad completa que se usa en la serie Build It!
Se requiere un perfil de desarrollador
No cumples con los requisitos para tener un perfil del desarrollador. Notifica a tu administrador de Workspace para que habilite esta función.
Crear un Perfil del desarrollador
Crea un Perfil del desarrollador de Google gratuito para desbloquear todas las habilidades, reglas, instrucciones y artefactos de Build It!
Únete a Builder Central para desbloquearlo
Reclama tu insignia de membresía de Builder sin costo con un solo clic para desbloquear todas las habilidades, reglas, instrucciones y artefactos de Build It!
Cómo instalar y usar Google Antigravity
Agrega esta habilidad a tu espacio de trabajo de Google Antigravity para mantener alineados los inspectores de componentes existentes cada vez que evolucione un componente subyacente:
- Crea la carpeta
.agents/skills/component-inspector-updater/en el espacio de trabajo de tu proyecto (o abre Google Antigravity Customizations > Skills para agregar una habilidad del espacio de trabajo). - Guarda la definición completa de Markdown que aparece a continuación como
SKILL.mddentro de esa carpeta. - Invócala de forma manual después de modificar un componente (por ejemplo: "Usa la habilidad component-inspector-updater para sincronizar CoachChatInspector con mis cambios más recientes") o instala la regla Inspector Editing Mode para que Google Antigravity ejecute este flujo de trabajo automáticamente mientras el modo de edición de Inspector esté activo.
- ¿Necesitas crear primero un inspector nuevo? Usa la habilidad complementaria Component Inspector Generator.
Definición de la habilidad Component Inspector Updater
Copia esta definición de habilidad completa en tu espacio de trabajo como SKILL.md.
---
name: component-inspector-updater
description: >-
Audits and synchronizes an existing isolated component development inspector when the underlying
React component's props, state, behavior, or test suites change. Reconciles the three state
categories (Editable, Props, Computed), refreshes plain-English test verification fixtures,
advances the 'Last Updated' timestamp chip, and verifies production tree-shaking integrity.
---
# Component Inspector Updater Skill
Use this skill whenever an underlying React/Next.js component (e.g. `CurrentSetCard`, `WorkoutHeader`) has undergone changes (such as added, renamed, or deleted props, altered state management, or updated test suites) and its existing development inspection route (`src/dev/inspectors/[ComponentName]Inspector.tsx`) needs to be brought up to date.
---
## 1. Core Update Principles
Because component inspectors represent a manual snapshot at a fixed point in time, any change to the target component introduces potential **inspector drift**. When updating an inspector:
1. **Full Prop Reconcilation**: Every property in `interface [ComponentName]Props` must be accounted for in either the **Editable State** or **Props State**.
2. **Category Accuracy**:
- **Editable State**: Only state variables that the user/athlete directly manipulates during active usage.
- **Props State**: Parent inputs and configuration.
- **Computed State**: All values derived via `useMemo` from the other two categories.
3. **Plain-English Test Synchronization**:
- Synchronize test cards with the latest assertions from `scripts/` and `docs/architecture/client_architecture_spec.md`.
- Update test fixture handlers so `[Load Test Fixture]` accurately populates the new prop structure.
4. **Preservation of Custom Presets & Scenarios**:
- NEVER delete, reset, or overwrite custom presets, scenarios, or edge-case fixtures that were manually added to the inspector (such as weekly overhaul proposals, multi-exercise scenarios, or custom user test cards).
- Only adapt their data shape to conform to updated prop signatures if types changed; never revert the presets list back to a minimal default.
5. **Timestamp Advancement**:
- Always update `const GENERATED_AT = 'YYYY-MM-DD HH:MM [TIMEZONE]';` to the current date and time.
6. **Preserve Production Tree-Shaking**:
- Ensure the App Router stub at `src/app/dev/[slug]/page.tsx` continues to guard with `process.env.NODE_ENV === 'development'` and `notFound()` in production.
7. **Zero Viewport / Page-Scroll Disruptions**:
- Verify that prop changes, preset loaders, and fixture triggers never introduce automatic page-level scrolling (e.g. `scrollIntoView()` or viewport jumping). Internal element scrolling must always be scoped strictly to `containerRef.current.scrollTop = containerRef.current.scrollHeight` so the user's viewport on the workbench controls is preserved.
> **Skill Maintenance Policy**: Updates to this skill must reflect generic architectural standards that apply to all component inspectors across the app. Do not update this skill for one-off requests for individual components (e.g. adding a specific preset or scenario to a single component).
---
## 2. Step-by-Step Update Workflow
### Step 1: Diff and Audit the Component
1. Inspect the updated component file: `src/components/[category]/[ComponentName].tsx`.
2. Inspect the existing inspector file: `src/dev/inspectors/[ComponentName]Inspector.tsx`.
3. Identify all discrepancies:
- **Added Props**: New inputs that require state variables and inspector controls.
- **Removed / Deprecated Props**: Old inputs that should be pruned from the inspector.
- **Type Signature Changes**: Props that changed types (e.g. `number` to `string | number`, or array structure changes).
- **Callback Signature Changes**: Changes to event handlers (`onWeightChange`, `onComplete`, etc.).
### Step 2: Audit Relevant Test Suites
1. Check test files in `scripts/` (e.g., `test-active-workout-suite.ts`, `test-client-state.ts`, etc.) and the plain-English test cases in `docs/architecture/client_architecture_spec.md`.
2. Determine if any new test cases were added or existing test expectations were modified.
3. Draft plain-English titles and descriptions for any new test cases.
### Step 3: Update `src/dev/inspectors/[ComponentName]Inspector.tsx`
Perform the following edits:
1. **Advance Timestamp**:
Update the constant:
```ts
const GENERATED_AT = 'YYYY-MM-DD HH:MM [TIMEZONE]';
```
2. **Update Props & Editable State Hooks**:
- Add/remove `useState` hooks for modified props or editable fields.
- Update the dummy data presets (`loadPreset('active')`, `loadPreset('completed')`, etc.) to match new prop structures while strictly preserving all custom presets (e.g. week proposals, multi-exercise scenarios, custom fixtures).
3. **Update Computed State (`useMemo`)**:
- Recompute derived metrics if formulas or business rules changed.
- Update dependencies array in `useMemo`.
4. **Update the State Inspector Controls (Right Column)**:
- Add controls for new props in the Props or Editable cards.
- Update the Computed State grid if new derived properties were added.
5. **Update Component Canvas Invocation (Left Column)**:
- Ensure `<[ComponentName] {...props} />` passes all required new props and updated handler signatures.
6. **Update Test Cases & Fixture Buttons (Bottom Section)**:
- Update or add test fixture cards with clear, plain-English user descriptions.
- Update `[Load Test Fixture]` click handlers to set the new state/props for each test scenario.
7. **Verify Component Registry**:
- Confirm `src/dev/registry.ts` has the component correctly listed with its current name, routePath, and domain category.
### Step 4: Validate Build & Tree-Shaking Integrity
1. **Typecheck**:
```bash
npx tsc --noEmit
```
Ensure zero TypeScript compilation errors.
2. **Production Bundle Verification**:
- For routine iteration, rely on `npx tsc --noEmit`.
- Never run raw `npm run build` while a local `next dev` server is active, as it overwrites `.next/` with production bundles and wipes out dev chunk manifests.
- If full production tree-shaking verification is needed, run in an isolated directory:
```bash
NEXT_DIST_DIR=.next-build npx next build && rm -rf .next-build
```
- Confirm route `/dev/[slug]` remains minimal in size (~700 B minimal 404 stub).
---
## 3. Checklist for Inspector Verification
- [ ] All props from `[ComponentName]Props` have corresponding state and inspector controls.
- [ ] Editable and Prop state controls correctly update the live canvas.
- [ ] Computed state cards reflect all derived properties with lock badges.
- [ ] All test fixture cards have plain-English descriptions (no raw test IDs in prose).
- [ ] `[Load Test Fixture]` buttons correctly apply the fixture state.
- [ ] `const GENERATED_AT` reflects the current update timestamp.
- [ ] `data-testid="last-updated-chip"` displays the updated timestamp in the header.
- [ ] `npx tsc --noEmit` exits with 0 errors.
- [ ] `npm run build` exits with 0 errors and preserves zero production bundle impact.