Use this skill when changing history-series reconciliation or history-to-chart mapping behavior. This skill defines implementation patterns only; policy authority remains in instruction files.

Use This Skill When

Editing DashboardHistorySeriesSyncService reconciliation behavior.
Editing KipSeriesApiClientService integration behavior for reconciliation.
Editing history values to chart datapoint conversion.

Core Expectations

Preserve the reconciliation pipeline: dashboard state -> sync service -> API client -> plugin reconcile endpoint.
Route history response mapping behavior through HistoryToChartMapperService.
Keep plugin contract assumptions stable unless a deliberate API change is coordinated.
Keep reconciliation and mapping concerns separated.

Widget History Dialog Enhancements (Implementation Companion)

Use this checklist when changing widget history dialog behavior that affects historical series display.

Keep dialog code as a read-only history consumer; do not add reconcile orchestration to dialog components.
Keep template/wildcard expansion deterministic and stable across repeated renders.
Keep dual-axis behavior centralized in shared helpers (classification, ordering, style, and axis config).
Keep line/legend/tooltip stroke semantics sourced from the same dataset style logic.
Keep axis title coloring mapped to the corresponding axis metric color.

Suggested Regression Test Matrix

Metric-to-axis mapping assertions for each supported dual-axis widget type.
Deterministic series order assertions after wildcard/template expansion.
Metric-color mapping assertions across multiple entities.
Series-order stroke style assertions across multiple entities (solid/dashed behavior).
Legend stroke style parity assertions against dataset stroke styles.
Tooltip stroke style parity assertions against dataset stroke styles.
Fallback behavior assertions when concrete paths are unavailable.

Avoid

Implementing ad hoc history mapping in chart consumers.
Bypassing sync service orchestration for reconciliation state.
Silent contract drift in reconcile payload structure.

References

.github/instructions/project.instructions.md
COPILOT.md (history-series and mapping architecture)

Más de este repositorio

mismo repositorio

angular-developer

mxtommy/Kip

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

2026-07-03125

kip-widget-creation

mxtommy/Kip

Create and scaffold new KIP Host2 widgets using the widget schematic with consistent post-generation implementation, registration, tests, and documentation updates.

2026-03-28125

kip-host2-widget

mxtommy/Kip

Apply KIP Host2 widget contract patterns for widget component changes, including runtime/options guards, stream observation structure, and transient signal state handling.

2026-03-11125

kip-dataset-orchestration

mxtommy/Kip

Apply KIP dataset ownership and lifecycle rules for widget and dashboard flows, including centralized write paths and owner UUID cleanup behavior.

2026-03-08125

KIP History Series Reconcile

Use this skill when changing history-series reconciliation or history-to-chart mapping behavior. This skill defines implementation patterns only; policy authority remains in instruction files.

Use This Skill When

Editing DashboardHistorySeriesSyncService reconciliation behavior.

Editing KipSeriesApiClientService integration behavior for reconciliation.

Editing history values to chart datapoint conversion.

Core Expectations

Preserve the reconciliation pipeline: dashboard state -> sync service -> API client -> plugin reconcile endpoint.

Route history response mapping behavior through HistoryToChartMapperService.

Keep plugin contract assumptions stable unless a deliberate API change is coordinated.

Keep reconciliation and mapping concerns separated.

Widget History Dialog Enhancements (Implementation Companion)

Use this checklist when changing widget history dialog behavior that affects historical series display.

Keep dialog code as a read-only history consumer; do not add reconcile orchestration to dialog components.

Keep template/wildcard expansion deterministic and stable across repeated renders.

Keep dual-axis behavior centralized in shared helpers (classification, ordering, style, and axis config).

Keep line/legend/tooltip stroke semantics sourced from the same dataset style logic.

Keep axis title coloring mapped to the corresponding axis metric color.

Suggested Regression Test Matrix

Metric-to-axis mapping assertions for each supported dual-axis widget type.

Deterministic series order assertions after wildcard/template expansion.

Metric-color mapping assertions across multiple entities.

Series-order stroke style assertions across multiple entities (solid/dashed behavior).

Legend stroke style parity assertions against dataset stroke styles.

Tooltip stroke style parity assertions against dataset stroke styles.

Fallback behavior assertions when concrete paths are unavailable.

Avoid

Implementing ad hoc history mapping in chart consumers.

Bypassing sync service orchestration for reconciliation state.

Silent contract drift in reconcile payload structure.

References

.github/instructions/project.instructions.md

COPILOT.md (history-series and mapping architecture)