halo-theme-dev

Guide developers through Halo theme structure, templates, and configuration YAML workflows.

Updated May 24, 2026
One-click install
npx skills add https://github.com/sAkuraOfficial/.agents --skill halo-theme-dev-sakuraofficial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: halo-theme-dev
Source: https://github.com/sAkuraOfficial/.agents/tree/main/skills/halo-theme-dev
Command: npx skills add https://github.com/sAkuraOfficial/.agents --skill halo-theme-dev-sakuraofficial

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Halo theme development can be time-consuming and error-prone due to complex wiring of theme.yaml, settings.yaml, templates, i18n, and tooling like vite-plugin-halo-theme. This skill provides up-to-date, reference-backed guidance and best practices to streamline building Halo themes.

Core Features & Use Cases

  • Guidance on structuring a Halo theme (theme.yaml, settings.yaml, templates, i18n)
  • How to integrate with vite-plugin-halo-theme and assets/references usage, plus debugging tips
  • Real-world use case: scaffolding a new theme from assets/theme-vite and validating theme.yaml compatibility
  • Note: Always fetch documentation from References when implementing specific field names or APIs
  • Quick adaptation for Vite-based and minimal templates

Quick Start

Copy the assets/theme-vite directory into your Halo themes folder, install dependencies, and start the Vite-based development workflow to begin building a theme.

Frequently Asked Questions about halo-theme-dev

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

FAQPage Schema
How do I structure a Halo theme with Thymeleaf templates and settings.yaml?

To structure a Halo theme, configure theme.yaml and settings.yaml, then organize Thymeleaf templates and i18n files. This guides wiring components and assets correctly for runtime loading.

How do I set up a Vite-based development workflow for Halo theme templates?

Setting up Vite-based Halo theme development involves copying the theme-vite directory, installing dependencies, and integrating vite-plugin-halo-theme to manage assets and templates.

What's the best way to integrate Finder APIs and localization into Halo themes?

Integrating Finder APIs and localization requires fetching reference documentation to avoid hard-coding version-specific field names, ensuring templates and assets are wired correctly.

Does this Halo theme development guide support both Vite and traditional Thymeleaf workflows?

Yes, it covers workflows for both Vite-based themes and traditional Thymeleaf templates. You can scaffold themes from assets and validate theme.yaml compatibility across both approaches.

Why does my Halo theme.yaml configuration fail during runtime loading?

Theme.yaml failures often stem from hard-coding version-specific field names or incorrect asset wiring. Always fetch documentation from references to ensure compatibility and validate settings.