How do I install the Widgetkit skill?

Run npx skillmds@latest add caglarbaranbora/widgetkit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Widgetkit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Widgetkit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Widgetkit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Widgetkit?

caglarbaranbora (@caglarbaranbora) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Widgetkit by caglarbaranbora — Agent Skill

Name: Widgetkit
Author: caglarbaranbora

Widgetkit

Route WidgetKit implementation tasks to the correct Knowledge Contracts -- widget declaration and families, timeline provider and entries, widget interactivity and deep links, and timeline reloading and refresh budget. Use when conforming to Widget, WidgetBundle, or WidgetConfiguration, choosing StaticConfiguration or AppIntentConfiguration, declaring supportedFamilies or reading widgetFamily, applying containerBackground, implementing TimelineProvider (placeholder, getSnapshot, getTimeline), building a Timeline of TimelineEntry values, choosing a TimelineReloadPolicy, wiring widgetURL, Link, Button(intent:), or Toggle(_:isOn:intent:), or calling WidgetCenter.reloadTimelines/reloadAllTimelines. v1 is home-screen/Lock-Screen widgets only -- no Live Activities/ActivityKit, no watchOS complications as a distinct surface, no Control Widgets (iOS 18 Controls/ControlWidget), no StandBy-specific layout. Triggers on WidgetKit, Widget, WidgetBundle, WidgetConfiguration, StaticConfiguration, AppIntentConfiguration, sup

File contents

WidgetKit — Foundations Skill

Purpose

Route WidgetKit implementation tasks to the minimum required WidgetKit Knowledge Contracts. v1 scope is home-screen and Lock-Screen widgets built with Widget/WidgetConfiguration and TimelineProvider only — no Live Activities, no watchOS complications as a distinct surface, no Control Widgets, no StandBy-specific layout.

Routing

Load only the contracts relevant to the task. All paths relative to knowledge/widgetkit/.

Conforming to Widget, WidgetBundle, or WidgetConfiguration; choosing StaticConfiguration/AppIntentConfiguration; declaring supportedFamilies or reading @Environment(\.widgetFamily); applying .containerBackground(for: .widget); or the kind string's stability -> widget-declaration-and-families.md
Implementing TimelineProvider's placeholder(in:), getSnapshot(in:completion:), or getTimeline(in:completion:); building a Timeline of TimelineEntry values; or choosing a TimelineReloadPolicy -> timeline-provider-and-entries.md
Wiring widgetURL(_:), Link, Button(intent:), or Toggle(_:isOn:intent:) into a widget's view -> widget-interactivity-and-deep-links.md
Calling WidgetCenter.shared.reloadTimelines(ofKind:)/reloadAllTimelines(), or reasoning about the refresh budget -> timeline-reloading-and-refresh-budget.md

Never load more than the contracts relevant to the specific question.

Stop Conditions

Stop and report if the requested topic has no matching Knowledge Contract in knowledge/widgetkit/ — do not guess or fall back to general knowledge.

Live Activities and ActivityKit — Deferred
watchOS complications as a distinct surface — Deferred
Control Widgets (iOS 18 Controls/ControlWidget) — Deferred
StandBy-specific layout — Deferred
Authoring an AppIntent itself — its parameters, perform() body, and any entities it exposes — owned by app-intents (knowledge.app-intents.intent-results-and-widget-hookup); this Skill only routes to wiring an already-authored intent into a widget's tap target
Scheduling the background work that produces new widget data (e.g. a BGAppRefreshTask) — owned by backgroundtasks (knowledge.backgroundtasks.background-refresh-and-widget-timeline-hookup); this Skill only routes to the reloadTimelines/reloadAllTimelines call site once new data has already landed

---name: widgetkitdescription: Route WidgetKit implementation tasks to the correct Knowledge Contracts -- widget declaration and families, timeline provider and entries, widget interactivity and deep links, and timeline reloading and refresh budget. Use when conforming to Widget, WidgetBundle, or WidgetConfiguration, choosing StaticConfiguration or AppIntentConfiguration, declaring supportedFamilies or reading widgetFamily, applying containerBackground, implementing TimelineProvider (placeholder, getSnapshot, getTimeline), building a Timeline of TimelineEntry values, choosing a TimelineReloadPolicy, wiring widgetURL, Link, Button(intent:), or Toggle(_:isOn:intent:), or calling WidgetCenter.reloadTimelines/reloadAllTimelines. v1 is home-screen/Lock-Screen widgets only -- no Live Activities/ActivityKit, no watchOS complications as a distinct surface, no Control Widgets (iOS 18 Controls/ControlWidget), no StandBy-specific layout. Triggers on WidgetKit, Widget, WidgetBundle, WidgetConfiguration, StaticConfiguration, AppIntentConfiguration, sup---# WidgetKit — Foundations Skill## PurposeRoute WidgetKit implementation tasks to the minimum required WidgetKitKnowledge Contracts. v1 scope is home-screen and Lock-Screen widgetsbuilt with `Widget`/`WidgetConfiguration` and `TimelineProvider` only —no Live Activities, no watchOS complications as a distinct surface, noControl Widgets, no StandBy-specific layout.## RoutingLoad only the contracts relevant to the task. All paths relative toknowledge/widgetkit/.- Conforming to `Widget`, `WidgetBundle`, or `WidgetConfiguration`; choosing `StaticConfiguration`/`AppIntentConfiguration`; declaring `supportedFamilies` or reading `@Environment(\.widgetFamily)`; applying `.containerBackground(for: .widget)`; or the `kind` string's stability -> widget-declaration-and-families.md- Implementing `TimelineProvider`'s `placeholder(in:)`, `getSnapshot(in:completion:)`, or `getTimeline(in:completion:)`; building a `Timeline` of `TimelineEntry` values; or choosing a `TimelineReloadPolicy` -> timeline-provider-and-entries.md- Wiring `widgetURL(_:)`, `Link`, `Button(intent:)`, or `Toggle(_:isOn:intent:)` into a widget's view -> widget-interactivity-and-deep-links.md- Calling `WidgetCenter.shared.reloadTimelines(ofKind:)`/`reloadAllTimelines()`, or reasoning about the refresh budget -> timeline-reloading-and-refresh-budget.mdNever load more than the contracts relevant to the specific question.## Stop ConditionsStop and report if the requested topic has no matching KnowledgeContract in knowledge/widgetkit/ — do not guess or fall back to generalknowledge.- Live Activities and `ActivityKit` — Deferred- watchOS complications as a distinct surface — Deferred- Control Widgets (iOS 18 `Controls`/`ControlWidget`) — Deferred- StandBy-specific layout — Deferred- Authoring an `AppIntent` itself — its parameters, `perform()` body, and any entities it exposes — owned by `app-intents` (`knowledge.app-intents.intent-results-and-widget-hookup`); this Skill only routes to wiring an already-authored intent into a widget's tap target- Scheduling the background work that produces new widget data (e.g. a `BGAppRefreshTask`) — owned by `backgroundtasks` (`knowledge.backgroundtasks.background-refresh-and-widget-timeline-hookup`); this Skill only routes to the `reloadTimelines`/`reloadAllTimelines` call site once new data has already landed

Frequently asked questions