Menu
Use for shipped UI action journal, request correlation, WebSocket churn, or frontend observability work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use to deliver an approved OpenSpec change through execution matrix, Beads, checks, and handoff.
Use to verify the full pool run flow on a live contour through report and OData evidence.
Use to inspect, restart, and verify local frontend/backend runtimes with targeted probes.
Work with 1C databases via OData protocol: create batch operations, handle transactions (< 15 seconds!), debug OData requests.
Execute DevOps tasks for CommandCenter1C: start/stop services locally (host machine), check health endpoints, view logs, run migrations. Use when user needs to start development environment, check service status, debug deployment issues, or mentions local development, health checks, logs, restart.
Navigate monorepo structure, locate components, explain service dependencies.
| name | ui-action-observability |
| description | Use for shipped UI action journal, request correlation, WebSocket churn, or frontend observability work. |
Пакует repeatable workflow для shipped capability ui-action-observability: снять bounded UI journal bundle, связать его с request_id / ui_action_id на backend boundary и безопасно расширить instrumentation без поломки redaction-first contract.
Используй, когда пользователь просит:
Не используй для обычной UI-правки без observability/debug scope.
openspec/specs/ui-action-observability/spec.mdfrontend/src/observability/uiActionJournal.tsfrontend/src/App.tsxfrontend/src/api/client.tsfrontend/src/observability/confirmWithTracking.tsfrontend/src/components/ErrorBoundary.tsxfrontend/src/hooks/useWorkflowExecution.tsorchestrator/apps/api_v2/observability.pydebug/export-ui-journal.shdocs/agent/RUNBOOK.md, docs/agent/VERIFY.md и DEBUG.md, если задача про runtime incident или export bundle../debug/export-ui-journal.sh [url-pattern] или ./debug/eval-frontend.sh "JSON.stringify(window.__CC1C_UI_JOURNAL__?.exportBundle() ?? null, null, 2)".events[] для route/action/error chronology;active_http_requests;active_websockets_by_owner;active_websockets_by_reuse_key;recent_churn_anomalies.request_id и ui_action_id из bundle с backend problem payload и server logs.frontend/src/App.tsxconfirmWithTracking.tsfrontend/src/api/client.tsfrontend/src/components/ErrorBoundary.tsxfrontend/src/hooks/useWorkflowExecution.tsorchestrator/apps/api_v2/observability.pytrackUiAction(...) или confirmWithTracking(...).X-Request-ID и X-UI-Action-ID, backend должен возвращать их в headers/problem payloads на fail-closed paths.owner, reuseKey, channelKind, socketInstanceId, lifecycle outcome и churn signal.trackUiAction должны оставаться sync или microtask-detached; не вводи произвольные async handlers без обновления supporting logic и tests.cd frontend && npx vitest run src/observability/__tests__/uiActionJournal.test.ts src/api/__tests__/client.observability.test.ts src/observability/__tests__/trackUiActionUsage.test.ts./scripts/dev/pytest.sh -q orchestrator/apps/api_v2/tests/test_problem_details_request_correlation.py./scripts/dev/check-agent-doc-freshness.sh./debug/export-ui-journal.sh [url-pattern]request_id / ui_action_id бьются между frontend bundle и backend payload/logsПримеры:
/pools/runs и найди связанный backend request."trackUiAction и проверь redaction."