Component Inspector Updater
기술기본 React 구성요소의 속성, 상태, 동작 또는 테스트 모음이 변경될 때 기존의 격리된 구성요소 개발 검사기를 감사하고 동기화합니다. 세 가지 상태 카테고리(수정 가능, 속성, 계산됨)를 조정하고, 일반 영어 테스트 인증 고정 장치를 새로고침하고, '최종 업데이트' 타임스탬프 칩을 진행하고, 프로덕션 트리 셰이킹 무결성을 확인합니다.
이 스킬을 사용하려면 로그인하세요.
Google 개발자 프로필로 로그인하여 Build It! 시리즈에 사용된 전체 기술을 확인하고 복사하세요.
개발자 프로필 필요
개발자 프로필을 사용할 수 없습니다. Workspace 관리자에게 이 기능을 사용 설정하도록 요청하세요.
개발자 프로필 만들기
무료 Google 개발자 프로필을 만들어 모든 Build It! 기술, 규칙, 프롬프트, 아티팩트를 활용하세요.
Builder Central에 가입하여 활용하기
클릭 한 번으로 무료 빌더 멤버십 배지를 신청하여 모든 Build It! 기술, 규칙, 프롬프트, 아티팩트를 활용해 보세요.
Google Antigravity에서 설치 및 사용하는 방법
기본 구성요소가 발전할 때마다 기존 구성요소 검사기를 정렬된 상태로 유지하려면 이 기술을 Google Antigravity 작업공간에 추가하세요.
- 프로젝트 작업공간에
.agents/skills/component-inspector-updater/폴더를 만듭니다(또는 Google Antigravity 맞춤설정 > 기술을 열어 작업공간 기술을 추가합니다). - 아래의 전체 마크다운 정의를 해당 폴더 내에
SKILL.md로 저장합니다. - 구성요소를 수정한 후 수동으로 호출하거나(예: 'component-inspector-updater 스킬을 사용하여 CoachChatInspector를 최신 변경사항과 동기화해 줘') Inspector 수정 모드 규칙을 설치하여 Inspector 수정 모드가 활성 상태인 동안 Google Antigravity가 이 워크플로를 자동으로 실행하도록 합니다.
- 새로운 검사기를 먼저 스캐폴딩해야 하나요? 컴패니언 Component Inspector Generator 기술을 사용합니다.
구성요소 검사기 업데이트 도구 스킬 정의
이 전체 스킬 정의를 작업공간에 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.