cyface

This skill should be used when the user asks about "ApplicationV2", "ActorSheetV2", "ItemSheetV2", "DocumentSheetV2", "DialogV2", "DEFAULT_OPTIONS", "PARTS", "data-action", "_prepareContext", "HandlebarsApplicationMixin", "sheet registration", "form handling in Foundry", "tabs in Foundry sheets", "drag and drop in Foundry", "V12 to V13 migration", "migrate to V13", "convert to ApplicationV2", "ProseMirror editor", "submitOnChange", "tag form", "actions system", "editImage", "_processFormData", "_processSubmitData", "inline item editing", "CSS theming in Foundry", "theme variables", "CSS layers", or mentions FoundryVTT V13 application classes, sheet patterns, or migration from V12 to V13.

This skill should be used when the user asks about "FoundryVTT system development", "FoundryVTT module", "Foundry hooks", "data model", "template.json", "Actor class", "Item class", "Roll class", "compendium packs", "game settings", "game.i18n", "localize", "i18n", "testing FoundryVTT", "Vitest with Foundry", "mocking Foundry", "system.json", "FoundryVTT project structure", "Foundry documents", "embedded documents", "settings registration", "Hooks.on", "Hooks.once", "game.settings.register", "game.actors", "game.items", "CONFIG object", "FoundryVTT canvas", "FoundryVTT API", "SCSS in Foundry", "language files", "translation files", "pack management", "LevelDB packs", "compendium JSON", or mentions building a game system or module for FoundryVTT.

This skill should be used when the user asks to "create an Alpine component", "add Alpine.js", "use x-data", "add reactivity", "create a dropdown", "build a modal", "use Alpine store", "add x-show", "toggle visibility", "bind attributes with Alpine", "add focus trap", "use Alpine plugins", or mentions Alpine.js directives (x-data, x-bind, x-on, x-model, x-show, x-for, x-if, x-transition, x-cloak, x-ref, x-effect, x-teleport). Also applies when working with Alpine.js alongside HTMX.

This skill should be used when the user asks to "add HTMX", "make an AJAX request", "add hx-get", "add hx-post", "swap content", "add auto-refresh", "add polling", "submit form with HTMX", "add sorting with HTMX", "use hx-trigger", "add partial page updates", "use hx-swap", "add loading indicator", "boost links", "use server-sent events with HTMX", "add infinite scroll", "replace page content without reload", "add websocket support", or mentions HTMX attributes (hx-get, hx-post, hx-put, hx-delete, hx-target, hx-swap, hx-trigger, hx-vals, hx-indicator, hx-push-url, hx-boost, hx-confirm, hx-ext, hx-on, hx-select, hx-headers, hx-sync, hx-encoding). Also applies when building server-driven UIs or working with HTMX alongside Alpine.js.

This skill should be used when the user asks about "UI design", "UX design", "design principles", "usability", "visual hierarchy", "layout principles", "accessibility design", "Fitts' Law", "Hick's Law", "cognitive load", "information architecture", "visual design", "interaction design", "affordance", "progressive disclosure", "Gestalt principles", "color theory", "typography", "readability", "legibility", "golden ratio", "rule of thirds", "proximity", "alignment", "figure-ground", "signal-to-noise ratio", "mental model", "design review", "UI review", "design patterns", or mentions improving the visual design, layout, or usability of an interface.

This skill should be used when the user asks about "Coolify", "deploy app", "restart app", "app logs", "deployment status", "list servers", "list databases", "environment variables", or any other management of applications, databases, deployments, servers, services, or projects on a self-hosted Coolify instance via its REST API.