hc-new-widget

Automate HamClock-Next widget creation and integration via MCP scaffolding and REGISTER_WIDGET.

33|7|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/k4drw/hamclock-next --skill hc-new-widget
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hc-new-widget
Source: https://github.com/k4drw/hamclock-next/tree/main/.claude/skills/hc-new-widget
Command: npx skills add https://github.com/k4drw/hamclock-next --skill hc-new-widget

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end process of designing, scaffolding, and integrating new widgets into HamClock-Next using the REGISTER_WIDGET pattern and MCP tooling.

Core Features & Use Cases

  • Widget creation workflow: scaffold, register, and wire-up components.
  • MCP tooling integration: generate boilerplate for Widget, Provider, Panel, and Store.
  • Dashboard integration: ensure CMake and runtime registration via REGISTER_WIDGET work at startup.

Quick Start

Follow the MCP scaffolding workflow to generate a new widget scaffold and register it with the HamClock-Next dashboard.

Frequently Asked Questions about hc-new-widget

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

FAQPage Schema
How do I create a new widget in HamClock-Next?

You create a HamClock-Next widget by using MCP scaffolding to generate boilerplate for the widget, provider, panel, and store. This workflow automates the process of designing, scaffolding, and wiring up components.

How does the REGISTER_WIDGET pattern work for dashboard integration?

The REGISTER_WIDGET pattern handles runtime registration so your new widget appears at dashboard startup. The scaffolding workflow ensures CMake integration and runtime registration function correctly during the end-to-end creation process.

What do I need to scaffold before adding a widget to HamClock-Next?

You need an environment supporting MCP tooling and CMake to scaffold new widgets. The scaffolding workflow generates the required boilerplate for the widget, provider, panel, and data store components.

What is the best way to automate widget boilerplate generation for HamClock-Next?

The best way to automate widget boilerplate generation is using MCP scaffolding. It applies the REGISTER_WIDGET pattern to generate code for widgets, providers, panels, and stores, including CMake integration and error handling.

Why is my HamClock-Next widget not showing up at startup?

Your widget may not show up if CMake integration or runtime registration via the REGISTER_WIDGET pattern fails. The scaffolding workflow includes a thorough integration checklist to verify startup registration and resolve these errors.