ikf-heatmap-contract-enforcer

Audit UI components for IKF Heatmap Contract violations and refactoring plans.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/heyflouai/ikf-central-dashboard --skill ikf-heatmap-contract-enforcer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ikf-heatmap-contract-enforcer
Source: https://github.com/heyflouai/ikf-central-dashboard/tree/main/.claude/skills/ikf-heatmap-contract-enforcer
Command: npx skills add https://github.com/heyflouai/ikf-central-dashboard --skill ikf-heatmap-contract-enforcer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures consistency and adherence to the IKF Heatmap Contract across all heatmap-like components in the repository, preventing visual and functional discrepancies.

Core Features & Use Cases

  • Contract Auditing: Identifies violations of the heatmap contract, including color hue, signal display, layout, and sorting.
  • Refactoring Guidance: Provides a plan to refactor code into shared utilities and components to eliminate duplication.
  • Verification Checklist: Offers a visual checklist for manual verification of heatmap components.
  • Use Case: Automatically audit all mini-heatmaps on the dashboard and wishlist cells to ensure they use the correct signal-based coloring and numeric sorting, flagging any inconsistencies for correction.

Quick Start

Run the ikf-heatmap-contract-enforcer skill to audit all heatmap components for contract violations.

Frequently Asked Questions about ikf-heatmap-contract-enforcer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit UI components for heatmap contract violations?

To audit heatmap components for contract violations, run an audit that identifies files breaking signal-based coloring, numeric sorting, and layout rules, then generates refactoring suggestions for shared utilities.

What is a heatmap contract in frontend UI consistency?

A heatmap contract defines rules for signal-based coloring, numeric sorting, and consistent layout across heatmap-like components, ensuring visual and functional uniformity throughout the repository.

How do I fix inconsistent heatmap coloring and sorting in dashboard cells?

Fix inconsistent heatmap coloring and sorting by identifying violating components and following a provided refactoring plan to consolidate duplicated code into shared utilities and correct signal display.

Can I check dashboard mini-heatmaps for numeric sorting and layout consistency?

Yes, you can check dashboard mini-heatmaps and wishlist cells to verify correct signal-based coloring and numeric sorting, automatically flagging any layout inconsistencies for correction.

What is the best way to refactor duplicated heatmap code into shared utilities?

The best way to refactor duplicated heatmap code is to use a generated plan that identifies contract violations and outlines steps to extract shared utilities and components, eliminating redundancy.

When do I need a visual checklist for heatmap component verification?

You need a visual checklist for heatmap component verification when manually confirming that all UI elements adhere to rules for color hue, signal display, layout, and sorting after an audit.