元件檢查器更新工具
技能當基礎 React 元件的屬性、狀態、行為或測試套件變更時,稽核並同步處理現有的獨立元件開發檢查器。協調三種狀態類別 (可編輯、屬性、計算)、重新整理淺顯易懂的測試驗證固定裝置、更新「上次更新時間」時間戳記方塊,以及驗證正式環境 tree shaking (移除沒用到的程式碼) 完整性。
登入即可使用這項技能
登入 Google 開發人員個人檔案,即可查看及複製「Build It!」系列中使用的完整技能。
須具備開發人員設定檔
您不符合建立開發人員設定檔的資格。請通知 Workspace 管理員啟用這項功能。
建立開發人員設定檔
免費建立 Google 開發人員個人檔案,即可解鎖所有 Build It! 技能、規則、提示詞和構件。
加入 Builder Central 即可解鎖
一鍵領取免費的 Builder 會員徽章,即可解鎖所有 Build It! 技能、規則、提示和構件。
如何在 Google Antigravity 安裝及使用
將這項技能新增至 Google Antigravity 工作區,即可在基礎元件演進時,讓現有元件檢查工具保持一致:
- 在專案工作區中建立
.agents/skills/component-inspector-updater/資料夾 (或開啟 Google Antigravity 的「Customizations」>「Skills」,新增工作區技能)。 - 將下列完整 Markdown 定義儲存為該資料夾中的
SKILL.md。 - 修改元件後,請手動叫用這項技能 (例如:「使用 component-inspector-updater 技能,將 CoachChatInspector 與我的最新變更同步」),或安裝檢查器編輯模式規則,讓 Google Antigravity 在檢查器編輯模式啟用時自動執行這項工作流程。
- 需要先建構全新的檢查器嗎?使用隨附的元件檢查器產生器技能。
元件檢查器更新工具技能定義
將這段完整的技能定義複製到工作區,並命名為 SKILL.md。
SKILL.md (.agents/skills/component-inspector-updater/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.