halo-dev

Use when managing Halo posts, single pages, categories, or tags from the terminal. This includes listing, creating, updating, deleting, exporting, importing, or any content management operation for Halo CMS. Trigger this skill whenever the user mentions Halo posts, pages, categories, tags, or content management in a CLI context, even if they do not explicitly mention 'content'.

Use when working with Halo CLI authentication, login, bearer token or basic auth, profile setup, profile switching, current profile inspection, or fixing missing keyring credentials. Trigger this skill whenever the user needs to log into Halo, manage Halo CLI profiles, switch profiles, or diagnose authentication issues.

Use when moderating Halo comments or replies, creating official replies, managing notifications, listing unread notifications, deleting notifications, or marking notifications as read. Trigger this skill whenever the user mentions Halo comments, comment replies, or notifications in a terminal context.

Use when operating Halo themes, plugins, attachments, backups, or moments from the terminal. This includes install, upgrade, activate, enable, disable, upload, download, create, delete, reload, and batch maintenance flows. Trigger this skill whenever the user mentions Halo themes, plugins, attachments, backups, moments, or any Halo CMS maintenance operation in a CLI context.

Use when searching public content on a Halo site with Halo CLI. This includes keyword search, site URL based search, result limits, or any search that does not require authenticated console access. Trigger this skill whenever the user wants to search a Halo site from the terminal, even if they do not explicitly mention 'search'.

Use when a task involves Halo CLI, Halo CMS command-line operations, or terminal-based Halo management. Also use when you need shared rules for profiles, JSON output, help discovery, config paths, and destructive actions. Trigger this skill whenever the user mentions 'halo', 'Halo CLI', or terminal operations for Halo CMS, even if the specific command area is not yet clear.

Use when the task involves Halo CLI, Halo CMS terminal operations, or any command-line interaction with Halo. This includes login, profiles, posts, single pages, search, plugins, themes, attachments, backups, moments, comments, notifications, or shell completion. Trigger this skill whenever the user mentions 'halo', 'Halo CLI', or wants to manage Halo from the terminal, even if the exact command area is unclear.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

Build React applications using React Router's data mode with createBrowserRouter and RouterProvider. Use when working with route objects, loaders, actions, Form, useFetcher, or pending/optimistic UI without the Vite plugin.

Build React applications using React Router's declarative mode with BrowserRouter. Use when configuring routes with JSX, navigating with Link/NavLink, or reading URL params and search params without data loaders or actions.

Build full-stack React applications using React Router's framework mode. Use when configuring routes, working with loaders and actions, handling forms, handling navigation, pending/optimistic UI, error boundaries, or working with react-router.config.ts or other react router conventions.

Use when creating or modifying a Halo CMS plugin: writing Java backend code, configuring plugin.yaml, defining custom extensions (GVK), creating custom APIs (CustomEndpoint, MVC controllers), building Vue-based UI with @halo-dev/ui-shared, setting up Gradle builds with DevTools, defining RBAC role templates, declaring pluginDependencies, exposing or consuming plugin extension points, publishing shared events, registering custom FormKit inputs, generating API clients from OpenAPI, registering theme-side Finder APIs, or handling plugin lifecycle (start/stop/delete).

Use when creating or modifying a Halo CMS theme, writing Thymeleaf templates, configuring theme.yaml or settings.yaml, calling Finder APIs, using vite-plugin-halo-theme, defining theme settings forms, referencing static assets, implementing halo:comment or halo:footer extension points, defining model annotation fields (AnnotationSetting), adding i18n support, or handling error pages. Always use this skill when the user mentions themes, templates, Thymeleaf, theme configuration, or wants to customize the frontend appearance of a Halo site — even if they do not explicitly say "theme."

Use when creating or modifying a Halo CMS theme: writing Thymeleaf templates, configuring theme.yaml or settings.yaml, calling Finder APIs, using vite-plugin-halo-theme, defining theme settings forms, referencing static assets, implementing halo:comment or halo:footer extension points, or defining model annotation fields (AnnotationSetting).