Glance Config

Draft and refine valid Glance YAML for this repository. Keep output practical, preserve the user's existing structure when editing, and prefer project-local examples over generic placeholders.

Workflow

1. Identify the target artifact. Decide whether the user needs a full glance.yml, a page block, a widget block, or an included fragment.

2. Load only the references that match the task. Read references/glance-core-reference.md for Glance syntax, layout rules, shared widget properties, and custom-api guidance. Read references/project-widgets.md when the request involves this repository's Cup updates, Proxmox, or server-stats integrations. Read references/examples.md when the user asks for a ready-to-paste example. Read references/community-widgets.md when the request mentions community widgets, third-party widgets, or extension widgets.

3. Build the config at the right scope. If the user asks for a complete dashboard, produce top-level sections such as server, theme, and pages. If the user asks for a page or widget, return only the YAML fragment that belongs at that level unless they explicitly ask for the whole file. If the request is primarily about visual theme, branding, favicon/app icon, or custom CSS, switch to the dedicated glance-theme skill instead of forcing it through this one.