Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

inspector-implementation

Étoiles169

Forks14

Mis à jour18 avril 2026 à 18:12

Use when an agent needs to implement or modify the Inspector library itself — panel UI, hierarchy/runtime behavior, custom property models, macros, or Example-app dogfooding. Especially useful when changing `Sources/Inspector/`, `Sources/InspectorInterface/`, or `Sources/InspectorMacros/` and you need the repo's architecture and verification workflow in one place.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

ipedro

ipedro/Inspector

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	inspector-implementation
description	Use when an agent needs to implement or modify the Inspector library itself — panel UI, hierarchy/runtime behavior, custom property models, macros, or Example-app dogfooding. Especially useful when changing `Sources/Inspector/`, `Sources/InspectorInterface/`, or `Sources/InspectorMacros/` and you need the repo's architecture and verification workflow in one place.

Inspector Implementation

Overview

Use this skill when the work is inside the Inspector repo, not in a consumer app. Typical tasks:

changing runtime behavior in Sources/Inspector/
adding or adjusting Inspector UI panels
extending custom property/action flows
changing macro-generated Inspector integration (@InspectorPanel, @InspectorProperty)
dogfooding changes through the Example app

Fast architecture map

Start from these zones:

Sources/Inspector/Manager/ — top-level orchestration and presentation flow
Sources/Inspector/ViewHierarchy/ — live hierarchy capture and element references
Sources/Inspector/ElementInspector/ — element panel UI and interactions
Sources/Inspector/ElementLibraries/ — per-type property/section definitions
Sources/Inspector/Bridge/ — Inspector MCP bridge/runtime semantic layer
Sources/InspectorInterface/ — public macro declarations / debug-facing interface surface
Sources/InspectorMacros/ — macro expansion logic
Example/Example/ — dogfooding app and runtime verification target

When touching specific features

Runtime / bridge / semantic tooling

Look first in:

Sources/Inspector/Bridge/
Tests/InspectorTests/InspectorBridgeServiceTests.swift
Tests/InspectorTests/InspectorMCPTransportTests.swift
Tests/InspectorMCPServerTests/
Tests/InspectorMCPWireTests/

Panel UI / element inspector behavior

Look first in:

Sources/Inspector/ElementInspector/
Sources/Inspector/CommonUI/
Sources/Inspector/TransitionCoordinator/

Built-in editable properties / sections

Look first in:

Sources/Inspector/ElementLibraries/Sections/
Sources/Inspector/Extensions/InspectorElementViewModelProperty/

Customer-extensibility / macros

Look first in:

Sources/InspectorInterface/
Sources/InspectorMacros/
Example/Example/PlaygroundViewController.swift
Example/Example/RoundedButton.swift

Verification

SwiftPM/server-side verification

swift build --product InspectorMCPServer
swift build --target InspectorMCPWireTests
swift build --target InspectorMCPServerTests

Example app / iOS verification

xcodebuild test \
  -project Example/Example.xcodeproj \
  -scheme Example \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro,OS=26.4.1'

Prefer focused -only-testing: runs while iterating, then broaden when the slice stabilizes.

References

Read only when needed:

references/architecture.md

Plus depuis ce dépôt

même dépôt

inspector-integration

ipedro/Inspector

Use when an agent needs to integrate the Inspector library into an app without focusing on the MCP bridge: startup wiring, configuration/customization, debug-only gating, and custom panel registration. Especially useful when patching another iOS app to call `Inspector.start()` correctly and optionally register custom Inspector libraries.

2026-04-18169

inspector-mcp

ipedro/Inspector

Use when an agent needs to inspect a live iOS app through the Inspector MCP bridge, register or troubleshoot InspectorMCPServer for a consumer Xcode project, or query, resolve, and snapshot the live UIKit hierarchy on Simulator. Especially useful when Inspector is a SwiftPM dependency of another app and the Inspector package path must be derived from Xcode DerivedData instead of assumed from the current repo.

2026-04-18169

inspector-mcp-consumer

ipedro/Inspector

Use when an agent needs to patch a consumer iOS app so it exposes the Inspector MCP bridge, add or verify the app-side Inspector startup configuration, or choose the correct UIKit or SwiftUI lifecycle entry point for `enableMCPBridge`, `snapshotExpiration = 300`, and `snapshotMaxCount = 8`. Especially useful when preparing another app to be driven by `InspectorMCPServer` and then handed off to the `inspector-mcp` skill for live inspection.

2026-04-17169

name	inspector-implementation
description	Use when an agent needs to implement or modify the Inspector library itself — panel UI, hierarchy/runtime behavior, custom property models, macros, or Example-app dogfooding. Especially useful when changing `Sources/Inspector/`, `Sources/InspectorInterface/`, or `Sources/InspectorMacros/` and you need the repo's architecture and verification workflow in one place.

Inspector Implementation

Overview

Use this skill when the work is inside the Inspector repo, not in a consumer app. Typical tasks:

changing runtime behavior in Sources/Inspector/
adding or adjusting Inspector UI panels
extending custom property/action flows
changing macro-generated Inspector integration (@InspectorPanel, @InspectorProperty)
dogfooding changes through the Example app

Fast architecture map

Start from these zones:

Sources/Inspector/Manager/ — top-level orchestration and presentation flow
Sources/Inspector/ViewHierarchy/ — live hierarchy capture and element references
Sources/Inspector/ElementInspector/ — element panel UI and interactions
Sources/Inspector/ElementLibraries/ — per-type property/section definitions
Sources/Inspector/Bridge/ — Inspector MCP bridge/runtime semantic layer
Sources/InspectorInterface/ — public macro declarations / debug-facing interface surface
Sources/InspectorMacros/ — macro expansion logic
Example/Example/ — dogfooding app and runtime verification target

When touching specific features

Runtime / bridge / semantic tooling

Look first in:

Sources/Inspector/Bridge/
Tests/InspectorTests/InspectorBridgeServiceTests.swift
Tests/InspectorTests/InspectorMCPTransportTests.swift
Tests/InspectorMCPServerTests/
Tests/InspectorMCPWireTests/

Panel UI / element inspector behavior

Look first in:

Sources/Inspector/ElementInspector/
Sources/Inspector/CommonUI/
Sources/Inspector/TransitionCoordinator/

Built-in editable properties / sections

Look first in:

Sources/Inspector/ElementLibraries/Sections/
Sources/Inspector/Extensions/InspectorElementViewModelProperty/

Customer-extensibility / macros

Look first in:

Sources/InspectorInterface/
Sources/InspectorMacros/
Example/Example/PlaygroundViewController.swift
Example/Example/RoundedButton.swift

Verification

SwiftPM/server-side verification

swift build --product InspectorMCPServer
swift build --target InspectorMCPWireTests
swift build --target InspectorMCPServerTests

Example app / iOS verification

xcodebuild test \
  -project Example/Example.xcodeproj \
  -scheme Example \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro,OS=26.4.1'

Prefer focused -only-testing: runs while iterating, then broaden when the slice stabilizes.

References

Read only when needed:

references/architecture.md