菜单
Scope is repo-wide. Implements the `trace-v1` contract for `X-Trace-Id` and `traceparent` correlation. Trigger this skill whenever editing HTTP middleware, transports, RPC clients, runtime-proxy, or anything that reads/writes trace headers anywhere in the monorepo. See ADR 002.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Scope is repo-wide. Enforces the cross-package import direction policy (apps depend on packages; packages depend only on packages of equal or lower role; apps never depend on each other). Trigger this skill when adding a new import that crosses workspace boundaries, modifying `package.json` `dependencies`, adding/changing barrel files, or editing ESLint `no-restricted-imports`. See `docs/architecture/dependency-policy.md`.
Scope is repo-wide. Authoritative guide for the error contract built around `ERROR_CODES`, `VnextForgeError`, `ApiResponse<T>`, and `error-presentation`. Trigger this skill whenever throwing, catching, mapping, displaying, or testing errors anywhere in the monorepo (apps/*, packages/*). See ADR 005.
Scope is the entire monorepo (root + all workspaces under apps/* and packages/*). Update the monorepo ESLint configuration in vnext-forge-studio. Use when changing shared lint rules, workspace-specific ESLint behavior, runtime globals, or logger/no-console overrides. Trigger this skill for any ESLint config work in `eslint.config.mjs` at the repo root or in any workspace.
Scope is the host-agnostic notification port in packages/designer-ui plus its shell adapters in apps/web (sonner toast) and apps/extension/webview-ui (VS Code native). Guidelines for emitting and routing transient user feedback (toast / native notification / status-bar pill). Use when calling showNotification(...), wiring a new shell sink, deciding between transient feedback and inline screen state, or working on status-bar notification chrome.
Scope is apps/web (web frontend). Optional guidance for theming and color tokens in the web app. Use only when the task is explicitly about visual system work; do not treat theme token migration as a required part of the architecture refactor. Trigger this skill for any theming or color token work under `apps/web`.
Scope is repo-wide domain knowledge (not bound to a single workspace). vNext Runtime platform referansı. Workflow, state, transition, task, schema, view, function ve extension kavramlarını, JSON tanım yapılarını ve C# mapping/rule pattern'lerini kapsar. vNext bileşenleri oluşturulurken veya düzenlenirken bu skill'i kullanın. Trigger this skill whenever vNext workflow/task/schema/view/function/extension JSON or `.csx` mapping/rule files are being created or edited anywhere in the monorepo (or in target vnext domain repositories).
| name | trace-headers |
| description | Scope is repo-wide. Implements the `trace-v1` contract for `X-Trace-Id` and `traceparent` correlation. Trigger this skill whenever editing HTTP middleware, transports, RPC clients, runtime-proxy, or anything that reads/writes trace headers anywhere in the monorepo. See ADR 002. |
trace-v1)Scope: Repo-wide. Authoritative ADR:
docs/architecture/adr/002-trace-headers.md.
apps/server always generates a fresh X-Trace-Id (UUID v4) per inbound request. It does not adopt any inbound X-Trace-Id.traceparent is informational. If present, the W3C trace ID is parsed and stored on the Hono context as linkedTraceId. It is logged for correlation but never becomes the primary traceId.X-Trace-Id. Set in a finally block in the traceIdMiddleware so success, validation failure, and crash paths all emit the header.X-Trace-Id propagates outbound. The runtime-proxy includes the current request's X-Trace-Id on every outgoing call (built by buildRuntimeProxyOutboundHeaders).VnextForgeError.traceId is set from the ambient traceId whenever the error is constructed inside a request.traceId on ApiFailure and surfaces it in dev logs and the error fallback UI for support copy.apps/server/src/shared/middleware/trace-id.tspackages/services-core/src/services/runtime-proxy/runtime-proxy.service.ts (buildRuntimeProxyOutboundHeaders)apps/web/src/shared/api/client.ts (preserves traceId from ApiFailure)apps/server/src/__tests__/trace-id.test.tsX-Trace-Id into the response.X-Trace-Id. Generate it.X-Trace-Id on every response, including error responses.X-Trace-Id survives explicitly via the helper, not via blanket forwarding.linkedTraceId when present so external systems' traces can be joined out-of-band.trace-id → request-logger → cors → body-limit → routes → error-handler
trace-id runs first so every later middleware (including error-handler) can read c.get('traceId').
traceparent on responses unless we adopt distributed tracing repo-wide (deferred).X-Trace-Id after the response leaves the handler.docs/architecture/adr/002-trace-headers.mddocs/architecture/adr/005-error-taxonomy.md — traceId ↔ VnextForgeError.docs/architecture/adr/001-trust-model.md — why we don't trust inbound trace headers.